Skip to content

faq

The questions engineers actually ask.

Six answers, no hedging. If yours is missing, ask a founder directly.

Questions we get from engineers.

01What exactly sits in the request path?+

An HTTP endpoint your runtime calls immediately before a tool executes, instead of letting the call go straight to the MCP server. The guard judges the call and answers allow, escalate or block. If it cannot evaluate at all it returns 503, and what happens next is your configured fail mode — fail-closed (the default) means the call does not execute.

02Does the judge model see our tool calls?+

On the hosted tier, yes: the call and the policy context go to the judge to produce a decision. On the BYOK tier your judge key is used and only you hold it. On the self-hosted tier nothing leaves your network at all.

03What happens when the guard is down or wrong?+

Fail behaviour is explicit, and you choose it. The default is fail-closed: an unevaluable call is a 503 and the call does not execute. A rule can instead declare fail-open, in which case an outage yields an allow carrying a degraded reason on the decision record — never a bare silent pass. Rate limits and the spend cap return 429. If a decision looks wrong you can see exactly which rule or signal produced it in the decision record.

04How do rules get written?+

As one plain-English sentence each, with a constraint type and a severity, compiled into a deterministic policy the guard enforces on every evaluated call. You write them in the console or over the API, start from a shipped pack, or we compile them with you at onboarding. Rules are judged on meaning rather than matched as patterns, so one rule reaches every tool and argument shape that means the same thing. At runtime the judge applies that policy and never invents it.

05Will it catch an attack we didn't anticipate?+

It will, if a rule describes the harm rather than the specific technique — and that is how the shipped packs are written. 'Never transmit customer data to a destination outside the organization's approved service list' covers the email, the webhook, the file upload, and the vector that ships next quarter. What no rule describes, nothing blocks: the guard enforces your policy and never invents one. Write rules about outcomes, not about techniques.

06Can we run it ourselves?+

Yes. Self-hosted runs the same container image with a signed license, in your own VPC, with your own database. Talk to us for a license and deployment notes.

07How does billing count?+

Per decision, per calendar month (UTC). The relay counts each evaluation once, decisions reported over the reporting contract count once each, and retries or duplicate batches never double-count. Decisions past the included allowance are metered against your spend cap at the plan rate and settle with the billing cycle — never a per-call invoice. Reaching the cap returns 429.

Ask a founder directly at hello@orithos.com, or read the full contract in the documentation.