Skip to main content
For an enterprise that wants isolation but not a whole dedicated cluster, the dedicated-namespace tier gives you your own isolated instance on a shared, fully-managed Kubernetes pool. You share the expensive, undifferentiated plumbing (the cluster control plane, the network, the load balancer) — which is where the saving comes from — while everything that holds your data and runs your app is yours alone. We operate, patch, upgrade, and monitor all of it. You just use the app.

​
What you get

The namespace is dedicated — it is yours. What’s shared is the cluster, so a small team isn’t paying for a whole control plane.
So no two customers share a namespace, nodes, or a database. Another customer’s workload cannot reach yours (network policy), cannot land on your nodes (node taints), and has a separate database. The only things in common are the cluster’s control plane and network — the parts that carry no customer data.
Need nothing shared at all — for a stricter regulatory posture? The dedicated-cluster tier gives you an entirely separate cluster, VPC, and data tier. Same app, higher floor.

​
Logging in

Your instance lives at your own subdomain, e.g. your-company.aws.agentbees.ai.
  • Sign in with your own identity provider (SSO) — Google, Microsoft, Okta, or any OIDC IdP. We map your IdP groups to roles (admin / developer / viewer), so access is governed by your directory.
  • No separate passwords to manage; offboarding a user in your IdP removes their access here too.

​
Monitoring your usage & cost

Every instance has a Billing & usage page (under Admin). It shows only your own cloud cost — the exact pass-through figure your invoice is built from:
  • Monthly cost broken down by compute, storage, database, and network.
  • A running total per period.
  • The numbers come straight from the cloud provider’s Cost & Usage Report, so they reconcile to the bill — no estimates or markups on the pass-through line.
You see only your tenant’s numbers. The page is scoped to your instance and enforced on the server — you can never see another customer’s cost, and they can never see yours.

​
How the number reaches you

  1. We attribute cloud cost per customer from the provider’s billing export (your dedicated database/cache/storage are tagged to you; your namespace’s share of the pool compute is split to you).
  2. Our billing pipeline pushes your slice into your instance.
  3. Your Billing & usage page reads it — your data never leaves your instance to show you your own bill.

​
Your invoice

The platform fee (a per-seat annual subscription) covers us running, patching, upgrading, and monitoring everything above. The pass-through line is exactly what you see on the Billing & usage page.
Two views of the same data. Your team sees a single-tenant “Billing & usage” view (only you). Our platform operations team sees a cross-tenant aggregate to produce invoices and watch fleet health — never mixed, never visible to you.