Pricing aligned to authority

Experiment for free.
Pay when authority begins.

Evaluate production traffic in Shadow. Pay when Admis becomes the governed authority permitted to change what a production agent may do.

Admis Runtime Preview v0.1 · Production access by invitation

Commercial paths

01Available now

Developer

$0 Free

Build, evaluate and understand the decision boundary before production authority begins.

  • Admis Runtime Preview v0.1
  • SDKs, schemas and adapters as released
  • Local evaluation and Observe mode
  • Shadow experimentation
  • Admissibility traces and decision records
  • Community release updates
View Runtime Preview

No credit card. Production enforcement is not included.

02Production Early Access

Design Partner

Guided 90-day program

Be among the first teams to move Admis from Shadow into production enforcement, with our implementation team alongside you.

  • One consequential production use case
  • Shadow-to-Enforce activation
  • Evidence and identity integration
  • Usage measured through Protected Actions
  • Jointly defined success measures
  • Direct access to the engineering team
Apply for Production Early Access

Limited launch cohort. Production access is by invitation and program terms are agreed before activation.

03Custom

Enterprise

Let’s talk

Govern consequential agent action across production systems, teams and regulated environments.

  • Custom annual agreement plus usage
  • Admis Security, Decision and Compliance scope
  • Central policy, ledger and role-based access
  • Evidence, identity and platform integrations
  • Hosted, VPC or private deployment planning
  • Assurance, retention and support commitments
Discuss your deployment

Institutional and embedded deployments are scoped through the enterprise conversation.

When payment begins

Authority changes
the commercial state.

Admis stays open at the integration edge. Commercial value begins when an organization authorizes it to affect production execution or requires institutional operating controls.

01 · Observe inside Develop

Develop

Free

Build locally, inspect determinations and validate the decision boundary without changing agent behavior.

02 · Production evaluation

Shadow

Free or launch-included

Evaluate real production traffic, record outcomes and tune policy without intervening in execution.

03 · Authority begins

Enforce

Paid production

Authorize Admis to constrain, escalate, quarantine, block or abort consequential production actions.

04 · Institutional operation

Scale

Platform plus usage

Extend governed authority across platforms, environments, evidence systems and organizational controls.

The conversion trigger

Payment begins when Admis is authorized to affect production execution, or when the organization requires enterprise capabilities such as SSO, managed integrations, private deployment, long-term ledgering or assurance.

The usage metric

Protected Actions,
not seats.

Enterprise agreements combine an annual platform commitment, included Protected Actions and usage above the committed volume. Agent count and user seats do not define the core value metric.

Protected Action

A proposed consequential production action evaluated by Admis before execution.

The metric aligns price to the governed decisions that matter, while avoiding a tax on every user, developer or agent instance.

payments.transfer
Move funds
records.delete
Destroy records
access.grant
Change privilege

Enterprise agreements

Priced to the
operating reality.

The agreement reflects where Admis runs, what authority it holds and how much institutional assurance the deployment requires.

Annual platform commitment
+ included Protected Actions
+ usage above commitment
01

Protected Action volume

Expected and peak consequential-action evaluations across production.

02

Platforms and environments

The number of production systems, agent runtimes and governed environments.

03

Product scope

The combination of Admis Security, Admis Decision and Admis Compliance required.

04

Evidence and identity

Enterprise identity, threat, policy, consent and operational evidence integrations.

05

Deployment model

Hosted, VPC, hybrid or private infrastructure requirements and data boundaries.

06

Assurance and signing

Decision attestation, signing and higher-assurance verification requirements.

07

Retention and regulation

Ledger duration, replay requirements and regulatory operating obligations.

08

Support and availability

Implementation support, response commitments and production availability needs.

Product scope

One agreement.
Three control domains.

Products do not function as public price tiers. The deployment is scoped around the control domains the organization needs.

Pre-execution security

Admis Security

Threat, identity, privilege, anomaly, exfiltration and Zero Trust controls applied before execution.

Consequence-aware control

Admis Decision

Distributional evaluation for material actions whose consequences must be assessed under uncertainty.

Executable institutional policy

Admis Compliance

Organizational and regulatory requirements translated into controls applied directly to autonomous action.

Pricing FAQ

Clear before
authority begins.

What can I use for free?
Admis Runtime Preview v0.1, released SDKs, schemas and adapters, local evaluation, Observe mode, Shadow experimentation, traces and decision records. Production enforcement and enterprise operating capabilities require paid access.
When does Admis become paid?
When Admis is authorized to constrain, escalate, quarantine, block or abort production actions, or when an organization requires enterprise capabilities such as SSO, managed integrations, private deployment, long-term ledgering or assurance.
What is a Protected Action?
A proposed consequential production action evaluated by Admis before execution. Protected Actions are the principal usage metric for production and enterprise agreements.
Is pricing based on seats or agents?
No. Enterprise pricing is anchored to an annual platform commitment and Protected Action volume. Platforms, production environments and operating requirements affect scope, but user seats and agent count are not the core value metric.
Is Shadow charged?
Local Shadow experimentation is free. During launch, production Shadow is free or included as part of the Production Early Access Design Partner program. The applicable enterprise agreement will define included production volume before enforcement begins.
How do Admis Security, Decision and Compliance affect pricing?
They define the control scope of the deployment. Security covers pre-execution threat and identity control. Decision adds consequence-aware evaluation under uncertainty. Compliance applies executable organizational and regulatory constraints. The combination is reflected in the enterprise agreement.
Is private or VPC deployment available?
Private and VPC deployment are planned enterprise and institutional options. Availability depends on the deployment program, integration maturity and agreed operating requirements. The team will not describe a route as available before it has reached the appropriate maturity.
How does the Design Partner program work?
Selected teams enter a guided 90-day program centered on one consequential production use case. The program covers Shadow-to-Enforce implementation, evidence integration and jointly defined success measures. Participation begins with an application and deployment review.

Independent decision authority for agentic systems.

Production Early Access

Move from observation
to governed action.