Every deployment has an identity and a return path.
A release is accepted only when its source commit, build manifest, checksums, migrations and rollback command agree.
What a verified release records
The public site and the operational platform are deployed independently, but refer to the same canonical source revision.
- 01
Commit SHA
The exact source revision used by the build.
- 02
Artifact checksums
Integrity values for deployed packages and configuration.
- 03
Migration state
The database version expected by the release.
- 04
Rollback
A tested command and the previous compatible artifact.
Recent releases
Notable platform releases, in reverse chronological order.RSS
- July 30, 2026
Control plane v5.16: activation gates and recovery proof
Activation guidance, recovery hostname drill and private origin proof landed in the control plane. Enforcement remains gated behind stability windows and rollback evidence.
- July 29, 2026
Edge telemetry v5: live traffic windows
Minute-level traffic rollups, observation attribution and verified status displays now power the operational dashboard without entering the visitor request path.
- July 29, 2026
Customer dashboard V4
The customer dashboard moved to route-scoped data loading, explicit unknown states and a persistent product shell for portfolio and per-domain operations.
- July 28, 2026
Policy replay and origin outage drill
Policy replay evidence, customer edge fallback routes and freshness controls were exercised end to end, including an origin outage drill.
- July 27, 2026
Self-hosted identity with step-up
Sign-in moved to the self-hosted AegiFlow identity flow: OIDC sessions, passkeys, TOTP and step-up verification before sensitive actions, with Romanian onboarding.
- July 23, 2026
Single-source public website
The public website moved to a single bilingual Astro source with immutable releases, checksums and a tested rollback path.