NautsAI software & research
Back to NautGate

NautGate / Guide 2 of 3 / 2 min read

How NautGate makes the path visible

NautGate receives a connected request, applies an approved route, and records the response information needed for review.

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.

48Nauts / Product guides

1. Put one workflow through the gate

Your application sends a model request through NautGate. Route selection applies the configured privacy, capability and availability requirements. An automatically routed request can use a decision model to help select among approved models.

A confidential route needs explicit behaviour when its local model is unavailable. The configured confidential route blocks rather than silently sending that request to a cloud fallback.

  1. 01Application request
  2. 02Route checks
  3. 03Approved model

2. Keep the evidence proportionate

The gateway receives the response and records available model, latency, usage and cost information. The served-model identity in this record is provider-reported; it is not an inspection of the provider’s model weights.

Prompt and response capture follow the recording policy. Metadata can explain much of a request without retaining every original value. Where personal data does not need to leave the application, use a local reduction step such as Bowden-PII before the request continues.

3. Review and act

Use the request history to investigate spend, changes in model behaviour and route decisions. Alert rules and integrations determine which events result in notification or follow-up work.

Agree the handoff to the orchestrator when an event should affect the running agent. Test the coverage, alerts and handoff with a representative workflow before relying on them. Optional HSM signing can make captured checkpoints independently verifiable; it does not turn uncaptured activity into evidence.