Kubernetes namespaces, without the Kubernetes.
Every team gets its own isolated namespaces with quotas, network policies and access control already in place. Developers deploy. Platform teams keep the guardrails.
ProductsNamespace Manager
acmefrontendNamespaces
NameEnvironmentClusterStatus
shop-apiprodfsn1-prodReconciled
shop-apistagingfsn1-stageReconciled
searchprodpar-prodUpdating
searchdevfsn1-stageCreating
checkoutprodpar-prodReconciled
docsprodfsn1-prodReconciled
How it works
acme / frontend
shop-api · prod
shop-api · staging
checkout · dev
Resource limits
Network isolation
Team access
Clusters
fsn1-prod · in sync
fsn1-stage · in sync
Organize
Group namespaces by team and by environment: dev, staging, prod.
Set up
Namespace Manager adds the guardrails each namespace needs: limits, network isolation and access.
Sync
A small agent in each cluster fetches its setup and applies it.
What teams get
Guardrails from the first minute
Every namespace starts with resource quotas, limit ranges, default-deny network policies and Pod Security labels. Cilium or standard Kubernetes network policies.
Access from your identity provider
Bind a group from Entra ID or any OIDC provider to a workspace or a namespace. Roles are admin, editor and viewer.
kubectl when you need it
Generated kubeconfigs sign in through your identity provider and only list the namespaces you hold a grant on.
Many clusters, any cloud
Spread environments across clusters and regions on Hetzner, Scaleway, AWS, Azure or your own hardware. Nothing assumes a specific managed Kubernetes.
Routing built in
Each namespace gets its own host, routed through the Kubernetes Gateway API.
One source of truth
State lives in Postgres behind a REST API and a web UI. No custom resources to install, no hand-applied YAML to drift.
Deploy from anywhere you already work.
One CLI for laptops and pipelines. Describe the app in a short file, deploy, check status and roll back to any of the last ten revisions. Works from GitHub Actions or any CI that can run a command.
$ nmctl deploy --tag v1.8.2 --wait
→ shop-api: revision 7 rolling out
✓ shop-api is live
$ nmctl status
shop-api revision 7 ready
$ nmctl rollback
✓ shop-api rolled back to revision 6
Coming soon
Let your AI agents run it too.
An MCP server for Namespace Manager, so AI assistants and agents that support MCP can work with your namespaces directly.
Three ways to run it
ViaKube hosting
On our clusters
Namespace Manager drives our hosting platform. We run the clusters; your team gets namespaces and deploys. No cluster to build or maintain.
Your team signs in through Control Center, our web console, and manages its namespaces from there.
In your own clusters
Self-hosted with Helm against the clusters you already run, on any cloud, signing in through your own identity provider. Air-gapped installs are supported.
Self-hosted with Control Center
Run it alongside your own Control Center to share sign-in, roles and the audit log with other ViaKube products.