{ "componentChunkName": "component---src-pages-blog-markdown-remark-fields-slug-js", "path": "/blog/evergreen-hosting-announcement", "result": {"data":{"markdownRemark":{"html":"

Introducing Evergreen Hosting: Automatic Upgrades for SuperTokens

\n

Today we’re announcing Evergreen Hosting for SuperTokens managed instances.

\n

Starting soon, managed SuperTokens instances will automatically upgrade to the latest stable version as new releases become available. These upgrades are designed to be transparent, gradual, monitored, and reversible — with zero downtime for the vast majority of releases.

\n

This will become the new default behavior for managed hosting.

\n

If your team needs to continue using manual upgrades, you’ll still be able to opt out at any time.

\n
\n

Why We’re Making This Change

\n

Authentication infrastructure sits directly on the critical path of application security.

\n

When security vulnerabilities are discovered, the time between a patch becoming available and that patch being deployed matters more than ever.

\n

Historically, managed SuperTokens instances required customers to manually trigger upgrades. While this gave teams maximum control, it also meant many instances remained on older versions longer than intended — sometimes missing important security and stability improvements.

\n

The urgency around fast patch adoption is increasing rapidly.

\n

Recent developments like Anthropic’s Project Glasswing have demonstrated how AI-powered systems can now discover software vulnerabilities at unprecedented scale and speed. The time between vulnerability discovery and active exploitation is shrinking across the industry.

\n

For security-critical infrastructure like authentication, staying continuously updated is becoming the safer default.

\n

Evergreen Hosting is our response to that shift.

\n
\n

What Evergreen Hosting Does

\n

With Evergreen Hosting enabled, your managed SuperTokens core instance will automatically upgrade to the latest stable version as releases roll out.

\n

You do not need to:

\n\n

Your existing integration remains exactly the same.

\n

The upgrade happens entirely on the infrastructure side.

\n
\n

How Rollouts Work

\n

We designed Evergreen Hosting around safety, progressive delivery, and rapid recovery.

\n

1. Gradual Rollouts

\n

New releases are never deployed to every instance simultaneously.

\n

Rollouts happen in stages:

\n
    \n
  1. Development instances first
    2. \n
  2. Small production cohorts next
    3. \n
  3. Progressive rollout across the remaining fleet
    4. \n
\n

This staged approach helps us detect issues early before they affect a broader set of customers.

\n
\n

2. Progressive Traffic Shifting

\n

Even within an individual instance, traffic is migrated gradually to the new version rather than all at once.

\n

This allows us to observe real-world behavior under load while minimizing blast radius if something unexpected occurs.

\n

3. Continuous Monitoring

\n

After every upgrade, instances are automatically monitored for:

\n\n

Monitoring continues throughout rollout and after completion.

\n

4. Instant Rollback

\n

If an issue is detected, rollback happens automatically within seconds.

\n

Additionally, we maintain a one-week rollback safety window after rollout completion so delayed or low-frequency issues can still be safely reverted.

\n
\n

Downtime Expectations

\n

For the overwhelming majority of releases, upgrades happen with zero downtime.

\n

Your authentication APIs continue serving traffic throughout the rollout process.

\n

In rare cases involving significant data restructuring or major infrastructure transitions, a short maintenance window may be required. These windows are typically under a minute, and customers will receive advance notice beforehand.

\n

What Evergreen Hosting Does Not Change

\n

Evergreen Hosting only changes how your managed instance is updated.

\n

It does not change:

\n\n

Manual upgrades are also not going away.

\n

Teams that require strict change-management processes, internal QA validation, or version pinning can continue operating that way.

\n

Opting Out

\n

We understand that some organizations need tighter control over deployment timing.

\n

You can opt out of Evergreen Hosting at any time.

\n\n

Your instance will remain on its current version until you manually upgrade again or re-enable automatic upgrades.

\n

Version Pinning Support

\n

For customers with compliance requirements, validation pipelines, or release certification processes, version pinning remains fully supported.

\n

You can continue locking your instance to a specific version while performing internal testing before upgrading.

\n
\n

Why We Believe This Is the Right Default

\n

Infrastructure security increasingly depends on reducing operational delay.

\n

As software ecosystems become more interconnected — and as AI accelerates vulnerability discovery — the safest systems are often the ones that stay continuously updated.

\n

Our goal with Evergreen Hosting is simple:

\n\n

While still respecting that some teams need manual control.

\n

Timeline

\n\n

Questions?

\n

If you have questions about rollout mechanics, rollback guarantees, version pinning, compliance workflows, or whether Evergreen Hosting is the right fit for your environment, reach out to the SuperTokens team.

\n

We’re happy to walk through your setup and help determine the best upgrade strategy for your organization.

","frontmatter":{"date":"May 07, 2026","title":"Introducing Evergreen Hosting: Automatic Upgrades for SuperTokens","cover":"evergreen-hosting-announcement.png","author":"Joel Coutinho","description":"SuperTokens managed instances will now automatically receive stable upgrades with zero downtime, instant rollback, and continuous monitoring"},"fields":{"slug":"/evergreen-hosting-announcement/"}},"site":{"siteMetadata":{"title":"SuperTokens Blog"}}},"pageContext":{"id":"fd9c2784-b677-5739-823d-b6e538de610f","fields__slug":"/evergreen-hosting-announcement/","__params":{"fields__slug":"evergreen-hosting-announcement"}}}, "staticQueryHashes": []}