System status
The running posture, stated honestly for our launch stage.
Where each system stands.
We do not publish an aggregate uptime percentage before we have an honest measurement window. Systems not yet generally available are labeled Pre-launch, not dressed up as live.
Marketing site
guardkin.com — Vercel edge + Cloudflare.
Application API
Generally available at launch; pilot-cohort access is provisioned directly.
Authentication
Clerk-backed; MFA enforced. Live for pilot tenants.
Audit chain
Hash-linked, signed, dual-written — hot 90d (Axiom) · cold WORM 7y (S3 Object Lock).
The record, as it accrues.
Every incident that affects a published system will be recorded here with a timestamp, impact, and resolution — the same honesty the transparency report commits to annually.
History begins at launch
No incidents to report.
There is nothing here yet because there is nothing to disclose — and we would rather show an honest empty ledger than backfill a 90-day uptime graph we have not measured.
Get notified of incidents.
Status subscriptions go live with the hosted status page at launch. Until then, security and availability notices for pilot tenants are sent directly — reach us and we will add you to the notification list.
Subscription endpoint · available at launch