Business Model
Revenue Streams
Three layers, each targeting a different buyer.
PaaS — Managed Deployments (Usage-Based)
| Tier | Price | Target | What They Get |
|---|---|---|---|
| Free | $0/mo | Developers, hobbyists | Limited agents, capped LLM usage, default skills only |
| Pro | $9.99/mo | Power users | More agents, stronger models, expanded integrations |
| Business | $29.99/mo | Teams | Larger swarms, advanced integrations, team coordination, priority support |
IaaS — Enterprise Infrastructure (Contract-Based)
| Revenue Type | Description |
|---|---|
| Enterprise licenses | Annual contracts, priced per-cluster or per-seat |
| Deployment fees | Integration, customization, and migration services |
| Support contracts | SLA-backed tiers with defined response times and escalation |
| Custom runtime integration | Professional services for proprietary runtimes |
Solves three enterprise objections: data residency (runs in their infrastructure), vendor lock-in (cloud-agnostic), and compliance (isolation, RBAC, audit, BYOK).
SaaS — Marketplace (Phase 3+)
| Revenue Type | Description |
|---|---|
| Agent marketplace | Revenue share on third-party agent and skill sales |
| Paid skill packages | Premium first-party integrations (SAP, Salesforce, ServiceNow) |
| Platform commission | Percentage on all marketplace transactions |
Unit Economics
| Metric | Value |
|---|---|
| Agent footprint | Orders of magnitude lighter than Python/Node runtimes |
| Scale-to-zero | Near-instant cold start; idle agents cost nothing |
| LLM costs | Platform-managed; no GPU infrastructure |
| Enterprise revenue | Annual contracts with high retention |
A node that hosts 10-20 Python-based agents can host hundreds of Agent Runtime agents. Lower costs enable a generous free tier, which drives adoption, which justifies higher enterprise contracts.
Growth Strategy
1
Step 1
Consumer app validates the platform
Real traffic proves the orchestrator, runtime, integrations, and cost controls work in production.
2
Step 2
Developer PaaS attracts volume
Public API and lower hosting costs become the wedge for developer adoption.
3
Step 3
Enterprise IaaS captures contracts
Same stack developers use, deployed in customer infrastructure with an SLA.
4
Step 4
Marketplace creates network effects
Skills, agents, and federation make the network more valuable over time.