How do I manage agent logic across many tenants?
#The question
"How do I manage agent logic across many tenants?" comes down to giving an agent a real operational story. Swirls does that by making the agent a deployable artifact: declare it in .swirls files and ship it with git push or swirls deploy.
#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.
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 the artifact and the runtime for agentic systems. The artifact is a set of .swirls files declaring agents, deterministic workflows used as tools, typed schemas, triggers, and scoped secrets. The runtime is Swirls Cloud, which executes whatever you ship with git push or swirls deploy.