01
Identity & access
Identify users and services. Grant access to approved models and MCP tools.
KeycloakAPI-key bridge
Put limits on your AI. Not on your choices.
The AI operating system
you control.
Open source. Self-hosted. Independent by design.
Set who can access approved models and MCP tools, and apply configured PII policies to supported gateway traffic. See usage and measured costs in Studio while choosing your clients, model providers, and infrastructure. Cost visibility is not a hard spending limit.
✦ Self-hosted
✦ Open-source (MIT)
✦ Provider-independent
✦ Frontend-independent
Continuous GitOps delivery
Declared in Git. Reconciled by Flux.
flux — neurwerk.base
01 / Choose your interfaces
Works with…
Use the integrated apps or bring compatible clients with a configurable LLM endpoint.
Any frontend or app with a configurable LLM endpointConnect through a custom, OpenAI-compatible API URL.02 / The neurwerk.base stack
Open-source packages. One Base.
Route supported LLM and MCP traffic through your self-hosted gateway. Configure access and PII policies, then monitor usage and measured costs without tying your infrastructure to one client or provider.
neurwerk.base
02
LLM & MCP routing
A shared AI endpoint, independent of your choice of client or provider.
AgentGatewayAgentGateway extProc
03
PII policies
Sensitive-data detection, policy handling, and attachment inspection.
PII EnginePresidioDocling
04
Administration & usage
Base controls, policy tools, request usage, and measured cost with configured pricing.
StudioAgentGateway
05
Metrics & alerts
Latency, reliability, errors, and platform health.
PrometheusGrafanaAlertmanager
06
Logs & traces
Collect logs and investigate supported LLM/MCP requests.
Fluent BitOpenSearchOpenSearch DashboardsLangfuseOpenTelemetry Collector
07
Secrets & trust
Secret delivery, certificates, and private access.
OpenBaoExternal Secretscert-managertrust-managerWireGuard
08
State & storage
Persistent state, caching, and storage for Base services.
PostgreSQLValkeyRook/CephClickHouse
09
Delivery & operations
GitOps reconciliation, ingress, and configuration reloads.
Flux CDTraefikReloader
Neurwerk componentUpstream component
03 / Pick your LLM models
Your models. Your choice.
Connect approved models from external providers or your own private endpoints. You choose the destinations; Base applies configured policies to supported traffic routed through its gateway.
External providers
Connect MCP tools
MCP servers are separate tool destinations, not LLM models.
MCP servers
External providers may receive data outside your infrastructure. Choose destinations and policies to suit your deployment.
Start with the source.
Read the release, inspect the packages, connect a client.
Base repository: MIT. Third-party components retain their own licenses.