Quickstart · 100% Inside Your VPC

Send your first request. Inspect the result. Understand the boundary.

Follow three separated paths: run a browser example in the interactive lab, verify benign and blocked requests locally, or configure durable execution controls for consequential actions.

STANDALONE IN-VPC CONTAINER SAFE RUST · ZERO GC
# Start the In-VPC Gateway with authoritative tenant and admin key
docker run -d --name sabrix-gateway \
  -p 127.0.0.1:8080:8080 \
  -v $(pwd)/sabrix-records:/var/lib/sabrix/records \
  -e ADMIN_API_KEY="${ADMIN_API_KEY:?Set ADMIN_API_KEY}" \
  -e SABRIX_AUTHORITATIVE_TENANTS="acme" \
  -e UPSTREAM_ADDR="https://api.openai.com" \
  -e SABRIX_FAILURE_MODE=closed \
  ghcr.io/sabrix-ai-inc/sabrix-proxy:latest
Interface Role Traffic Protection Scope
Gateway API Model & Egress Gate /v1/* & Tool Egress Evaluates supported prompts and tool calls against configured rules. Approval thresholds hold supported actions for review; hard limits reject them.
Admin Console Management & Audit /admin & Control API Operator interface for policy configuration, human approval and audit exports. Cryptographic signing depends on signing configuration.

Route Supported Model Traffic with One Configuration Change

Point your existing OpenAI, Anthropic, or LangGraph SDK base_url to Sabrix to inspect streaming prompts and mask sensitive data. (Consequential financial mutations use the separate action execution path detailed below):


      

Approvals & Wire Status Codes

Consequential external mutations (Stripe refunds, cloud updates, database modifications) route through Sabrix. The gateway enforces spend limits, holds high-risk actions for human approval, and prevents duplicate execution across competing retry loops:

Endpoint & Phase HTTP Status Protocol State Wire Meaning & External Effect Next Client Action
POST /v1/chat/completions
Model Gate
200 OK Completed Model tokens scanned in-flight; benign traffic permitted. Consume stream.
POST /v1/chat/completions
Model Gate
403 Forbidden SG-SEC-001 Tool payload attempts cloud metadata SSRF (169.254.169.254); severed before socket connection. Log violation; drop request.
POST /v1/operations/prepare
Prepare Phase (Agent Auth)
200 OK PREPARED Operation registered under tenant policy; validates the caller-supplied bound 32-hex operation_id against tenant identity, recording semantic_intent_digest, bound_wire_digest, and idempotency_key. No outbound dispatch or external effect. Request operator approval grant (if required by policy) or submit claim.
POST /admin/v1/approvals/mint?operation_id={id}
Operator Grant (Human Auth + CSRF)
200 OK MINTED Authenticated human operator mints signed approval token (approval_id) bound immutably to operation ID and canonical parameter digests. Submit approval_id with claim payload.
POST /v1/operations/claim
Dispatch Claim (Agent Auth)
200 OK CLAIMED Worker claims single dispatch permission lease ($R=1, E=1$) using signed approval_id and bound digests. In-flight lease committed to durable store; claim is not an external effect. Invoke forward proxy dispatch command with operation ID.
POST /v1/operations/claim
Concurrency Race (Agent Auth)
409 Conflict HTTP 409
(conceptual: DUPLICATE_FENCED)
Competing worker attempts concurrent claim or duplicate lease on active operation. Second dispatch lease suppressed ($R=1, E=1$). Inspect existing operation state via GET /v1/operations/{id}.
POST /v1/operations/{operation_id}/dispatch
Socket Dispatch (Agent Auth)
200 OK Provider Payload
(e.g. status: succeeded)
Command sent with empty body to ID-bearing path. Gateway reconstructs persisted outbound identity, destination, and arguments, dispatching through forward proxy. Query operation status to verify confirmed state transition.
POST /v1/operations/{operation_id}/dispatch
Tamper / Timeout (Agent Auth)
409 Conflict /
502 Bad Gateway
HTTP 409 / 502
(conceptual: ARGUMENT_MISMATCH / PENDING_RECONCILIATION)
If outbound arguments mismatch signed grant digest, returns 409 before wire transmission. If upstream socket drops mid-request, returns 502 and transitions to Quarantine (unconfirmed). Quarantined; automated retries suppressed until destination reconciliation.
GET /v1/operations/{operation_id}
Status Query (Agent Auth)
200 OK e.g. SettledSuccess
(returns owned record)
Inspects authoritative execution state in durable journal. HTTP 200 confirms the query succeeded; record.status reflects current lifecycle state (e.g. Prepared, Claimed, Dispatching, PendingSettlement, SettledSuccess, or AmbiguousInFlight) alongside confirmed timestamps and provider external_resource_id. Inspect record.status and provider evidence before declaring settlement. Active or ambiguous outcomes must not trigger a fresh dispatch.

Deployment Topologies: Serverless Cloud Run vs. Kubernetes Sidecar

Sabrix can run inside customer infrastructure without Sabrix-hosted traffic processing. Model providers, identity services and secret stores depend on your configuration. Choose a regional gateway or pod-level sidecar:

Google Cloud Run Gen2 (Model Routing Gateway)

Autoscaling regional gateway for model API routing and in-flight stream evaluation:

gcloud run deploy sabrix-gateway \
  --image=gcr.io/sabrix-cloud/sabrix-proxy:latest \
  --region=us-central1 \
  --port=8080 \
  --set-env-vars="SABRIX_FAILURE_MODE=closed"
Note: For durable action execution, configure an authority with storage that survives instance replacement, authenticated operators and a supported provider integration.

Kubernetes Pod Sidecar (Localhost Loopback)

Sidecar sharing the pod network namespace (127.0.0.1):

containers:
  - name: agent-worker
    image: internal-registry.io/agent:v2.1
    env:
      - name: OPENAI_BASE_URL
        value: "http://127.0.0.1:8080/v1"
  - name: sabrix-sidecar
    image: ghcr.io/sabrix-ai-inc/sabrix-proxy:latest
    resources:
      requests: { memory: "32Mi", cpu: "50m" }
      limits:   { memory: "64Mi", cpu: "500m" }
Verification & Diligence

Enterprise Diligence & Verification

Verify core governance scenarios inside your private cloud using local integration tests or request the enterprise qualification materials:

Enterprise Qualification & Diligence Package
Automated benchmark harnesses, crash-injection scripts, SOC 2 / EU AI Act Article 14 controls mapping, and acceptance checklists.
Test Live Lab ↗