Introduction

Since launching the Managed Guardian Service (MGS) in beta in 2022, our goal has been simple: make it easier for organizations to build, test, and operate Guardian-based workflows without unnecessary infrastructure friction. Over the past several years, MGS has been shaped by real-world usage across the Guardian ecosystem, with more than 1,000 users onboarding through the platform and deploying policies in test and production environments.

Today, we are excited to share the next milestone in that journey. On March 2, 2026, the Managed Guardian Service will officially enter general availability (GA), alongside the introduction of ATP (Automatic Transaction Processing), a new optional Hedera HBAR consumption model designed to further simplify Guardian onboarding and operations.

This post explains what GA means, why ATP was built, and what organizations can expect going forward.

What General Availability Means

General availability reflects the maturity and stability of the Managed Guardian Service as a production-ready platform. Moving to GA allows us to formalize how MGS is operated and supported, while maintaining continuity for existing users.

Importantly:

• There are no breaking changes associated with GA
• Existing tenants, users, environments, policies, and configurations remain intact
• No forced migrations or automatic reconfiguration occur

GA is not a reset. It is a formalization of a platform that has already been operating in real-world scenarios for years.

The Problem ATP Was Built to Solve

While Guardian enables powerful, verifiable workflows, onboarding to Web3-based infrastructure can still be a barrier for many organizations. Managing wallets, private keys, and cryptocurrency introduces operational overhead that is often unrelated to an organization’s core mission.

For enterprises, NGOs, and teams new to Web3, these requirements can slow adoption and complicate internal processes. We built ATP to remove that friction, allowing organizations to focus on outcomes rather than infrastructure management.

Introducing ATP

ATP is an optional MGS-managed Hedera consumption model that simplifies how organizations onboard to, operate, and offboard from Guardian environments.

With ATP, organizations can begin using Guardian without directly managing cryptocurrency or underlying transaction mechanics. ATP works seamlessly for both testnet and mainnet use cases and is designed to fit naturally into enterprise operating models.

What ATP Enables

ATP introduces several capabilities that significantly reduce onboarding and operational complexity:

• Onboard in under 60 seconds: New organizations can be up and running with Guardian in under a minute.
• Pay in dollars: Organizations pay for usage in USD, while MGS manages the underlying transactions automatically.
• No crypto handling required: There is no need to manage wallets, private keys, or cryptocurrency directly.
• Cloud-like consumption experience: Guardian usage through ATP feels similar to cloud platforms such as AWS, Azure, or Google Cloud, where consumption is handled behind the scenes.

These capabilities make Guardian more accessible to a broader set of users, without sacrificing trust or transparency.

Self-Managed vs MGS-Managed: Choice and Flexibility

ATP is designed to provide flexibility, not lock-in.

• Fully self-managed operation remains supported
• ATP is optional and enabled at the tenant level
• Organizations can move into ATP and move back out as their needs evolve

Ownership of policies, schemas, and topics remains explicit, signed, and auditable at all times.

Enterprise Readiness and Deployment Options

As part of GA, MGS also supports advanced deployment options for organizations with additional requirements, including:

• Dedicated hosting environments
• Regional deployment considerations
• Environment-level isolation

These options are available for organizations that require greater control or separation and are offered as part of tailored enterprise engagements.

GA Transition and Trial Period

When Managed Guardian Service enters general availability on February 27, 2026, existing accounts will automatically enter a 30-day trial period.

During this trial:

• There is no interruption to current usage
• All existing tenants, environments, users, and policies continue to operate as they do today
• Organizations have time to review available options and ask questions

A free tier will continue to be available, and no changes occur without engagement or approval.

What Happens Next

General availability marks an important milestone, but it is not the end of the journey. Additional details around subscriptions, ATP, and deployment options will be shared following GA.

We want to thank everyone who has participated in the Managed Guardian Service beta. Your feedback and real-world usage have been instrumental in shaping the platform.

If you have questions or would like to discuss how GA or ATP applies to your organization, our team is available at support@guardianservice.io.

We look forward to continuing to build with the Guardian community.