We don't publish plans. Platform cost depends on reasoning budget, deployment isolation, and compliance scope — all of which are scoped per customer. A thirty-minute call gives you a number you can defend.
We use the same four levers to price every deployment. On the call we walk through each one with you.
Which Griffin variants you call — Lite, S, M, L, or Zero — and how often. Inference cost dominates platform cost, not headcount.
Shared cloud, dedicated VPC, on-prem, or fully air-gapped. Isolation posture changes the architecture and the price.
Which packs you switch on — SOC 2, ISO 27001, NIST, DORA, NIS2, FedRAMP, STQC — and the audit-evidence depth you need.
Repos, container registries, build systems, MCP servers, third-party vendors. The surface area we scan defines the workload.
A discovery call is free and non-binding. You leave with a clearer picture of fit — and, if you want one, a written proposal in under two weeks.
Twenty to thirty minutes. We learn your stack, your regulatory posture, and what success looks like for your team.
Our solutions engineer walks through deployment shape, reasoning budget, and integration points with your team.
A written proposal scoped to your environment — line items you can defend, no surprise add-ons at renewal.
Time-boxed pilot on a real repo or workload, then phased rollout with a dedicated technical account manager.
Platform cost is dominated by reasoning budget and deployment isolation — both of which are scoped per customer. A public price sheet would be either misleading or unhelpfully wide. A thirty-minute call gives you a number you can defend internally.
Nothing. A discovery call is free and non-binding. You leave with a clearer picture of fit, a scoped architecture, and — if you want one — a written proposal.
Most customers move from discovery to written proposal in five to ten business days, depending on the depth of scoping and how regulated your environment is.
Yes. We support fully air-gapped, VPC-isolated, and sovereign-cluster deployments — including offline vulnerability-database sync, on-prem GPU sizing support, and customer-controlled key material. Talk to our sovereign team on the call.
Whoever owns application security, supply-chain risk, or platform engineering on your side. We often see an AppSec lead plus a platform engineer — but a single technical decision-maker is enough to start.
Yes. We carry SOC 2, security documentation, and DPAs ready to share under NDA, and we respond to standard procurement questionnaires as part of the proposal stage.
Tell us about your stack, your regulatory posture, and what success looks like — we will scope the deployment and the price that fits.