Rollout is an operations rollout workspace for modeling business context, connecting tools, and running durable governed workflows. It combines workflows, custom records, documents, dashboards, work management, integrations, model-driven steps, and client-side execution into one deployable system. It is currently in alpha, so expect rapid iteration and breaking changes.
Mental model
- Workspace - Projects, tasks, objectives, records, documents, dashboards, and activities give people, workflows, and model-driven steps shared business context
- Automation - Workflows, runs, steps, triggers, approvals, and integrations execute business processes
- Governed capabilities - Models, code, MCP tools, server integrations, and client-side execution can act on workspace context with auditability
- Deployment - Rollout runs inside your infrastructure and can be driven by people, APIs, webhooks, client devices, and MCP clients
Who it's for
- Engineers and platform teams - Build durable automations for APIs, webhooks, client-device actions, MCP tools, and data processing
- Operations and program leads - Inspect runs, coordinate follow-up work, and keep execution tied to business records, tasks, documents, and OKRs
- Teams that self-host - Keep workflow execution and business data inside infrastructure they control
What you can build
- Projects & Tasks - Plan work with statuses, priorities, milestones, and timelines
- Record Types & Records - Model any domain (contacts, candidates, vendors) with flexible schemas
- Dashboards & Widgets - Personal dashboards with live workflow, task, and project widgets
- Automation Runtime - Triggers, model-driven steps, code, approvals, and integrations to move data and act
- Desktop Companion - Connect a device to run local commands, browser automation, and approval-sensitive actions
- AI Assistant Integration - Connect Claude Code or other MCP clients to manage your workspace
Quick start
- Quick Start Guide - Create your first project and workflow
- Projects & Tasks - Organize work with views and statuses
- Record Types & Records - Build custom record types and records
- Dashboards - Add widgets and saved dashboard views
- Visual Workflows - Learn the runtime, editor, and node types
- Desktop App - Connect the desktop companion
- MCP Integration - Connect AI assistants like Claude Code
Core concepts
Projects and tasks
Projects coordinate related work across Teams. Tasks track individual items with statuses, priorities, rich descriptions, and an explicit planning Team. Team-owned Cycles provide numbered, time-boxed planning and immutable delivery evidence.
Record types
Record types are custom data models you define for your business. Each record type has fields, labels, and display settings, and each record can link to tasks, projects, or workflows.
Dashboards and widgets
Dashboards are customizable grids of widgets. You can also embed live widgets directly inside rich text fields using the slash command menu.
Workflows
Workflows are visual automations built from nodes connected on a canvas. A trigger node starts the run, action nodes do the work, and utility nodes branch or merge data. Workflows are the control plane for business processes, not the whole product.
Vocabulary
- Workflow - The automation definition
- Draft - The continuously autosaved working copy of a workflow; production never runs it
- Release - An automatically numbered, immutable revision created by publishing a Draft
- Current Release - The release selected for new production runs
- Running / Paused - Whether the Current Release can accept new production runs
- Run - One execution of a workflow
- Step - One executed node inside a run
- Branch - An optional authoring line with its own autosaved Draft; publishing it creates a release with branch provenance
- Record Type / Record - Custom business data models and their instances
- Relationship - A typed link between resources or records
Connections
Connections link your team to external services. The catalog includes Google (Gmail, Sheets, Drive, and Calendar), GitHub, Atlassian (Jira), Telegram bots, SSH hosts, Tailscale, container registries, 1Password, bring-your-own LLM providers, vector stores, and speech providers. The API Request node can reach any REST API, and MCP/client capabilities expand what workflows and model-driven steps can call.
Desktop companion
The desktop app connects a device to your account, enabling local shell commands, browser automation, Claude Code/Codex sessions, and approval-sensitive actions from workflows.
Features overview
| Feature | Description |
|---|---|
| Projects & Tasks | Statuses, priorities, milestones, board/timeline views |
| Objectives & Key Results | Objectives with measurable key results and progress tracking |
| Record Types & Records | Flexible record types with rich fields and presets |
| Dashboards | Widgets and views with live data |
| Visual Workflows | Automation control plane with triggers, actions, integrations, and run history |
| Integrations | Server integrations, API Request, webhooks, MCP, and client capabilities |
| MCP Integration | Connect AI assistants like Claude Code |
| Desktop App | Device automation and command center |
| Security | Auth, sessions, and tenant isolation |
| Licensing | Business self-hosting and private distribution |
Need help?
Start with Getting Started for a hands-on walkthrough, or jump to Visual Workflows to learn about building automations.