We are publishing the first stable release of Cuitty: a modular admin platform that runs ten production modules behind one HTTP wire protocol. The modules — audit, configs, costs, deploys, logs, performance, repository, secrets, video, forge — each compile to a single binary, share the same identity layer, and emit the same event stream.
Why now
Most platform teams we talk to land in the same place: a few SaaS vendors, a couple of in-house dashboards, a Slack channel for runbooks, and a half-finished policy doc. The pieces work. The seams do not. Auth lives in one product, audit in another, deploys in a third. Whoever is on call learns five UIs.
Cuitty’s wager is that the seams are the product. A shared identity story (BetterAuth + SpiceDB), a shared event bus, a shared audit chain, and a shared admin shell are what make ten different surfaces feel like one platform.
What ships in 0.x
- The ten modules listed above, runnable via Docker Compose, Helm, or a single
cui serverbinary. - A wire-protocol-first design: every module exposes the same JSON-over-HTTP API. The TypeScript SDK is a thin generated client; the Python SDK is identical.
- Cuitty Cloud, our managed offering, runs the same code. There is no hidden enterprise fork.
What 0.x does not yet ship
We are honest about gaps. The dashboards in the costs module are basic. SAML/OIDC SSO is on Team plans only and the connector library is short. The video module’s Playwright recorder still exits non-zero on certain Cloudflare challenges. We have a public roadmap — see the changelog.
What to read next
- The wire protocol is the product, on why we keep the SDKs thin.
- Compare against Datadog, Grafana Cloud, and Vercel.
- The docs for the quickstart.
If you want to talk to us, the issue tracker is the front door.