01
Follow the cost
Inspect recorded spend, requests and providers for the applications connected through your gateway.
← All products
Audit / NautGateAvailable
NautGate
Your AI is already acting. Are you still in control?
Would you notice an agent burning through your API budget, taking an unexpected route or changing its behaviour? NautGate makes connected AI activity visible: inspect spend, control model routes and keep verifiable evidence.
The reason
I wanted to know what my LLM was actually doing.
The same model could feel different from one week to the next. I wanted a record I could inspect instead of guessing what had changed.
NautGate grew from that monitoring tool into a gateway for connected applications and agents. It records their usage, controls model routes and can produce signed evidence for later inspection.
Inside NautGate
What you can do.
Select an image to take a closer look.
02
Investigate changes
Compare recorded usage and behaviour. Use the detail behind a request to investigate an unexpected result.
03
Monitor model health
Compare trust scores and behaviour charts across models. Investigate flagged shifts and open drift alerts.
04
Inspect the evidence
Review receipts and checkpoints. Optional Securosys HSM signing makes recorded evidence independently verifiable with a trusted key.
Follow the NautGate workflow
NAUTGATE / FROM REQUEST TO EVIDENCE
01
Request
Your application sends a request to NautGate.
How the signature works
NautGate passes the checkpoint to its signing service, which calls Securosys TSB:
POST /v1/synchronousSign · SHA256_WITH_RSAThe returned signature is checked before the evidence is marked verified. This illustration makes no HSM requests.
Watch the NautGate demos
NAUTGATE / PRODUCT DEMOS
See NautGate at work.
Start with the overview. Take a deeper look when you want to know more.
Choose your demo
Both videos are narrated in English.
Availability, scope and technical resources
NautGate connects applications and agents to approved model routes and records the activity behind each request. Explore the interfaces, routing controls and optional signing integration. The single-user open-source and Enterprise editions have different scopes; team requirements and licence terms are discussed separately.
A separate single-user open-source edition is available. It is not the Enterprise or SME offer. Its licence and documentation apply to that edition; enterprise scope and terms are agreed separately.
Visibility covers the AI activity connected through your gateway. Logging, routing, retention and event responses depend on your configuration. HSM signing is optional; it verifies recorded evidence, not the truth of a model’s answer.
Technical questions
Is there also an open-source version?
Yes. The open-source edition is for single-user use. It is separate from the Enterprise edition for organisations; licence terms and feature scope differ.
Does NautGate switch agents or models?
NautGate controls model routes for connected agent requests. Replacing the executing agent belongs to the connected orchestrator. The orchestrator integration needs to be configured and tested.
How does routing with decision models work?
For eligible automatically routed requests, a decision model such as Jev assesses the task. NautGate maps that assessment to approved models while applying privacy, capability and health rules. Explicit choices and policy controls retain precedence.
Does NautGate store full prompts and responses?
Capture follows your configured policy. Metadata and routing decisions provide traceability; sensitivity checks and redaction govern captured content. Configure recording scope for your workflow.
Does NautGate capture every use of AI?
It captures requests routed through the gateway. Applications must be explicitly connected. Activity outside that connection is not automatically visible.
Can we run it locally?
Yes. NautGate can run on your infrastructure. Local models and offline mode allow outbound provider connections to be disabled. Review the configuration for your environment.
What does a signed receipt prove?
Receipt integrity and inclusion in a signed checkpoint. It does not prove input truth or which model weights a provider actually executed. Model identity is taken from the provider response.
Do we need an HSM?
No. Routing, logging and the dashboard work without an HSM. The signing extension connects checkpoints to a Securosys HSM.
Does it make us compliant automatically?
NautGate supports compliance work with technical controls and evidence. Organisational and legal requirements still need to be assessed and implemented.
NautGate guides