Platform

Swirls is both a language and a platform. Your .swirls files define what your workflows do. The platform handles how they run.

Ways to run workflows

• Local development — Use the Swirls CLI to sync .swirls files to a project, run graphs, and iterate. See Local Development.
• Swirls Cloud — Managed infrastructure that runs your workflows at scale. See Swirls Cloud.
• Self-hosting — Run the platform yourself when your requirements demand it. See Self-hosting.

Execution pipeline

When a trigger fires, the platform executes the attached graph. Nodes run in topological order, and outputs are stored after each node completes. The full run record is available immediately in the Portal and through the API.

Trigger fires → Graph executes → Nodes run in topological order → Outputs stored

What the platform handles

• Execution orchestration — Scheduling, retries, and error handling across graph runs.
• Stream persistence — Durable, queryable storage for graph outputs.
• Secret management — Encrypted storage for API keys and credentials.
• Form hosting — Hosted form endpoints with schema validation.
• Webhook endpoints — Managed HTTP endpoints for inbound webhooks.
• Cron scheduling — Reliable cron execution with timezone support.
• Portal UI — Web interface for managing projects, viewing executions, and debugging runs.