It looks like they’ve gone Enterprise-only with Publish. When you’re logged into Builder.io, apart from the free plan, the only other plan available is “Enterprise”.
If you create a new builder.io account, you’re not even allowed to use Publish anymore unless you contact Builder to start an enterprise plan:
Talking with Builder Support, the team doesn’t even seem sure what’s going on with Builder Publish.
The “Growth” and “Pro” plans are mentioned, but none of those plans are shown in Builder.io anymore. “Growth” is apparently gone. Support is confused whether “Pro” is a plan with the CMS.
Just wild that the product that made Builder.io is getting discarded in favor of Fusion. Publish is a great product because it’s a productive CMS for a range of users (particularly with custom components).
Fusion is just not a productive product for developers, and the dependence on AI means Builder Fusion as a content backend is slow and sloppy.
Hello @chris-hayes I’m Adam, one of the Product Managers here at Builder where I focus mostly on Publish. I can definitely tell you that we’re not “sunsetting Builder Publish” or even decreasing our commitment to it in any way.
We’ve actually been doing a lot of development on it over the last year, which has enabled our users to ship more content faster than ever before. For a list of those improvements and where we see ourselves headed in 2026, definitely give this blog post a read.
You are correct though that we recently made an important change to our pricing strategy for Publish. That change is that new customers interested in Publish are encouraged to connect with our sales team rather than signing up directly through our website. We believe that this allows us to better understand specific needs and ensure Publish is the right fit for their use case.
Users that are already using Publish should see no changes - other than limited upgrade options for free tier users. Existing users continue to have full access to their spaces, can create new ones as needed, and can manage subscriptions exactly as they do today.
We know this shift may feel like a step backward, especially for users like yourself who value self-serve access. We hear that concern. We believe this decision allows us to focus our Publish resources on delivering better outcomes for the customers already building with it, while ensuring new customers get the dedicated support that a CMS implementation typically requires.
I’m Adam, one of the Product Managers here at Builder where I focus mostly on Publish. I can definitely tell you that we’re not “sunsetting Builder Publish” or even decreasing our commitment to it in any way.