Why our pricing
looks like this.
Pricing is a hypothesis to validate with design partners, not a final answer. Here is the reasoning behind every decision — and what we are deliberately deferring.
We sell memory, not verification
The CLI verifies. The platform remembers, audits, and proves. A free command-line tool can check a build once; it cannot give a team a shared history of how faithful their software has been to its specifications over time. We align price with the thing customers cannot rebuild themselves.
Open core
Free forever: the CLI, the GitHub Action, bring-your-own-key, unlimited local evaluations, MIT licensed. Paid: the hosted platform, dashboard, evaluation history, audit trails, team collaboration, and governance. This is how GitHub built a business on Git and Datadog on open-source monitoring. We draw the line deliberately: the commodity (the CLI) is MIT, and the defensible layer (the dashboard, audit, and governance) is proprietary — so no cloud provider can resell the valuable part.
Bring your own key
BYOK is our wedge, not our friction. CodeRabbit — the category anchor — has no BYOK and retains your code for seven days; data residency is the requirement that pushes engineering orgs onto expensive enterprise tiers elsewhere. Norma gives that posture by default at the Team tier: verifications run on your own provider key under your own retention terms. Norma passes the request through to your provider and returns the result without retaining your code or storing the model's response — you own the vendor relationship and the data; we never keep a copy. Because we don't resell tokens, production inference is your bill, not our margin — a clean, high-margin platform, and the security story that wins the deal, three tiers earlier than the incumbent offers it.
Value before the key ask
The trial runs on Norma's own inference, bounded so our cost stays forecastable. You see drift caught and a Spec Fidelity score before you are ever asked for a key — the "aha" comes first, the setup second. When you convert, an admin sets one org-level key once and every engineer inherits it; no per-seat key friction. We never gate first value behind setup.
The positioning ladder
The category we claim grows as we earn the right to claim it. We lead with the wedge and grow into the larger category, rather than overreaching on day one.
- Stage 1 now we are hereSpec Fidelity
Does the software match the intent? A clear, novel, ownable wedge that avoids the crowded code-quality category.
- Stage 2 nextThe Audit Layer for AI-generated software
Provenance, traceability, accountability, governance. A materially larger category.
- Stage 3 eventuallyThe System of Record for AI software delivery
Institutional memory, historical truth, compliance, organizational trust. Credible only once the records exist.
What we watch first
Pre-product-market-fit, the pricing table is the least important thing on the page. MRR and ARPU are lagging outputs. These four leading indicators decide whether the model works:
- Time to first hosted Spec Fidelity report (activation).
- Repositories per account (adoption).
- Seats per account (expansion).
- Weekly active accounts (retention).
Operating rules
No fabricated metrics, testimonials, logos, or customer counts appear on the pricing page or anywhere else. We do not imply customers or numbers we do not have. The first-25 cap on the Design Partner program is real and will be honored.