CEDX Deploy · Developer & low-code
Deploy is the estate's shipping lane: every deploy carries provenance and a risk score, every environment carries a protection tier, and the safe rollback window is measured in minutes — before you need it.
The hardest alert on the overview reads: checkout production risk 88, window 12m — an irreversible migration with no canary. A deploy tool that prints that before the fact is doing its job.
Runs on demo data — Northline Systems is the demo workspace, not a customer.
What it is
320 deploys with service, environment, status, provenance, SHA, duration and risk. dpl_a8f2 — checkout-api to production — carries an Automation provenance, a review flag, 4m 12s and risk 88. Who or what shipped a change is a column, not a rumor.
18 environments across production, staging, preview and sandbox tiers. production requires 2 reviewers and a 10-minute wait, holds 48 variables and 12 services; training has none and has gone stale. Protection is per-environment configuration you can read.
96 preview hosts, one per PR or branch, with service, status and age. pr-951 fix/partner-auth queues for checkout-api; 49 are ready to open; 34 have sat over 72 hours with a consider-expire flag. Previews are cheap because they are counted.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/deploy.
01 — Overview
320 deploys at 56.6% steady, a 4m 12s mean build — and a ship health of 51%, printed without rounding up. Alerts root-cause the pressure: a payments-settle schema live with under 10 minutes of safe rollback, an edge rewrite rolled back after a failed canary, and 9 required checks failing right now.
02 — Deploys
1–25 of 320 deploys across preview, staging and production. dpl_c1e4 — payments-settle, Assistant provenance, review flag, 6m 50s, risk 91 — sits two rows from dpl_9b30, an inventory-read promote at 02:14 that the overview flags as after-hours. Context is on the row.
03 — Environments
production and hotfix both demand required reviewers; canary takes one reviewer and a 5-minute wait. dr-us-east demands reviewers and has gone stale — a finding in itself, on screen.
04 — Previews
Preview hosts carry their PR, branch and service — feat/ledger-partition spans four of them across storefront-web, payments-settle and notify-pipeline. Errors surface here first: pr-731's webhook-dispatch host shows Error at 4 days old.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the pipeline: the 4m 12s mean build, the 13 deploys blocked on failing checks, and the discipline that keeps 02:14 promotes rare and flagged.
320 deploys · 56.6% steady
The required checks are their suites — 9 failing right now, each one a named gate between a branch and production.
13 blocked · 9 checks failing
Run the 18 tiers from training to canary: reviewers, wait times, variable counts — and the stale flags when an environment stops earning its compute.
18 environments · 7 productionThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Build and promote average 4m 12s across the window — the card on the overview, not a brochure number.
Required checks gate every tier: 13 deploys currently blocked, 9 checks failing, each named on the row it stops.
Production demands 2 reviewers and a 10-minute wait; agent-origin production deploys queue for review — 9 are waiting now.
The safe window is measured before it is needed: 12 deploys have 30 minutes or less, and payments-settle's is under 10. The edge rewrite used its window after a failed canary.
One record
Deploy is not a release tool for one stack. It is the same gate for apps, functions, scripts and environments — one provenance model across all of it.
The required checks blocking 13 deploys are Test suites — a red suite here is a stopped deploy there.
CEDX SandboxStaging and sandbox tiers are Sandbox environments, and preview hosts clone from the same machinery.
CEDX FunctionsA function deploy is a row in this ledger — runtime, region and risk score travelling together.
CEDX ScriptsAutomation-origin deploys carry the assistant's name and a review flag — the same approval discipline as scheduled runs.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your first pipeline
Deploy with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/deploy. It runs on demo data from the Northline Systems demo workspace.
Deploy impact: reversibility, canary coverage, schema change and blast. The checkout-api deploy at risk 88 carries an irreversible migration with no canary — the alert says exactly that, with a 12-minute window.
Like human ones, plus a flag. Assistant and Automation provenance show on the row, and production deploys from an agent queue for review — 9 are waiting in the demo workspace, each with approval control at the environment tier.
The minutes in which a deploy can be safely reversed, measured per deploy: 12 sit at 30 minutes or less, and payments-settle's v4 schema has under 10. The edge gateway's failed canary used its window and rolled back — that is what the number is for.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then check the rollback window on the last irreversible thing you shipped.