day to day
How we operate. In plain English.
This is the page we wish other vendors had. What we do, what we don't, and how you can expect us to behave when something matters.
we will not
compromise on
What we hold to.
- 01 One product at a time.
We finish the product in front of us before we let ourselves think about the next one. Roadmaps follow the work, not the other way around.
- 02 Narrow until justified.
Every feature has to earn its place against the cost of supporting it for years. The default answer is no.
- 03 Honest scope, plain copy.
If something is not in v1, we say so on the page. If a customer is asking for it, we say that too. No marketectures.
- 04 Boring deployment.
Single managed runtime per product. Documented runbooks. Backups, retention, and on-call written down before launch.
- 05 Owner-operated.
A small team, reachable by email, answering in working days. No support tier wall.
- 06 Suite, not platform.
We may add a second product. We may add a third. We will not pretend they exist before they do, and we will not glue them into a monolith.
matters
The deliberate no's.
We will not bolt SSO, MFA, PAM, governance and CIEM under one roof to pad a deck.
No third-party integrations sold under our name. Each product owns its surface.
Repo-band or seat pricing, posted on the page, cancellable from the portal.
If a model improves a finding, we use one. We do not retrofit chat onto the product.
We will not publish 'companies served' counts that lump in trial signups.
If product scope grows, we say so on the changelog with a date.
visible > surprising
How we ship.
Every Friday. Bug fixes, small UX improvements, copy edits. Posted to the changelog.
One meaningful behavior change per month. Documented before it ships, tested in PRs.
A scope review. We re-read the v1 promises and say where we drifted.
last quarterly scope review · 2026 Q1 · drift: none material