Swirls Cloud

Swirls Cloud is the managed runtime for your .swirls agents. You author .swirls files locally, deploy them to Cloud, and inspect the compiled project in the Portal. Auto-scaling workers and a verifiable audit chain are bundled in for hosted execution. Deploy with git push or swirls deploy. No CI/CD to maintain.

What's included

Every Cloud deployment ships with the full platform. No add-ons, no plugins.

• Durable execution: Steps are checkpointed automatically. Failovers resume without duplicate work.
• Auto-scaling workers: Workers scale with your queue depth. You pay for work that ran, not machines reserved.
• The Portal: Inspect every execution as a trace, drill into spans step by step, and approve human-in-the-loop reviews.
• Verifiable audit chain: Append-only, hash-chained audit log. Customer-verifiable.
• Per-node secrets: Secrets are delivered at run time. A node sees only what the .swirls file declared it needs.
• Versioned deploys: Every deploy is a snapshot. Roll back to any previous version from the Portal.
• Team collaboration: Invite teammates, manage roles, and share the audit trail.
• Identity-scoped access: Declare role and policy blocks and each principal reaches only the agents and workflows their role grants.

Three pillars

Runtime managed

• Durable execution with automatic step recovery
• Auto-scaling workers based on queue depth
• The Portal hosted: trace, inspect, approve
• Sleep, signal, and child-workflow yields

Governance enforced

• Cryptographically scoped delegation tokens, attenuated per call
• Per-node secrets, never ambient
• Tamper-evident audit chain, customer-verifiable
• Permissions bound to the workflow hash

Regulated production

• 99.9% uptime SLA on every Cloud account
• Row-level tenant isolation, per-tenant keys
• SOC 2 Type II targeting 2027

Good to know: The .swirls file is the security policy. Every permission, key, and token derives from what you wrote. Modify a file and old tokens stop working. See the security model for the full chain of trust.

Getting started

curl -fsSL https://swirls.ai/install | bash
swirls auth login

swirls configure

swirls deploy

git push

Deploy methods

Swirls Cloud supports two deploy paths:

Both paths compile your .swirls files and lock the resulting definition to every execution token. You can use both on the same project.

Plans

On Developer and Team plans, you supply your own vendor API keys (OpenAI, Anthropic, Resend, and others). Enterprise unlocks platform-managed keys. See swirls.ai/pricing for the full comparison.

One-time credit top-ups are available on any plan: Pile of Credits (3,000 for $4.99) and Bag of Credits (18,000 for $19.99). Top-up credits land on your balance right away and never expire.

Credits

Credits are spent two ways. Each successful node execution in a workflow run spends credits from your plan's monthly allowance, and each turn in an agent chat spends 25 credits. Failed nodes and turns that do not complete are not billed.

Per-node cost

Control-flow nodes (map, while, switch, wait) are free. The work they orchestrate is what gets billed.

AI tier breakdown

ai and agent nodes are priced per model class. Every tier is currently 25 credits regardless of whether you use a platform-managed key or BYOK.

The tier system is in place so per-class pricing can land without a schema change. Track the current numbers on swirls.ai/pricing; the docs and the marketing page both read from the same source.

Agent chat

Talking to an agent directly bills 25 credits per turn, where a turn is one message you send. This matches the cost of an agent node in a workflow. Turns that do not complete are not billed. When your balance runs out, the agent stops accepting new turns until you upgrade your plan or buy a credit top-up.

Next steps

• Local Development: Author, validate, and deploy .swirls files from your machine.
• Agent Onboarding: Let AI agents register for Swirls on behalf of users.