Products
Solutions
Resources
Our product updates page tells you what we shipped. I want to share more of the why.
We’ve been operating at a fever pitch recently. Building, meeting with customers, getting feedback, jumping on support needs, building more. The product updates page gives you a view of the work that’s reached a finished state. There’s more coming down the pipeline.
With all these pieces in flight, it can be hard to follow the larger story. I wanted to take a moment to give some color commentary on how our updates fit together and why we’ve been prioritizing what we have.
The story of May, June, and July’s feature releases is rooted in customer requests, and it follows two narratives: a governance story and an ease-of-access story.
How we’ve been learning what to do
Everything we shipped in June and July was sourced from customer requests, both individually and for the larger themes.
I’m in about two customer meetings per day, every day of the week. That gives me a lot of opportunity to hear about what you want and gauge if we’re planning the right features.
In those conversations, the team and I listen for patterns. We’ll ask you for your top priorities, and then try to figure out the underlying reason or needs behind those asks. The more we hear an underlying need come up in conversations, the more important we know it is.
As we start forming hypotheses of what’s important, we’ll test them quickly by putting them back in front of customers in future talks. I’ll say, “Here’s what we think we should be focused on,” and if the customer mirrors the thinking or zeroes in on it, that validates my hypothesis.
The signal for more governance and easier access came up organically and was super clear.
The governance story
On the governance side, what we heard is that you were looking for finer control over the process by which changes get made, whether those changes happen within the Statsig application, in the API, or with the MCP server.
Things like change reviews are important because PMs like me can sometimes make inadvertent changes we shouldn’t. Engineers don’t want that. PMs don’t really want that either. So orgs establish formal change processes.
Our main Statsig application already meets a lot of needs around those processes. But the rise of coding agents complicates things. Now it’s not just rogue PMs updating a config or changing a targeting rule in the Console, but also agents doing it via MCP tools, or folks working in external UIs interacting by API.
To keep things from getting gnarly, it was clear we needed to extend governance to wherever the changes take place. The bulk of our product updates the past months went toward tackling this number one theme, enhancing the endpoints and tools so that when you initiate a change, it follows a governance process correctly.
Feature gate reviews don't require a console to work anymore
You can audit version history via MCP now
MCP now follows global user permissions for read-only access (this was one of our biggest requests)
And that's just a few of the dozen updates we've shipped. Wherever you use Statsig, we’re meeting you there to support your governance process.
The ease of use story
The multitude of ways we heard about you using Statsig led to our second theme: ease of use. Expanding access to functionality shouldn’t stop with governance. If there’s a way to do anything in the Statsig application, there should also be a way to do it via API or MCP.
There’s an ongoing debate in the industry about headless vs. UI, so I want to be clear that this isn’t about that. To be honest, a lot of that debate seems mostly about aesthetics. We aren’t prioritizing one mode over the other; we’re prioritizing making it easy for everyone to use Statsig, however they use it.
Single-override DELETE endpoints make it easier to clean up individual overrides between test runs
You can spin up Autotunes from the MCP now
The full experiment review lifecycle is now available in API and MCP
Improvements like this aim to make end-to-end actions easier, from coming up with an idea to configuring it to learning from it. There’s definitely more to go for expanding access, and we’ll stay focused on the endpoints that are most impactful to how you want to work.
The next episode
We’ve used the past couple of months to establish this pattern of getting validation from customers and then continuing to build with these tools. We’re excited for this to continue with larger areas of investment and new innovation.
Governance that works for your processes is a platform necessity. We have more to do around governance and review processes, and you’ll see that coming to the MCP tools as well. We’re aiming to make sure all interaction modes have parity.
There's also more innovation coming beyond this in the next couple of months. The product updates page will continue to update as we ship new features, but I’ll also keep posting these color commentaries about once a month.
And if you have other priorities, please let me or my teammates know. More team members are coming online, and we’re going to keep the conversation going to keep improving the Statsig platform for you.