How do I deploy a different AI agent for each customer?
#The question
If you are asking "How do I deploy a different AI agent for each customer?", you want this running without wiring up bespoke infrastructure. The short answer: describe the system in .swirls files, ship it with git push or swirls deploy, and Swirls Cloud runs it.
#Who's asking
Forward-deployed / solutions engineer. Tasked with standing up custom agent logic per customer or per org, comfortable in a terminal and IDE.
#Why Swirls is a fit
Swirls makes the agent a deployable artifact. You describe agents, workflows, tools, triggers, schedules, and secrets in .swirls files, then ship them with git push or swirls deploy. DSL in, running system out.
Your app becomes a thin consumer: a session id, a trigger, a response. Prompt assembly, tool calls, schedules, and audit move out of application code and into a deployed Swirls project.
Swirls files live in source control next to your application code. You review agent changes in a PR and read your operational process over time through git history.
#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.