Back to vendors
O

OpenBox AI

Also known as: OpenBox AI Trust Platform

Visit site
Entry priceGrowth free to start · Enterprise custom quoteFull pricing detail

Runtime governance layer that wraps AI agents built on Temporal, LangChain, CrewAI, Mastra and other frameworks, checks each operation against guardrails, policies and trust tiers before it runs, routes risky actions to human approval, and signs every session into a tamper-evident proof certificate.

OpenBox is a runtime governance layer for AI agents. It wraps an agent the customer already runs, on Temporal, LangChain, LangGraph, CrewAI, Deep Agents, Mastra, n8n or CopilotKit, or through OpenRouter, and checks each operation before it takes effect, returning one of four verdicts (allow, block, require approval, or halt the session). Governance runs as a lifecycle of five phases: assess, authorize, monitor, verify and adapt.

Each agent gets a risk profile scored on fourteen parameters across base security, AI-specific and impact categories, which sets its starting trust tier, and a trust score that moves with its compliance, its goal alignment and its approval record. Four tiers set how tightly an agent is controlled, and an untrusted band suspends it. Controls combine guardrails for PII, harmful content, toxicity and banned words, OPA/Rego policies for permission checks, and behavioral rules that catch patterns across several steps. Operations that need a person go to an approvals queue where reviewers approve, reject or escalate them.

Session replay, a monitor for invocations, tokens, cost and errors, and an LLM-scored alignment score against each agent's stated goal show what the agent did. Each session's events are hashed into a Merkle tree and signed as a tamper-evident proof certificate, through AWS KMS by default or the customer's own attestation service. Every agent carries a decentralized identifier and a signing key separate from its API key, and admins manage access through roles and teams.

OpenBox fits teams that already run agents on one of those frameworks and need enforceable controls and audit evidence around them. It is a governance layer, not an agent builder. It does not orchestrate workflows, ground agents in knowledge, give them memory or connect them to business systems. The platform runs as a hosted service, with custom deployment offered only on the Enterprise plan.

Vendor details

Canonical URL

https://www.openbox.ai

Category

Agent infrastructure

Subcategory

Runtime governance and trust layer for AI agents

Funding status

Independent. OpenBox's launch release of March 31, 2026 announced a five million dollar seed round led by Tykhe Ventures, with Tykhe general partner Prashant Malik backing the round.

Company status

independent

Use cases & customers

Primary use cases

Runtime policy enforcement on agent actions before they executeCryptographic attestation and audit trails as governance evidenceHuman approval for high-risk agent operationsTrust scoring and goal-drift detection across an organization's agents

Target customers

Regulated enterprises deploying AI agentsSecurity, compliance and risk leaders governing AI agentsAI platform teams running agents on Temporal, LangChain, CrewAI or Mastra

Deployment options

Cloud

Integrations

SDKs and plugins for Temporal (Python plugin), LangChain, LangGraph, CrewAI and Deep Agents (Python), Mastra and CopilotKit Runtime v2 (TypeScript), an n8n community node, and an OpenRouter SDK with routing policies and proof of routing. Each connects to the hosted endpoint core.openbox.ai with a per-agent API key. Cursor and OpenClaw integrations are coming soon. Proof certificates sign through AWS KMS by default or through the customer's own attestation service.

In practice

An agent is about to call an API it should not. OpenBox intercepts the operation, checks it against the agent's guardrails, policies and trust tier, and blocks it before it executes rather than flagging it after the damage.

A bank must show regulators that its agents are governed. OpenBox produces tamper-evident proof certificates, hashing each session's events into a signed Merkle tree ready for inspection.

An operation exceeds what the agent's trust tier allows. OpenBox pauses it and routes it to a reviewer in the approvals queue, and the approval record feeds the agent's trust score.

Agentic Index coverage score

6.0 / 14 capabilities · 43%

Integrations & Tool Calling Partial

SDKs and plugins wrap agents built on Temporal (a Python plugin), LangChain, LangGraph, CrewAI and Deep Agents in Python, and Mastra and CopilotKit Runtime v2 in TypeScript. An n8n community node and an OpenRouter SDK round out the set. Each operation the agent takes passes through OpenBox for a verdict. These integrations govern actions the customer's own framework takes. Agents cannot take authenticated action in an outside system through OpenBox. Cursor and OpenClaw integrations are coming soon.

SourceOpenBox, docs.openbox.ai/getting-started and /developer-guideread 2026-09-25

Workflow Orchestration Not documented

The customer's framework, such as Temporal, LangGraph or CrewAI, owns the workflow, its steps and its handoffs, and OpenBox governs those runs without running them. A HALT verdict cancels the framework's workflow. Multi-Agent Sessions is a view of each team's runs. OpenBox names no workflow model of its own.

SourceOpenBox, docs.openbox.ai/core-concepts/governance-decisions and /administration/organization/teams/multi-agent-sessionsread 2026-09-25

Knowledge Grounding & RAG Not documented

OpenBox is a governance layer around the customer's agent, and it names no way to index or retrieve the customer's documents for the agent to ground its answers on. Guardrails inspect the agent's inputs and outputs.

SourceOpenBox, docs.openbox.ai/overview and the docs index (llms.txt and llms-full.txt)read 2026-09-25

Human Oversight & Guardrails Full

When an operation crosses a risk threshold, a policy calls for review or the agent's trust tier requires it, OpenBox returns REQUIRE_APPROVAL. The operation pauses and appears in the Approvals queue, where a reviewer approves, rejects or escalates it. An unanswered request expires. Who approved or denied, and when, is recorded with the decision.

The Adapt tab shows each agent's pending approvals with risk tier, semantic action type and triggering rule, plus approval history and approval rate. Chained guardrails screen the inputs and outputs of every operation, and BLOCK and HALT verdicts stop an action or end the session. Each framework SDK has its own way of enforcing these verdicts.

SourceOpenBox, docs.openbox.ai/core-concepts/governance-decisions, /trust-lifecycle/adapt, /trust-lifecycle/authorize/guardrails and /administration/compliance-and-auditread 2026-09-25

Security, Identity & Governance Full

Admin, Developer and Viewer roles are set under Organization > Permissions. A Viewer can see agents, logs and reports but cannot change anything. Teams decide which agents a member can see and which sessions they can act on. Each agent also carries its own cryptographic identity, a DID and an Ed25519 signing key kept separate from its API key. OPA/Rego policies run stateless permission checks on every agent operation, giving least privilege tool access. An organization audit log records who changed what. OpenBox names no identity provider integration such as SSO, SAML or SCIM.

OpenBox shows ISO 27001, ISO 42001 and NIST badges on its site, but none links to a certificate, auditor, report or date. It names SOC 2, ISO 27001 and GDPR only as frameworks it maps its customers' audit evidence to.

SourceOpenBox, docs.openbox.ai/administration/organization, /administration/organization/teams, /core-concepts/agent-identity and /trust-lifecycle/authorize/policies, plus the openbox.ai footer and /solution/complianceread 2026-09-25

Observability & Auditability Full

Session Replay steps through an agent session event by event, showing every tool call, governance decision and full JSON payload. The Monitor tab tracks each agent's invocations, response time and token use, along with cost and errors, over selectable time ranges.

Every governance decision goes into an immutable audit trail with verdict, reason, workflow and run IDs and approval metadata, and the trail exports on demand. Each session's events are hashed into a Merkle tree and signed into a tamper evident proof certificate, through AWS KMS by default or the customer's own attestation service. An organization audit log records user and configuration changes, separate from the runtime traces.

SourceOpenBox, docs.openbox.ai/trust-lifecycle/session-replay, /trust-lifecycle/monitor, /administration/compliance-and-audit and /administration/attestation-and-cryptographic-proofread 2026-09-25

Memory & State Persistence Not documented

Trust score history, approval history and behavioral rules that track patterns over several steps all describe the agent. OpenBox applies them as governance rules, and the agent never reads them as context for its decisions. The Enterprise plan includes Universal Agent Memory Governance, which governs the customer's memory instead of providing one, and OpenBox describes it no further. OpenBox names no memory layer or state the agent reads across runs.

SourceOpenBox, docs.openbox.ai/core-concepts/trust-scores, /trust-lifecycle/authorize/behaviors and openbox.ai/pricingread 2026-09-25

Deployment & Data Residency Partial

The Enterprise plan includes Custom Deployment and SLAs, with no named environment, region or way to choose one. Every SDK guide points the agent at the hosted endpoint core.openbox.ai. OpenBox publishes no region list and names no self hosted or customer cloud option.

External attestation lets the customer sign proof certificates with its own attestation service or a Trusted Execution Environment. That choice sets where the signing key sits, not where OpenBox runs. OpenRouter routing policies can restrict model providers by data residency, which applies to the customer's model traffic, not to where OpenBox itself is deployed.

SourceOpenBox, openbox.ai/pricing, docs.openbox.ai/getting-started/deep-agents and /administration/attestation-and-cryptographic-proofread 2026-09-25

Prebuilt Agents, Templates & Packs Partial

Four guardrail types, covering PII detection, content filtering, toxicity and banned words, can be chained into a pipeline for each agent. Three preconfigured risk profiles (low, medium and high) set an agent's starting trust tier. These are modules of one governance engine that the customer assembles, plus presets for settings. OpenBox names no catalog of ready made agents, workflows or policies.

SourceOpenBox, docs.openbox.ai/trust-lifecycle/authorize/guardrails and /trust-lifecycle/assessread 2026-09-25

Triggers & Channel Coverage Not documented

The customer's own runtime, such as Temporal, LangChain or n8n, starts and runs the agent. OpenBox's SDKs wrap that agent, and every governance evaluation responds to an operation the agent began. Alerts on trust tier changes and goal drift flag agents for people to review, and they do not wake an agent.

SourceOpenBox, docs.openbox.ai/getting-started and /dashboard/alerts; docs.openbox.ai/dashboard/alertsread 2026-09-25

Model Flexibility & Routing Not documented

The agent's framework chooses its model, and OpenBox evaluates the operations that result. OpenBox offers no model choice of its own for the customer's agent. The OpenRouter SDK's routing policies are Rego rules that allow or deny model providers and record proof of where each call was routed. They govern the customer's model traffic and offer no choice inside OpenBox. The Alignment Score uses an LLM evaluation that OpenBox calls configurable, and it names no provider list or way to select one.

SourceOpenBox, docs.openbox.ai/developer-guide/openrouter/routing-policies and /core-concepts/trust-scoresread 2026-09-25

APIs, SDKs & MCP Extensibility Full

SDKs for the platform include a Python Temporal plugin with a full API reference, Python SDKs for LangChain and LangGraph, CrewAI and Deep Agents, and TypeScript SDKs for Mastra and CopilotKit, plus an n8n community node and an OpenRouter SDK. Each comes with configuration options, error codes and an event model.

They authenticate to the hosted endpoint core.openbox.ai with API keys for each agent (live and test) and send each agent operation for a governance verdict. OpenBox names no REST API reference and no MCP server of its own. The MCP mentions in its docs belong to the Temporal demo agent.

SourceOpenBox, docs.openbox.ai/developer-guide/temporal-python/sdk-reference, /developer-guide/langchain and /getting-started/copilotkit/add-openbox-to-copilotkitread 2026-09-25

Testing, Debugging & Optimization Partial

The Verify phase scores each session's actions against the agent's declared goal with an LLM evaluation that OpenBox calls configurable. Results show as an Alignment Score from 0 to 100 percent, with check counts, a trend line against a threshold (70 percent by default) and logged drift events.

The score tracks the customer's agent's behavior over time, and it runs only on live sessions. OpenBox names no way to test an agent against fixtures, mocks or datasets before production, and no red teaming before deployment or CI/CD checks. The Adapt phase tunes governance rules, not the agent, and the Assess phase is a risk questionnaire.

SourceOpenBox, docs.openbox.ai/trust-lifecycle/verify, /core-concepts/trust-scores and /trust-lifecycle/assessread 2026-09-25

Browser & Computer Use Not documented

Agent operations are governed, but OpenBox itself operates no browser or computer. Browsers appear only as steps in two demo walkthroughs.

SourceOpenBox, docs.openbox.ai/overview and the docs index (llms.txt and llms-full.txt)read 2026-09-25

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Product updates

·Deployment / data residencyVerified

OpenBox's runtime governance platform for AI agents can now be bought on AWS Marketplace and run entirely inside the customer's own AWS account and VPC. A signed Helm chart and an AWS CDK template set it up on Amazon EKS, and endpoints can be limited to an IP allowlist or kept inside the VPC. Each session's proof certificate is signed with a key in the customer's own AWS KMS or through an external attestation endpoint.

Bears on: Deployment / data residency

View source
·Security / enterprisePartially Verified

Agents that use Okta for their identity can now start on OpenBox with just its API address, an API key and the agent's Okta private key, with the rest fetched automatically, as of version 1.4.0 of the Python SDK. The SDK checks the key against the credential OpenBox holds before the first governed request and refuses to send on a mismatch.

Bears on: Security / enterprise

View source
·Security / enterprisePartially Verified

OpenBox expanded its runtime governance platform into a framework-agnostic control layer. The update introduces integrations for over eight frameworks including LangChain, LangGraph, CrewAI, and Temporal. It adds capabilities such as pre-execution policy enforcement, session replays, human approval workflows, and tamper-proof audit trails mapped to the EU AI Act.

Bears on: Security / enterprise

View source
View all 3 OpenBox AI updates →Tracked since Jul 2026 · Verified from public vendor sources

Pricing

Growth free to start · Enterprise custom quote

not published; Growth is free and Enterprise is quoted

Free tier

What is public

Plan names, the free Growth plan and each plan's feature list are public. Enterprise rates, the billing unit and any Growth limits are not.

Billing mechanics

Two plans on the pricing page: Growth at Free and Enterprise at Custom (Get Quote). The Growth plan's limits and the Enterprise billing unit are not published.

Cost watchouts

Proof certificates sign through AWS KMS by default, or through the customer's own attestation service or Trusted Execution Environment, so external signing infrastructure is the customer's own cost. Human-in-the-loop controls are listed on Enterprise only.

Variable cost rationale

The pricing page publishes no metered unit on either plan: Growth is free and Enterprise is quoted with unlimited agents and users, which points away from usage metering. The billing unit itself is not published.

Additional watchouts

Human-in-the-loop controls, advanced risk scoring, compliance reporting and custom deployment appear only on the Enterprise card, so the free Growth plan covers the SDK, audit trails, policy engine, guardrails and basic observability.

Sales call required

Mixed (some tiers require a call)

Free / trial

The Growth plan is free to start, with sign-up at platform.openbox.ai; no Enterprise trial is published

Lowest paid plan

Not published; Enterprise is by quote

Key ambiguities

Growth plan limits (agents, users, sessions) are not published; Enterprise lists unlimited agents and users, which implies Growth has limits.

Missing data

Enterprise rates and billing unit, and any Growth plan limits.

Agentic Index verified 2026-09-25

Alternatives to OpenBox AI

The closest documented capability profiles to OpenBox AI among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

  • Lakera7.0 / 14Fuller documented coverage on Deployment & Data Residency and Testing, Debugging & Optimization
  • Prefactor4.5 / 14A lighter documented profile than OpenBox AIOpenBox AI vs Prefactor →
  • Coral5.5 / 14Adds documented Knowledge Grounding & RAG
  • Dome Systems6.5 / 14Adds documented Model Flexibility & Routing
  • Kernel8.5 / 14Adds documented Workflow Orchestration and Browser & Computer Use
  • Nevermined4.5 / 14Fuller documented coverage on Integrations & Tool Calling

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.