One policy for apps, scripts and AI agents.
The OpenAI-compatible gateway puts machine-to-model traffic under the same rules as the browser: payloads redacted before the provider, non-EU providers blocked, every call in the evidence log.
AI is no longer only typed. It is called.
Internal tools and agents sending data to model APIs.
The challenge
Developers wire model APIs into scripts, integrations and agents. The payloads carry customer data, and there is no browser in the path to inspect it.
Why existing controls miss it
Provider consoles meter usage but apply no organisation-wide data policy, and browser controls never see server-side traffic.
How Deltawall enforces it
Issue gateway keys per application or team. Each key carries a policy: redact payloads before the provider, restrict to EU-resident providers, block the rest.
- Drop-in for OpenAI-compatible SDKs
- Streaming supported
- Same evidence chain as the browser
Four steps. Quoted in writing.
Every tier includes the whole platform. What changes with size is the price per user, the setup scope and the service level.
Paid proof of value
Thirty days in your own browser estate, up to 100 users, on your sector's template. Credited in full against year one.
Tier by headcount
Starter for 100 to 249 protected users, Growth for 250 to 999, Enterprise from 1,000.
One-time setup
Rollout through your MDM, policy tuning to your data, and the works-council documentation.
Annual contract
Per protected user, billed annually. Monthly billing is available with a surcharge.
See it stop real-looking data in a real browser.
A 30-minute technical walkthrough: a prompt redacted, a file stopped, the dashboard, and an evidence pack verified offline in front of you.
No slide deck. Synthetic data only.
