Choose SaaS or Private Kubernetes
agent.ceo supports two starting paths: hosted SaaS and private Kubernetes. The product model is the same in both paths: create an organization, model it in agent.ceo/map, invite users, connect tools, deploy agents, and assign work.
The difference is who operates the infrastructure.
Quick Decision
| Choose | When |
|---|---|
| SaaS | You want to evaluate quickly, connect common tools, and avoid infrastructure work |
| Private Kubernetes | Agents must run inside your cloud, VPC, region, or regulated environment |
Most teams should start with SaaS unless a security, compliance, or network requirement makes private deployment necessary on day one.
Decision Matrix
| Requirement | SaaS | Private Kubernetes |
|---|---|---|
| First agent in minutes | Yes | No |
| No Kubernetes operations | Yes | No |
| GenBrain AI manages upgrades | Yes | No |
| Customer-controlled cluster | No | Yes |
| Private network access | Limited | Yes |
| Air-gapped operation | No | Yes |
| Customer-managed secrets backend | Limited | Yes |
| Custom ingress and egress policy | Limited | Yes |
| Best for evaluation | Yes | Sometimes |
| Best for regulated internal workloads | Sometimes | Yes |
Start with the Operating Model
Do not treat deployment as the first design decision. The first design decision is the operating model:
Rendering diagram…
If the first agent can safely work through hosted integrations, SaaS is the faster path. If the first agent needs private-only systems, private Kubernetes is the correct starting point.
SaaS Starting Path
Use SaaS when your first agent can work through connected tools such as GitHub, Slack, Gmail, Google Calendar, or a public API.
- Create the organization.
- Open agent.ceo/map.
- Add users and teams.
- Connect the first tool.
- Deploy one agent.
- Assign a constrained task.
Continue with SaaS Quick Start.
Private Kubernetes Starting Path
Use private Kubernetes when your first agent must operate near private repositories, internal APIs, cloud accounts, or regulated data.
- Confirm cluster prerequisites.
- Prepare namespaces, ingress, storage, secrets, and network policy.
- Install the platform services.
- Create the first organization namespace.
- Open the organization map and add users, agents, systems, and approval rules.
- Deploy the first agent.
Continue with Install on Your Own Kubernetes.
Migration Later
Starting with SaaS does not prevent private deployment later. Keep the organization map clean, use named agent templates, and avoid granting broad tool access to experimental agents. That makes it easier to migrate workflows into a private installation when compliance or network constraints become real.