LatentGateway
The right model access. For every team.
Configure supported endpoints, model tiers and team permissions. Keep restricted work on private models and allow approved third-party models for other workloads.
LatentStack is a modular AI software stack. This component is available on its own.
How it works
01
Private and approved external models
02
Team access and model tiers
03
Permissions distinct from task routing
Illustrative model-access configuration
Works with
Models
Private self-hosted endpoints and approved third-party endpoints exposed over OpenAI-compatible APIs.
Agents
LatentCode, and supported MCP-compatible third-party coding agents configured to route through the gateway.
Identity
Team and role mapping from your existing directory, for access and model tiers.
Supported-capability list v0.1 · owned by engineering · requires engineering sign-off before publication.
What it does not do
−It does not host or serve models. It governs access to the endpoints you provide or permit.
−It does not remove the terms of an external provider. Permitted inputs sent to that provider are handled under that provider’s terms.
−It does not route work by permission alone. Team permissions are distinct from task routing.
Deployment note
Available in all three deployment modes. In an air-gapped configuration there are no external model calls, so the gateway governs only locally available models.
Works alone. Better with
Questions
Can we use both private and third-party models?
Yes, where your environment and policies permit. Configure supported private models for restricted work and approved third-party models for other workloads. Air-gapped deployments use models available inside the isolated environment.
Does our code leave our network?
It depends on the configuration you choose. Work restricted to private models has no external fallback. Work you permit to use approved third-party models sends the permitted inputs to that provider under that provider’s terms.