Security Specification

Workspace Quotas, Limits & Pay-As-You-Go Architecture

Oridio enforces deterministic, multi-dimensional quota boundaries across all agent swarms. Because autonomous agents can rapidly trigger recursive loops, tool recursion, or unexpected traffic bursts, Oridio isolates usage into two fundamental infrastructure dimensions: Proxy Requests and Hardware Sandbox Compute Minutes.

Plan Quota Matrix

Plan TierWorkspacesProxy Requests / MoSandbox ComputeOverages (Pay-As-You-Go)
7-Day Free Trial1 Workspace100,000 (Eval Cap)300 Mins (5h)Trial guardrail (Fails-closed)
Starter ($29/mo)Up to 5250,000 requests1,500 Mins (25h)$8 / 100k reqs · $0.005/min
Pro ($79/mo)Up to 151,000,000 requests5,000 Mins (~83h)$6 / 100k reqs · $0.0035/min (25% Volume Discount)
EnterpriseUnlimitedCustom VolumeDedicated Bare-MetalBespoke Tiered SLAs

7-Day Free Trial Evaluation Guardrails

New developer signups receive an instant 7-day evaluation period with zero credit card required. During trial, usage is strictly bounded to 100,000 proxy requests and 300 compute minutes to prevent abuse while allowing complete testing of A2A interception, Wasm policies, and Firecracker microVM sandboxes. Once you activate your Starter plan, full allowances (250,000 requests and 1,500 minutes) unlock automatically.

Multi-Workspace Account Pooling

Every workspace created in the Oridio console automatically links to your root organization account through an internal parent_organization_id hierarchy. This means you do not need separate subscriptions for your staging, QA, and production swarms:

  • Starter: Create up to 5 isolated workspaces that all pool from the shared 250,000 monthly request quota.
  • Pro: Create up to 15 isolated workspaces that all pool from the shared 1,000,000 monthly request quota.
  • Each workspace maintains independent API master keys, Wasm security rules, and audit logs, but rolls up to a single consolidated monthly invoice.

Pay-As-You-Go Overages & Volume Discounts

Oridio never cuts off agent execution during unexpected traffic spikes when auto-refill is enabled. Overages are metered precisely per unit:

Starter Plan

Standard Pay-As-You-Go

$8.00 / 100,000 extra requests

$0.0050 / min extra sandbox compute

Ideal for individual builders running prototype and lightweight production agents.

Pro Plan

25% Volume Discount · Built for Scale

$6.00 / 100,000 extra requests

$0.0035 / min extra sandbox compute (30% compute discount)

Engineered for high-throughput swarms; lower marginal rates protect unit economics at scale.

Automated Quota Alerts & Webhook Dispatch

To avoid billing surprises, the Oridio billing engine actively checks workspace utilization every cycle:

  • 80% Utilization (Advisory): Logs a QUOTA_WARNING_80_PERCENT event, dispatches an alert email to the organization owner, and triggers configured webhooks.
  • 95% Utilization (Critical): Dispatches a high-priority QUOTA_WARNING_95_PERCENT alert recommending auto-refill verification.
  • Webhook Payload: When a webhook URL is configured in Settings, Oridio posts an automated JSON payload containing resource utilization, remaining limits, and direct management links.

Fail-Closed Safety & Custom Budget Caps

If Pay-As-You-Go auto-refill is disabled, or if an account reaches its user-defined monthly budget spend cap in Settings, Oridio fails closed. Outbound proxy requests receive an explicit HTTP 429 quota exhaustion response, guaranteeing zero unauthorized credit card charges.

Installation & Setup

Oridio can be integrated either as a drop-in HTTP proxy without modifying your agent codebase, or via our official language bindings for programmatic telemetry and fine-grained Wasm triggers.

$pip install oridio-python && npm install @oridio/sdk
Step 1: Set Proxy Base URL

Route OpenAI/Anthropic SDK client requests through https://proxy.oridio.org/v1.

Step 2: Add Auth Header

Supply your Oridio Master Key via header X-Oridio-Auth: ord_live_....

Architecture & Deep Dive

The Oridio security runtime operates as an out-of-band Layer 7 data plane. Rather than relying on non-deterministic LLM-as-a-judge prompts, security constraints are compiled into Ahead-Of-Time (AOT) WebAssembly binaries evaluated at bare-metal speeds.

Near-Native Wasm
< 0.7ms

P50 evaluation overhead per token packet.

Fail-Closed SLA
99.99%

Global Anycast edge proxy availability.

State Locking
Redlock

Distributed Redis mutex for swarms.

Zero Egress Leakage Guarantee: When a policy trips or a prompt injection signature is detected, Oridio severs the network socket instantly before any data traverses to the upstream provider.

Sample Code & Implementation

from oridio import OridioClient
from langgraph.graph import StateGraph

# Initialize Oridio Edge Gateway client
client = OridioClient(api_key="ord_live_7x9k2m...")

# Wrap your state graph with zero-trust proxy
graph = StateGraph(AgentState)
secure_graph = client.wrap_graph(
    graph,
    budget_limit_usd=50.00,
    pii_redaction=True,
    anomaly_detection=True
)

Interactive Runtime Playground

Edge Mode: Active
{"agent": "finance-bot", "query": "Transfer SSN 000-12-3456"}
{"agent": "finance-bot", "query": "Transfer SSN [REDACTED_SSN]"}(0.7ms p50)

Frequently Asked Questions

Oridio compiles security policies into Ahead-of-Time (AOT) WebAssembly running directly on global proxy edge nodes. Standard regex and token evaluation adds less than 1 millisecond (p50: 0.7ms, p99: < 5ms).

Need help integrating?

Our runtime engineering team can help pair on your agent topology.

Contact support@oridio.org
Previous (Swarm Control)BudgetingNext (Swarm Control) Redlock Mutex