Free
$0
Best for
Learning the language
Author a .swirls project, deploy it to Swirls Cloud, and inspect the compiled system before paying for a production plan.
Includes
- 1 project
- Full Portal and graph view
Author the system. Pay for the runtime.
Start free with the language and compiler. Choose a paid plan when you run systems for your company or across client workspaces.
Builder
$49/mo
Best for
One company
Run custom business systems for one organization. The base price includes every builder on the team.
Includes
- 25,000 credits a month
- 5 projects
- Unlimited builders
- 7-day free trial
Overage rates
- Credits above 25,000
- $1 per 1,000
MSP Partner
$250/mo
Best for
A client portfolio
Deliver client-specific systems through one provider organization, with a separate workspace for each client.
Includes
- 2 active client workspaces included
- 50,000 pooled credits a month
- Unlimited projects and builders
- White-label available
Overage rates
- Pooled credits above 50,000
- $1 per 1,000
- Active workspaces after 2
- $15 each / mo
Enterprise
Custom
Best for
Custom infrastructure terms
Volume rates, BYO-KMS, on-prem or your VPC, and a custom SLA.
Includes
- Credits from $0.80 per 1,000
- Unlimited audit retention
- Named 24/7 support
How billing works
Base plan, active clients, runtime use.
The base plan sets how you deliver. MSPs add active client workspaces. Builder and MSP runtime use above the included credit balance is billed at the published overage rate.
1 · Base plan
Choose the delivery context
Use Builder for one company or MSP Partner for a portfolio of client workspaces. Paid plans do not charge per builder.
2 · Clients
Add active client workspaces
MSP Partner includes two active client workspaces. Additional workspaces are billed only in months when they run something.
3 · Execution
Meter completed runtime work
Builder includes 25,000 credits and MSP Partner includes 50,000 pooled credits. Usage above either balance is billed at $1 per 1,000 credits.
Product fit, billing, and ownership.
What can I build with Swirls?
Swirls is for custom business systems built from supported Apps, workflows, data, connections, access rules, human reviews, and agents. Those parts live in one .swirls project and run on the same managed runtime. Swirls is designed for operational software, not arbitrary consumer interfaces or unrestricted framework code.
Do I need to build it myself?
You need to understand the process, make system-design decisions, and guide a coding agent. You own the intended behavior and decide what counts as correct. If you want someone else to lead implementation, Swirls Studio can define, build, integrate, launch, and support the system with you.
Which plan is right for me?
Free is for learning the language and inspecting one compiled project. Builder runs systems for one company.MSP Partner runs separate client workspaces through one provider organization. Enterprise covers custom infrastructure, security, support, or SLA terms. Paid plans do not charge per builder.
Can Swirls work with the software we already use?
A .swirls project can call supported actions in the tools already used by the process. You can add the missing App or workflow around those systems while leaving the existing systems of record in place. Check the Integration Catalog for current actions.
What do I own, and what does Swirls operate?
You own the source, system design, business logic, acceptance criteria, and every change to intended behavior. Swirls operates the supported App, workflow, agent, identity, data, credential, and observability services. Source validation and deployment history keep changes traceable.
How does pricing scale?
Start with a base plan, then pay for completed runtime work. Every paid plan includes monthly execution credits and unlimited builders. MSP Partner also includes two active client workspaces; founding partners pay $15 for each additional workspace only in months when it runs. The Builder and MSP plans bill usage above the included credit balance at $0.001 per credit, or $1 per 1,000 credits. The first 15 accepted MSP partners lock in the complete founding rate of $250 per month plus those active workspaces for life. After the founding cohort, new partners pay $500 per month plus $50 per client project. You bring your own provider keys and pay those providers directly.
What is a credit, and how are credits consumed?
An execution credit is Swirls' unit for completed work. A workflow uses the total credits for the nodes that finish successfully, whether the run starts manually, on a schedule, or from a trigger.
- 1 credit: code, HTTP, database, Postgres, integration, and workflow-call nodes
- 5–15 credits: stream and email nodes
- 25 credits: AI, agent, scrape, search, parallel, and disk nodes, plus each completed direct agent turn
- 0 credits: control flow such as map, fanout, while, switch, and wait
For example, a run with code, AI, and email nodes consumes 41 credits when all three complete. Failed nodes and agent turns that do not complete are not charged.
Can I deliver and brand Swirls-built software for clients?
MSP Partner gives each client a separate workspace with its own connections, policies, data, and operational history. You own the client relationship and set your service price. White-label options are available, but custom customer domains are not currently supported. Clients use the Apps and channels you deliver without builder seats.
What security and deployment options are available?
Hosted Swirls separates projects, credentials, data, and runtime state. The runtime applies declared access, stores encrypted secrets, pauses workflows for authorized review, and records runs and traces. Enterprise can add customer-VPC or on-prem deployment, BYO-KMS, and custom support or SLA terms. See the security overview and Data Processing Addendum for the current posture and terms.
Need a precise answer for your system?