Live today
Capture, the route map, your control center, the generated API reference, and the route inventory tests behind it all run in code today - not slideware.
Live status
Know exactly what's running.
This is the system you trust with your models, in plain sight. Check what's live, what's still in the works, and how to reach us - right now, no spin and no hidden incidents. Health you can verify yourself, kept separate from features we haven't finished.
Live right now
925routes live and mapped
8features still in the works
secret-safenothing private leaks
2 of 6surfaces fully shipped
What's running
Every part, with its real state.
No green lights we can't back up. Here's what's live today and what's still being built - so you always know exactly what you're relying on.
| Surface | State | Detail | Route |
|---|---|---|---|
| Public site | Operational | Live. Every page, the product docs, pricing, the trust center, and the full API reference are up and ready to use. | / |
| API reference | Operational | Live. Every route is listed straight from the running backend and checked by tests, so the docs match what you actually call. | /docs/api |
| Control center | Mounted | Up and wired in. Set your rules, watch captures and compiles, and manage exports - all from one place in your account. | /account/api-control-center |
| Compiler artifacts | Gated | In the works. Manifests, examples, evaluators, hashes, target recipes, and receipts are all in place; packaged releases are still being finished. | /platform |
| Exports | Mounted | Up and wired in. Take your proof out of the UI - evidence packets, SIEM/GRC handoff, catalogs, and verifier receipts, with nothing private leaked. | /integrations |
| Audit evidence | Secondary | Lives on its own. The audit verifier and signed reports stay available on the audit module - a separate surface from the core product status here. | kolm.ai/audit |
Each state shows a shape and a word, not a color alone. Check means operational and serving traffic. Ring means mounted and wired in. Clock means gated, in the works behind a readiness check. Boxed cross means it lives on its own surface, off this status page.
30 days agotoday
SERVING 30 days verified
Live checks
The same checks we run before every ship.
This page reads the exact public endpoints we check before we deploy - uptime, production readiness, the route map, and the list of features still being finished. The same view we use, open to you.
live checkchecking
/health is it up loading
/ready ready for traffic loading
/v1/product/graph routes live 925
closeout still in the works 8
- /health - checking if it's up
- /ready - checking if it's ready for traffic
- /v1/product/graph - loading the live route map
- readiness closeout - loading what's still in the works
DEPLOY SEQUENCE · backend first, then the site
# from repo root npm.cmd run lint:refs npm.cmd run verify:claims-scope npm.cmd run ui:audit:critical npm.cmd run local:surfaces:deep -- --json # deploy backend API target used by Vercel rewrites railway up # deploy public site shell and static assets npx.cmd vercel --prod # post-deploy gate curl https://kolm.ai/ready curl https://kolm.ai/v1/product/graph
A green uptime light means the system is running - not that every feature is finished. We keep those two things apart on purpose, so a working service is never confused with one we still call done.
What's still in the works
We show what isn't done yet.
No buried roadmap. The work that's still in progress - packaged releases, outside verification, published benchmarks - sits right here in the open, next to everything that's already live.
Each item is held behind a readiness gate (a release blocker we won't pass until the proof exists)A readiness gate is a checkpoint a feature must clear before we call it shipped. We keep it closed until there is evidence you can verify, so a claim never gets ahead of the proof. The live count is read straight from /product-readiness-closeout.json.. Right now 8 of them are still open.
Still being finished
We hold our public claims to what's shipped. Packaged releases, outside verification, and published benchmarks stay off the marketing copy until the proof is in.
Nothing private leaks
This page and our public API show counts, routes, and state - never your keys, your provider payloads, or anything else you'd want kept private.
Something looks off? Tell us.
Check your own capture and export state in your control center. Spot an incident, need our readiness evidence, or see something wrong on this page? Email a real engineer at dev@kolm.ai.