Your engineers want frontier models. Your regulator wants proof.
Sluis is the gateway in between: one API for every AI model that strips personal data from each prompt before it leaves, puts it back in the answer, and seals every passage in an audit ledger.
A lock does what no dam can: it holds back the sea and lets the ship through. It never opens both gates at once, and every passage goes in the keeper's ledger. Sluis does the same for AI traffic: your data sails through, what must stay inside stays inside, and every passage is provable.
Sluis is Dutch for canal lock.
One prompt, three views.
The same request: as your user types it, as the model receives it, and as your app gets it back.
What your user types
“Draft a payment plan for Anna de Vries, anna.devries@mail.nl, citizen ID 123456782.”
What the model sees
“Draft a payment plan for «PERSON_1», «EMAIL_1», «ID_1».”
What your app gets back
The full answer, with Anna back in place, restored mid-stream, no visible delay.
Every request passes three gates.
No request skips a gate. None leaves without a record.
Inspect
The gate closes behind you.
60+ detectors scan every prompt before it leaves; what they find is reversibly pseudonymized.
Route
The water level equalizes.
You decide per key: which models, which region, whose ownership; a failed provider fails over automatically.
Seal
The passage goes in the ledger.
Every request gets a hash-chained entry: verifiable offline, exportable, erasable per person (GDPR Art. 17, or any right-to-delete duty).
A data center address is only half the answer.
An address says where a server stands, not who owns it. Legal reach follows ownership: a provider's parent company can be compelled under laws like the CLOUD Act.
Region and owner
Where a model runs and who owns it are two different risks; Sluis labels both axes on every model in the catalog.
EU by default
The default is the strictest setting: EU-owned providers on EU-region clouds only, until you deliberately allow more.
Per workload
One key allows a frontier model for general drafting; another stays locked to the strictest route for anything personal.
residency.policy · class: PHIenforced
EU · France
mistral/mistral-large-latest
primary
EU · France
scaleway/llama-3.3-70b
fallback
EU · region
vertex/gemini-3.5-pro
allowed
United States
xai/grok-4.3
blocked · policy
Selling AI into Europe?
If your models or agents serve EU customers, Sluis is your compliance bridge: put the lock in front of your product and every call gains enforced EU residency, reversible pseudonymization, and a verifiable audit trail. No rebuild, one base_url.
EU residency, enforced on every request
Personal data pseudonymized before it reaches a model
An audit ledger your customers' auditors can verify themselves
Two readers. One gateway.
Whether you ship the code or sign off the risk, Sluis is built for you.
SHIPSIGN
01
For engineering
Swap one base_url and you are behind the lock: OpenAI-compatible, streaming stays streaming, +1 ms measured.
Switch from Chat to Passage. Sluis turns the goal into a Passage Contract, routes it to an owner-activated Station, keeps work inside a Chamber, pauses sensitive actions at a Gate, and gives every successful verified outcome a Seal.
PASSAGE / 0241passage-contract.v3
CONTROLLED
01
Passage Contract
Agree the goal, limits, acceptance checks and budget before work starts.
02
Station
An owner explicitly activates a macOS, Windows or Linux computer for execution.
03
Chamber
Folders, applications, tools and collaborators stay inside one bounded workspace.
04
Gate
Shell, browser, computer and other high-impact actions pause for policy or human review.
REVIEW
05
Seal
Every outcome carries the exact contract, actions, approvals, changes and checks.
VERIFIED
SIMPLE TARIFF
The fee is for the lock, not the tokens.
Your provider's list price, plus a flat 10%. Your first 50,000 tokens are free.
Compliance shouldn't mean giving up the best models. That's a false dilemma. You're just missing a lock.
Bas Alderding, founder
Chat · Passages · Stations
From a question to a verified outcome.
Use Chat for an answer or Passage for durable work. A Station executes inside a Chamber, risky actions stop at Gates, reusable Skills standardise the workflow, and every successful verified Passage ends with a Seal.