Gateway · request-time control
Each AI call your tools send through it, decided and recorded.
The gateway runs in your network, between your tools and the model providers. It decides each call under the signed policy from the Control Plane, and records the decision.
How it works
What it can do
- Decide each call sent through itAllow, redact, route, redact and route, or refuse, under one signed policy.Policy
- Start in record-onlyRecord only, Advisory or Enforce. The mode is part of the signed policy, so changing it takes a second person.Policy
- Mask personal dataMasked before the call leaves. The record keeps where it was and its type, never the text.Ledger
- Record every decisionEach record is chained to the one before. Change one and the chain names it.Ledger
- Emergency stopsStop a run, a unit your tool labels (X-Saible-Unit), a workload or an application at every gateway, in every mode, record-only included.Emergency stops
- A key for each toolSaible knows which tool made which request. A request with an unknown key is not forwarded.Registry
- Pulls, never pushedEach gateway pulls the signed policy and the stops. Nothing is pushed into your network.Gateways
- Watch it as it happenedReplay a window of records step by step, from records that hold no text. It opens on the newest emergency stop.Gateway → Overview
- Routing and cache, measuredRouting vs usual model is an estimate at list price over calls to auto or an alias only; a named model is never swapped. The cache runs in shadow: it counts, it serves nothing.Gateway → Overview
- Install it yourselfA Terraform module for ECS Fargate in your AWS account, or Kubernetes manifests (not yet run on a cluster).Gateways
Three modes
Start in record-only: nothing changes for your tools, and you see what the policy would have done.
Record onlyrecord_only
Every request is forwarded unchanged to its model's default endpoint, and everything the policy would have done is recorded. Emergency stops and unknown models or keys are refused in every mode.
- Forwarded unchanged, stops aside
- Personal data redaction applies
- Rules reroute or refuse
- Emergency stops refuse
- Each decision recorded
Advisoryadvisory
The rules only record what they would have done; redaction of personal data still applies before sending.
- Forwarded unchanged, stops aside
- Personal data redaction applies
- Rules reroute or refuse
- Emergency stops refuse
- Each decision recorded
Enforceblocking
The rules are applied: a request is redacted, rerouted or refused as the policy says, and recorded.
- Forwarded unchanged, stops aside
- Personal data redaction applies
- Rules reroute or refuse
- Emergency stops refuse
- Each decision recorded
Do it
- 1On Gateways, click Add a gateway and issue its credential.
- 2Install the gateway in your network, in record-only.
- 3Point one tool's SDK at the gateway, with the tool's Saible key.
- 4Send one request and open its record in the Ledger.
Gateway topics
- Gateway01A request, through the gatewayEvery request takes the same path. The policy decides; the record is written on every path, or a gap record says it was not.
- Ledger02What a decision record holdsWhere personal data was found and what was decided. Never the text itself.
- Control03Emergency stopsStop a run, a workload or a tool in every mode, record-only included.
- Access04Keys and who holds themFive keys. Each one opens one door.