Skip to content

Your infrastructure.
The same control.

Run Sluis Gateway on infrastructure you control. Keep provider keys, retained content and the audit ledger with you, while managing policy from one console.

A clear boundary
between control and data.

The console manages the policy. Edge handles the requests. Choose connected management or serve from local configuration.

Sluis console

Policy, credentials and budgets.

Outbound-only TLS

Sluis Edge

Inside your infrastructure

Serving
Provider keysAudit chainUsage ledger
Model trafficApproved provider
or local model

Model traffic goes directly from Edge to your approved provider. It does not pass through the Sluis cloud control plane.

Your gateway.
Layer by layer.

The data plane runs in your environment. Scroll through what stays with you, what can leave and what keeps working.

Your infrastructureSluis Edge
InspectData protection
RouteModel & tool policy
RecordAudit & usage
Provider keys · token mappings · local state

The same controls, running on your infrastructure.

Inspect locally.

Run the gateway’s data protection in your own deployment. Your provider credentials and token mappings stay on your side.

Optional hosted inspection can send remaining eligible text to its configured provider.

Review detection controls

Route directly.

Permitted model requests travel from Edge straight to your approved provider. They do not pass through the Sluis cloud control plane.

Choose local models when model traffic must remain inside your network.

Explore the data flow

Keep the record.

Your deployment holds the audit chain, usage ledger and retained content. Budgets are enforced against the local ledger.

A single binary and local SQLite state, with no cluster required.

Explore the audit evidence

Keep serving.

If the management tunnel drops, Edge continues from local configuration. The data plane can keep working independently of the console.

Verify binary checksums during installation and manage fleet updates from the console.

Plan your deployment

AI for teams with real responsibilities.

Talk about your team
Ministerie van Justitie
Omgevingsdienst de Vallei
DCMR Milieudienst Rijnmond
Omgevingsdienst Groene Metropool
Omgevingsdienst Regio Utrecht (ODRU)
Omgevingsdienst Midden-West-Brabant
COA
RDW
Adjust
Universiteit van Amsterdam
NHA
Moco Museum
Chemgas
InShared
Het Oranje Kruis
Storteboom
Hyva
Arbeid.ai
Kleentec
Rho Adviseurs
Bezwaarschriftenadviescommissie (BAC)
SoundAware
DLV Advies
Star-shl
Stratego
Contakt
NeKo Ship Supply
Hulshoff
Logisnext / Mitsubishi Forklift Trucks
Bloem Infra
Loendersloot Group
Procap
Condor
Hoogheemraadschap van Rijnland
Aegir Marine
VO-raad & PO-raad
Weekamp Deuren
DBF
STL
Voetbal International
Sena
Move Beyond
Farmplus
Woonbedrijf
Boekenbalie
Medicinfo
Kwast Wijnkopers
Royal ZON
Verhoeven
ABN AMRO
BASF
Bayer
Eurocross
Gilead Sciences
Edelman
PXR
Avanti
Wim Hof Method
Nictiz
Nétive VMS

Cloud or Edge?
Start with the requirement.

Both use the same controls. Your operating model and infrastructure requirements decide where the data plane belongs.

Managed cloud

Sluis Edge

Data plane

Managed EU infrastructure

Your infrastructure

Operations

Managed by Sluis

Your deployment

Model traffic

Through the Sluis gateway

Direct from your Edge gateway

Audit & retained content

Managed storage

Local to your deployment

Pricing

Usage-based

Annual licence per gateway

A few useful answers.

Does Edge keep all model traffic inside our network?

Only if you use models inside your network. With an external model provider, Edge sends permitted requests directly to that provider, without passing through Sluis cloud.

Do we need to open an inbound port for management?

No. Connected management uses an outbound-only TLS tunnel from Edge to the control plane.

Can we run without the cloud console?

Yes. Edge can serve from local configuration with the tunnel unset. For an air-gapped environment, the models and other required services must also be reachable inside your environment.

How is Edge licensed?

A flat annual licence per gateway. Contact the team to scope your deployment and pricing.

Make the deployment fit your policy.

Bring your infrastructure requirements. We’ll map the data flow with you.

Talk about Edge