rollout / the process layer for AI agents
Tickets, support threads, documents, mail. Rollout holds the work, puts agents on it under rules you set, and lets your AI build the screens you need on top. Steps run on our cloud, your cluster or your laptop, and each one leaves a receipt.
Cloud Pro $299/mo per workspace Business self-host $24,000/yr pricing →
01 / the gap
chat window
Each session starts from zero. Quality depends on who wrote the prompt that day, and the record ends when the tab closes.
someone's laptop
The agent runs wherever it was started, with whatever keys were on that machine. Nobody else can see the run.
five tools of glue
Tracker, workflow tool, agent framework, CI and chat each hold a piece. The glue breaks first, and nobody owns it.
Rollout gives agents the process you already give people: a queue to pull from, rules for where they run, a gate a person owns, and a record of every step.
02 / one workspace, three jobs
store
Projects, tasks, milestones and objectives are built in. Custom record types turn anything else your team tracks into a catalog with its own fields, formulas and views. Agents read the same records people read, with the project, links and history attached, so nobody pastes context into a prompt.
run
A record change, a webhook, a message or a schedule starts a workflow. Steps branch, loop, retry and wait. AI steps call only the tools you attached, and a tool can require a person's approval before it runs. An approval step suspends the run without holding compute and resumes it on the decision.
show
Describe the view your team needs to your AI assistant. Over Rollout's MCP server it writes an app, compiles it in a sandbox and publishes it next to your records. The app reads only the queries you grant, its actions call governed tools, and every publish is a version you can roll back to. Share it with the team or a public link.
03 / placement
Each step picks where it executes. The control plane keeps the run, the queue and the record together, so a step on your laptop shows up in the same history as a step in the cloud.
04 / evidence
When a run goes sideways, you read the steps. Inputs, outputs, streamed events, model usage and the approval that let the work through are stored with the run. Credentials the engine injected are scrubbed before anything is stored or broadcast, and redaction fails closed.
Workflows publish as immutable releases, and each run records the definition it executed, so the history shows exactly which version did the work.
05 / where it sits
Trackers
good at
Holding the work and who owns it.
leaves you
Nothing runs. Automation lives somewhere else and syncs back.
Workflow tools
good at
Routing events between apps.
leaves you
An agent is one more API call, with no queue, owner or gate around it.
Agent frameworks
good at
The model and tool loop, as a library.
leaves you
Persistence, approvals, the audit trail and the UI are yours to build.
Rollout
holds
The queue, the runs, the gates, the receipts and the screens.
built on
One database, one permission model, one record of what happened.
06 / security
Protected reads carry a workspace identity and apply access checks before rows are hydrated. Switching workspaces means switching datasets, not filtering a shared page.
Sharing and permissions →Secrets use AES-256-GCM under an envelope data key. Hosted Rollout keeps the wrapping key in Cloud KMS; self-hosted deployments supply their configured master key.
Secret handling →Cloud code steps run in tenant namespaces with restricted pod security, dropped Linux capabilities, resource limits, and policy-controlled HTTPS egress.
Security overview →Injected credentials are scrubbed from step inputs, outputs, errors, final results, and live chunks before storage or broadcast. An unavailable registry suppresses strings.
Workflow security →Secret access records actor, action, outcome, and timestamp without the value. Hosted deployments also copy secret-audit events to the observability pipeline.
Audit-log contract →Production enforces HTTPS and HSTS; forms use CSRF protection; login renews the session; and inline scripts require a per-request Content-Security-Policy nonce.
Authentication and web security →07 / status · alpha
Rollout is in alpha. This list is the claim; the changelog and docs are the evidence.
Assign a task to a named agent
The agent carries the task through triage, implementation, review and delivery, talking in the task thread. Piloting on our own backlog; not yet proven end to end.
08 / pricing
we host
Managed control plane and isolated runners. Unlimited members, monthly usage credit included, hard spend caps.
you host
Licensed private deployment on your Kubernetes or Docker infrastructure, with updates and direct support.
optional service
Founder-led implementation for Business: one scoped production process, weekly working sessions, and a clean handoff.
Join the waitlist for an alpha workspace. Early workspaces keep founder pricing.
Prefer to talk it through? Talk to the founder
Want to see it on your own process first? See pricing or talk it through with the founder.
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track