OrthıD
Browse the docs
Operations

Upgrades

3verest runs upgrades on your sovereign cell for you. They are rolling and zero-downtime by default, your data is backed up before any schema change, and you are notified - no action is required on your side.

Keeping OrthID current is part of the managed service. 3verest moves your cell to new versions, applies any database migrations, and rolls the request path with no downtime. You do not pull anything, run anything, or schedule a maintenance window.

Versioning

OrthID follows semantic versioning as MAJOR.MINOR.PATCH:

  • Patch releases are bug and security fixes. They are always safe to apply and never change the database schema.
  • Minor releases add features and may add backward compatible migrations. 3verest moves your cell one minor at a time.
  • Major releases may contain breaking changes to the API or schema. 3verest coordinates these with you ahead of time and shares the migration notes that matter for your integration.

How an upgrade runs

The request path uses a rolling update with readiness checks, so old instances keep serving until new ones are healthy. Because tokens are signed by keys that survive the upgrade, in-flight sessions stay valid throughout. Migrations are versioned and run forward only; within a minor series the new schema works with the immediately previous version, which is what makes the roll safe.

Backed up before every change
3verest takes a fresh, verified backup of your cell before applying any migration, so there is always a clean way back. See Backups & continuity.

What you see

You are notified when an upgrade is scheduled and when it completes. For a patch or minor release that is typically all you will notice; for a major release, 3verest flags any API or behaviour changes well ahead of the roll so your team can plan around them. There is nothing to install and nothing to roll back yourself - if a release misbehaves, 3verest rolls your cell back automatically.

No action required
For the overwhelming majority of upgrades you do nothing. The exception is a major release with a breaking API change, where 3verest will tell you in advance exactly what to update in your integration.

Next steps