Licensing
Enterprise deployment licensing.
Choose the deployment model that fits your security boundary, throughput, and evidence-retention requirements. Pricing is set per agreement against that shape. This page is what determines it.
Deployment tiers
Open Verifier
Local verification and edge interlock patterns
Verification libraries, middleware, and sidecar patterns that allow customer-side record checks.
Includes: the public verifier package, offline verification of retained records and bundles, and the published trust material. No issuance.
Who it fits: teams verifying records that someone else issued, and anyone auditing what they already hold.
Commercial Issuance
Managed Authorization and Denial record issuance
For commercial AI workflows, DevSecOps, agentic systems, regulated operations, and enterprise automation.
Includes: issuance of Authorization and Denial records against your policies, the enforcement integration at your chosen boundary, customer-held evidence, and independent verification.
Who it fits: teams putting a gate in front of a live workflow where the action has consequences.
Dedicated / Sovereign Deployment
Customer-controlled or authorized integrator-managed boundary
For federal and high-assurance environments requiring local evaluation, private trust material, and offline verification.
Includes: deployment inside your boundary, trust material you control, and verification that never requires our servers in the audit path.
Who it fits: environments where the data, the keys, or the audit path cannot leave your control.
What moves the number
Five things, in roughly the order they matter. Bring your answers to the call and we can scope it in that call rather than after it.
-
Deployment model
Which of the three tiers above. Running inside your own boundary costs differently from managed issuance.
-
Decision volume
How many actions pass the gate, and how that is distributed. A steady rate and a spiky one are not the same problem.
-
Retention
How long records and bundles must stay verifiable, and under whose control they sit.
-
Assurance level
What your environment has to satisfy, and what evidence your auditors and security reviewers need from us.
-
Integration surface
How many workflows and enforcement points are in scope, and what they already run on.
What an agreement covers
Commercial terms
Term, decision volume, overage handling, and renewal. Invoicing and procurement paperwork to suit your process.
Service commitments
Availability and support commitments written into the agreement, sized to the deployment model rather than assumed.
Data and legal
Data processing terms, residency, retention, and the security documentation your reviewers will ask for.
Security and compliance material is on Security and Compliance. What the evidence does and does not establish is on Trust, including the limits, stated plainly.
How to get a number
A pilot puts GeoClear in front of one real workflow in your environment, and the scope of that pilot is what the pricing is set against. Tell us the workflow, the enforcement point, and the timing, and we will come back with a scoped plan and a number for it.