Get a Demo

PlatformDeploy

One click from staging to production

Every application runs in a staging copy first. Once a version is proven there, you send that same version live in one click — checked on the way, with no downtime for your users. If something looks off, one click puts the last version back.

Get a DemoSee the release history
app.cenna.io/environments
Migrations dry-runHealth checkSmoke testsApproval
Production on v2.3.9 · v2.4.1 ready in stagingPromote to production

01Environments

How a version reaches your users

The board above shows the last step. Here is the whole path — every version takes it, so a release is a routine journey rather than a leap.

  1. Staging

    It proves itself here first

    A new version runs in a full copy of the app — its own database, its own settings, connected to your real systems. Your team tries it the way users will.

    Its own data · Its own settings

  2. Promotion

    One click sends it live

    When it is ready, that exact version moves to production. Cenna runs your checks on the way and stops if any fail, so a bad version never reaches anyone.

    Same version · Checked first

  3. Production

    Users get the proven version

    The new version takes over only once it is healthy, with the old one serving until then. Its cost is tracked on its own, so a staging test never lands on the production bill.

    Zero downtime · Cost tracked apart

02Promote

Ship the exact version you tested

When a version has proven itself in staging, one click moves that same version to production. Nothing is rebuilt, so there are no surprises — what your team tested is precisely what your users get.

  1. 01

    Choose the version

    Pick the staging version you want live. It is the same one your team tested, not a new build that might behave differently.

  2. 02

    It gets checked first

    Cenna runs the checks you set — a database dry-run, a health check, smoke tests, a sign-off — and stops if any of them fail.

  3. 03

    Users move over safely

    The new version starts up and only starts serving people once it is healthy. The old one keeps running until then, so nobody sees an error.

  4. 04

    It's on the record

    Who promoted it, what changed, and how long it took are saved, so there is never a question about what went live or when.

Same version you tested · Checked before it goes live · Nobody sees downtime

03History

Every release, in one history

Every version that has gone live, updated, or been rolled back — across every application — with whether it worked and how long it took. It is the one place to answer "what changed, and when?"

The Contract Hub rollback took 3m 51s — one click back to the last good version, no scramble.

04Rollback

Going back is one move

If a new version misbehaves once it is live, you put the last good one back with a single click. It happens in a couple of minutes, and nobody has to be woken up for it.

  • The last version is kept ready

    The previous release stays running in the background, so going back is instant — there is nothing to rebuild or wait for.

  • Minutes, not a midnight call

    A rollback finishes on its own in a few minutes. The Contract Hub one above took under four.

  • It shows up in the record too

    Rolling back is saved in the same history with who did it, so the timeline of what ran is always complete.

05FAQ

Common questions

How many environments can an application have?

Staging and production come as standard. You can add more — a QA space, a UAT space, or a separate production per region — and each is a genuinely separate copy, not a label on a shared one.

Does promoting rebuild the application?

No. Promoting sends the exact version that passed staging straight to production. Because nothing is rebuilt, what you tested is exactly what runs — the usual "but it worked in staging" surprises simply do not happen.

Can we require a sign-off before production?

Yes. A sign-off can be one of the checks a promotion waits on, so a named person has to approve before anything goes live. Their approval is saved on the release.

Do users see errors while a version is going live?

No. The new version only starts serving people once it is healthy, and the old one keeps handling requests until then. Nobody is dropped mid-way.

How far back can we roll?

To any release Cenna still keeps for that application. The last version is always ready for an instant switch back; older ones come back from their saved copy.

See a promotion and a rollback, live.

Thirty minutes: we promote a version from staging to production behind its checks, then roll it back — so you see exactly what your team would do on a bad Friday.

Get a Demo

Built for speed. Engineered for control.