Graham McNicoll

If your experimentation stack is Statsig, the last few months have probably been confusing. When OpenAI acquired Statsig, I saw many teams read it as good news. The assumption was that being owned by OpenAI would turn it into the most advanced experimentation platform on the market. I think the opposite happened. OpenAI wanted the team. It kept the talent and sold the rest to Amplitude. The brand and the customer base moved over. The code moved with them, but none of the people who actually built the product went along. I have seen how this plays out for a customer, and it shows up fast. Your support contact is gone, and the roadmap slows down. The work you were counting on stops moving, and you are now depending on a company that did not build the product and has to learn it from the outside. This is the part of choosing an experimentation platform that I think almost never gets weighed honestly. On the day you sign, you are buying into not just the product, but the company that builds it, and making sure they continue to thrive and build the best product. This is a real risk. You don't want to invest in a product and then have everyone who understands the system walk out the door. I keep coming back to one thing. Open source removes that single point of failure, and the Statsig unwind is the cleanest example I have seen of why it matters. A company can be acquired and broken up. The code cannot be taken away from you if you already have it. It is why we built GrowthBook the way we did. Your experiments run against your own warehouse and the source is yours. There is no parent company whose roadmap you are now stuck with, and no switching cost waiting for you if priorities change. If you are on Statsig and thinking about the move, we built migration paths for exactly this. They are on growthbook.io