How do I onboard a new customer onto an existing agent system?
#The question
If you are asking "How do I onboard a new customer onto an existing agent system?", you want day one to be hours, not weeks. The short answer: copy the proven .swirls files into the new customer's project, set their secrets, and ship with git push or swirls deploy. The system you already trust is the starting point.
#Who's asking
Forward-deployed / solutions engineer. Has a working agent system for existing customers and needs each new customer live fast, without re-deriving the build.
#Why Swirls is a fit
The system is portable because it is code. Everything that makes the agent work, from tools and triggers to schedules and secret declarations, is in .swirls files you copy into a fresh project. There is no environment to reverse-engineer.
Customer-specific configuration stays separate from logic. The new customer gets their own project, their own secrets in their own vault, and their own deploy history from the first push.
Validation happens before anything runs. swirls doctor checks the files locally, the free deploy tier lets you inspect the compiled project, and the first production execution happens only when you say so.
#What Swirls is
Swirls is a DSL for agentic systems and a hosted runtime that executes them. You write .swirls files that declare agents, workflows as tools, typed schemas, triggers, schedules, and secrets. Authoring is local and free. Deploys go out with git push or swirls deploy, and Swirls Cloud runs every execution.