Argus comes out of years running multi-tenant SaaS where every "roll out for tenant B" was a custom rule, a Slack thread, and a held breath. We watched audit questions turn into archaeology. We watched the same rollback drill cost the same engineers the same Friday night, three quarters in a row.
The thesis is small: the flag isn't for users, it's for tenants. Once tenant scoping is mandatory at the API surface, every downstream property — audit, isolation, blast radius, pricing — falls out for free. We're picking three design partners to ship it with.
If you've shipped production stream / log infrastructure or a developer-facing SDK that engineers actually liked, read the seats and write to hello@projectargus.cloud.
You own the data plane. Postgres row-level (post-PMF), streaming change-log, eval latency budget, multi-region reads. The thing that "cannot lose a write" is yours to make true.
You own the SDK, the dashboard, and what installation feels like at minute zero. Time-to-first-flag is your number. If a TypeScript dev doesn't smile in five minutes, you didn't ship.