Skip to main content

Licensing

Licensed to your enterprise. Deployed in your cloud.

GeoClear is not a subscription you sign up for. It is licensed to an organisation and deployed inside that organisation's own cloud account, alongside the workflows it protects.

Two ways to buy

There is no subscription, no self-serve plan and no price list. GeoClear is bought in one of two ways, and both are agreed with you directly.

A paid evaluation

A fixed fee covers a set number of transactions in one real workflow in your environment. A transaction is one consequential action that GeoClear evaluates, producing one operational evidence record.

Verifying a record that already exists is not a transaction and is never charged. If the evaluation reaches its number, it pauses and we agree the next scope with you; it never runs on into open-ended charges. The fee and the number are set for each evaluation.

An enterprise or federal contract

Negotiated for your organisation: how many deployments, which capabilities, retention, assurance level and support, under terms that fit your procurement process rather than ours.

One deployment model

GeoClear runs where your workload already runs: your cloud account, on AWS, Google Cloud, Azure or OCI, in your region and under your tenancy. There is no shared multi-tenant service, and there is no version of this where your evidence sits in our systems.

Where GeoClear runs GeoClear is deployed inside the customer's own cloud account, alongside the customer's workflow and their retained evidence. GeoClear the company sits outside that boundary and supplies only licensed software and the material needed to verify records independently. YOUR CLOUD ACCOUNT AWS, Google Cloud, Azure or OCI. Your region, your tenancy. Your workflow the agent proposes an action GeoClear verifies and issues the record Your evidence retained and verifiable offline Your data does not leave this boundary. Verification never needs to call out of it. GEOCLEAR, THE COMPANY Licensed software Verification material Support and updates What we do not hold Your dataYour evidenceA place in your audit path Licensed to run where your workload already runs.
What sits inside your boundary, and what we supply from outside it.

Your account, your keys

A deployment in your account holds its own signing key and issues records under its own identity. Your evidence is yours, not ours with your name on it.

Your data does not move

The workflow, the records and the retained evidence stay inside your boundary. We are not in the path and not in the audit trail.

Verification without us

Records and bundles can be checked offline by someone who does not trust us. That property is the point, and it survives us.

What the licence covers

The software

The verification and issuance components, deployed into your environment, with the infrastructure definitions to stand them up and stand them up again.

The verification material

What your auditors and your own systems need to check a record independently, including offline, without a call to us.

Deployment and integration

Done with your team as part of the engagement. The enforcement point is in your systems, so getting it in the right place is joint work.

Support and updates

Written into the agreement and sized to the deployment, rather than assumed from a tier.

Security and compliance evidence

The documentation your reviewers will ask for. See Security and Compliance.

Commercial and legal terms

Term, data processing, residency, retention and renewal, to suit your procurement process rather than ours.

What determines the number

Bring your answers to the call and it can be scoped in that call rather than after it.

  1. How many deployments

    Environments and accounts in scope, and whether that is one business unit or several.

  2. Decision volume

    How many actions pass the gate, and whether that is steady or spiky. The two are not the same problem.

  3. Which capabilities

    Which of the capability domains are in scope. Their current maturity is stated plainly on evidence profiles.

  4. Retention

    How long records and bundles must stay verifiable, and under whose control they sit.

  5. Assurance level

    What your environment has to satisfy, and what evidence your auditors and security reviewers need from us.

  6. Integration surface

    How many workflows and enforcement points are in scope, and what they already run on.

How to get a number

We do not publish a price list, and we are not going to put one up that we would have to walk back in the call. The paid evaluation above puts GeoClear in front of one real workflow in your environment, and the scope of that evaluation is what it is priced against. Tell us the workflow, the enforcement point and the timing, and we will come back with a scoped plan, a date and a number for it.