Multi-tenancy is a security posture, not a feature.

When your customers are the callers, every mechanism below is the machinery of isolating other people's customers — and, at the end, what we do not claim.

YOUR CALLERS

your backend
a cron job
another agent

Hold a scoped key. Nothing else.

THE GATEWAY — TRAFFIC STOPS HERE

key check → scope check
schema validation
quota · rate limit
run log · usage meter

Every request is authenticated, validated and metered before anything runs.

THE EXECUTION LAYER

reachable only from
the gateway,
by network policy

Enforced, not conventional. Customer traffic never reaches it.

The mechanisms.

self-hosted, by default Prompts, inputs and outputs stay on infrastructure you control. Nothing about your traffic leaves your boundary.

node allowlist Definitions are validated server-side before execution. Seven node types are allowed: input, llm, http, branch, retrieve, transform, output. Unknown types are rejected; anything that would execute caller-supplied code is rejected.

ssrf boundary The http node refuses private and link-local ranges, localhost and cluster-internal names — re-checked after DNS resolution, so a public hostname that resolves inward still fails.

tenant isolation Enforced on every path. Cross-tenant access returns 404, not 403 — it does not leak that a resource exists.

secrets by reference Secrets are referenced by name and resolved server-side. They are never embedded in a flow definition and never appear in run history.

keys stored hashed Shown once at creation, displayed by prefix afterwards, revocable with immediate effect.

network boundary Only the gateway may reach the execution layer, enforced by network policy — not by convention.

The same service runs CortexLabs' own products.

What we do not claim.

Orchent holds no SOC 2, HIPAA or ISO 27001 certification, and publishes no uptime SLA. If your procurement requires those today, we are not your vendor today. What we offer instead is the posture above, on infrastructure you control — where your existing controls, and your existing certifications, already apply.

We do not train on your data.