Startup
A two-person team standing up its first Pod. A grounded product agent with one knowledge base, live on a custom domain in an afternoon — humans on the gates, the agents doing the legwork.
- Builder UI
- RAG
- 1–2 connectors
- Free plan
a moment…
Customer support, sales ops, research, coding, physical-world automation — the same agents fit surprisingly different roles. Pick a starting point.
The same Pod runtime — Planning, Builder, QA and Knowledge agents under human-signed gates — scales from a single Slack assistant to a fleet of MCP-driven agents on the line.
A two-person team standing up its first Pod. A grounded product agent with one knowledge base, live on a custom domain in an afternoon — humans on the gates, the agents doing the legwork.
A SaaS embedding a Pod inside its own product. A Pod per customer account on the multi-tenant API, metered through Stripe usage billing, with each run streamed back into the product UI over SSE.
A compliance-bound team retiring point solutions. Internal Pods behind SSO and RBAC, every decision written to an immutable audit ledger, on-prem MCP servers and a private connector catalog inside your perimeter.
An ops team with hardware in the loop. Long-running Pods that act on MCP-exposed PLCs, ROS nodes and field equipment — the Pod Connector bridging cloud agents to the floor, supervised and signed off from Builder and the iOS app.