A more direct model for production support on the OP Stack
We built the OP Stack to be fully open source and MIT licensed, so anyone can take it and launch a chain. Over the past several years that model has worked: more teams have brought chains into production, the ecosystem has grown, and rollup-as-a-service providers have helped make deployment and early operations easier.
As those chains have matured alongside the wider industry, the support they need has matured too.
This month we're winding down the legacy support agreements we held through third-party rollup-as-a-service providers. Going forward, teams that want production support directly from OP Labs will work with us through OP Enterprise. It's a more customer centric model that will allow OP Stack partner to have a direct support relationship with the builders of the OP stack.
Launching a chain was the first step
The OP Stack made launching a chain significantly more straightforward. But deploying a chain and operating one in production are different jobs.
Most days a chain runs itself. The days that matter most are the ones where it doesn't: a sequencer stalls, an upgrade surfaces a regression, a derivation edge case puts the chain on the wrong fork. In those moments the most important question is simple. How fast can someone who understands the protocol at the level of the people who wrote it get hands on the problem?
For years, many teams got their support through a provider that sat between them and us. As the OP Stack ecosystem grew, that model added intermediaries and extra layers of communication, and spread our team thin across too many surfaces. It wasn't the best experience for the chains relying on it, and it isn't the model that scales as more value moves onchain.
Bringing production chains closer to the source
The natural next step is to make that relationship direct. With OP Enterprise, you work with the team that writes the code, and the support is built into how your chain runs:
High-availability sequencing that fails over to a healthy node automatically, before users notice anything.
Staged, monitored upgrades that get halted and rolled back at the first sign of a regression, instead of going chain-wide.
Proactive monitoring and incident response from OP engineers who can act directly, without waiting for a ticket.
The protocol authors on staff to diagnose the rare, complex failures correctly the first time.
Defined SLAs, with real accountability behind them.
Premium features that aren't available to chains running through a third party.
The point is a closer operating relationship for chains that carry users, applications, and value. Teams on OP Enterprise are in direct contact with the people who built the stack, the ones who know how to diagnose and resolve the most complex issues in production.
This gives chain operators a clearer owner, gives our engineers better visibility into what production chains need, and helps us improve the OP Stack based on what the most demanding chains require.
Open foundation, accountable support, one clear relationship
None of this changes the OP Stack itself. It's open, anyone can build on it, and that isn't changing. Teams can continue to launch and operate chains independently, or work with the infrastructure providers that best fit their needs.
What we're consolidating is how production support from OP Labs is delivered. It's the same shape as a company like Databricks, where the technology is open and the business is the managed service on top.
A stronger model for the next phase
This shift lets us focus our time and engineering where we can have the most impact: building the OP Stack, making it more resilient, and supporting the production chains that depend on it through a direct, accountable operating model.
Chains already working with us through OP Enterprise are unaffected. For chains that stay with a third-party provider: OP is no longer directly in the loop on support. Day to day that may be perfectly fine. The difference shows up in the rare, complex moments, a deep protocol bug, a derivation edge case, a security-sensitive upgrade, where having the team that builds the stack directly engaged is what determines how fast a chain recovers. Without it, recovery can be slower and less certain. For teams that want that direct support, and the resilience that comes with it, OP Enterprise is the path forward.