How the layer works together.
Every NexusLayer service follows the same four rules: one identity, one model gateway, credentials on request and complete observability. The result is a platform in which any combination of services can be composed into a workflow, and every step of that workflow can be explained afterwards.
Four foundations.
Services never hold provider keys, never store user passwords and never keep credentials in configuration. They rely on four shared services instead.
Every request carries a NexusLayer identity
Identity issues a signed session token for people and a scoped, short-lived token for agents. Every service validates the same token, so access is granted and revoked in one place.
SwitchBoardEvery model call goes through the gateway
Services and products never hold provider keys. They call SwitchBoard (or ModelRouter for Anthropic-native tooling), which applies routing policy, fails over between providers and attributes cost.
AgentVaultEvery credential is fetched, never stored
When a workflow needs to reach an external system, it requests that specific secret from AgentVault for a limited time. Nothing sensitive lives in prompts, code or configuration.
WatchGridEvery action is observable
Model calls, tool invocations, memory access, secret requests and sign-ins are reported to WatchGrid, giving a single timeline of what happened, what it cost and who was responsible.
Follow a request through the platform.
Choose a scenario to see which services take part and in what order. Select a step, or a service on the map, to follow it. Choose All connections to see every dependency, then select a service to isolate its own.
From a queued task to a reviewed pull request, with memory, credentials and a full trace.
Standard interfaces throughout.
Services communicate over open, well-understood protocols, so the layer integrates with the tools and agents you already use.
REST over HTTPS
Each service exposes a documented REST API behind TLS, authenticated with NexusLayer tokens.
MCP for agents
Memory, knowledge and secrets are available to agents as Model Context Protocol tools.
Live streams
Dashboards receive run updates over WebSockets as they happen.
Webhooks and schedules
Workflows start from CI/CD events, external webhooks or a schedule.
Composable
Adopt one service today and add others later. Each integrates through the same identity and gateway.
Accountable
Every action is attributable to a person or an agent identity, with its cost and outcome recorded.
Sovereign
Operated on our own infrastructure in Germany, with the option of local models for sensitive work.
Let's build it together.
Whether you want to run your own agents on the layer, discuss one of our products, or need a partner for an AI, Java or enterprise project, we respond within one working day.