About

Why this exists

We operate a handful of machines across a couple of datacentres, plus the usual rented cloud — a git host, an error tracker, a deploy platform. Keeping a picture of it all meant SSH, a pile of cron jobs, and a Slack channel where alerts went to die.

The tools that fix this properly are priced for companies with a platform team. The tools priced for us each see one side of the fence: your boxes, or your cloud, never both. So we started building the thing we wanted — one pane over both, cheap enough to be obvious.

The part we cared about first

We build for teams, and for the agencies and consultancies who run infrastructure on behalf of several clients at once. That only works if isolation is real. So it was the first thing we built and the first thing we tested: every table is scoped to an organization and guarded by Postgres row-level security, deny-by-default. Another tenant’s row cannot come back, even if our application code has a bug.

Where we actually are

Pre-launch. Authentication, organizations, isolation, and the host telemetry agent work today. The GitHub, Sentry, AWS, and Vercel integrations do not — they are being written now. We are not going to dress that up.

We are taking a small number of design partners: teams who will tell us what is wrong, use it while it is rough, and shape what gets built next. If that sounds like you, apply from the home page. We read every application ourselves.