ENTROVIKPlan a pilot

Editions and engagement

Start where you are. Scale without rebuilding governance.

Evaluate the complete platform, deploy a paid single-node foundation, then expand to corporate identity, high availability, private policy supply chains, and enterprise operations.

Scope an enterprise pilot ↗Try policy enforcement →

Choose the operating model

One runtime. Three ways to adopt it.

Pricing scales with the governance surface, operational requirements, and support model—not with surprise per-policy tolls.

EVALUATION

Prove it in your environment

30 daysVendor-signed, non-production entitlement

Evaluate the complete enforcement and control-plane experience against real policy requirements before committing.

  • Full platform capability
  • OpenAI, Anthropic, Gemini, Ollama, and vLLM paths
  • WASM policies, Playground, and simulation
  • SQLite or PostgreSQL evaluation
  • Conversion without reinstalling
Request an evaluation →
SMALLER PRODUCTION TEAMS
STARTER

Paid single-node governance

AnnualPredictable proprietary license

For smaller organizations centralizing production AI traffic without enterprise identity or clustered operations.

  • One organization and one Entrovik instance
  • SQLite or single-node PostgreSQL
  • Core policies, bundles, CLI, and admin UI
  • Explainability, audit, and metrics
  • Standard updates and support
Discuss Starter ↗
ENTERPRISE

Organization-wide control plane

AnnualPriced to deployment scope

For organizations operating Entrovik as governed, highly available security infrastructure across teams and applications.

  • OIDC, SAML, SCIM, granular RBAC, and multi-tenancy
  • PostgreSQL and horizontal availability
  • Private repositories, policy signing, and trust
  • Advanced audit retention and analytics
  • Enterprise SLA and upgrade planning
Discuss enterprise scope →

Commercial clarity

What determines enterprise scope.

We size an engagement around what must be governed and operated. We do not require you to expose prompt content to calculate a quote.

TRAFFIC

Applications and throughput

Number of protected applications, deployment environments, policy execution volume, and regional topology.

CONTROL

Organizations and identity

Tenant boundaries, administrator groups, corporate identity, access model, and separation-of-duty requirements.

ASSURANCE

Audit and operations

Retention, exporters, HA, support response, private policy repositories, and supply-chain controls.

Buying FAQ

Questions procurement and platform teams ask.

Is provider usage included?

No. Entrovik governs traffic to your provider accounts. Provider model charges remain between your organization and the provider.

Is Entrovik open source?

No. Entrovik is proprietary commercial infrastructure. Evaluation, Starter, and Enterprise installations use vendor-signed deployment entitlements.

Can we start on SQLite and move to PostgreSQL?

Yes. Starter and evaluation deployments can begin on SQLite, then use the validated export/import migration path when HA and multiple replicas become necessary.

What happens after a pilot?

You receive measured results, policy and deployment recommendations, unresolved risks, and a production plan. A pilot is intended to produce a go/no-go decision—not an indefinite proof of concept.

Make the buying case

Put governance in front of a real AI workflow.

We’ll define a bounded pilot with technical, security, and executive success criteria.

Plan the pilot ↗Review trust posture →