Concepts
Projects
Projects partition workflows, runs, channels, actions, and related operational resources within an organization. They're the right tool when you want logical isolation such as separate environments, products, or customer lanes while keeping one billing and identity boundary.
When to use projects
| Goal | Use |
|---|---|
Separate dev, staging, prod for one team | Projects |
| Separate two unrelated companies | Organizations |
| Separate two products in one company | Projects |
A workflow, run, channel, trigger, webhook, and worker pool all operate within exactly one project. API keys are created at the organization level, and some flows can pin them to a single project.
Handles and routing
Projects are addressable by handle in URLs:
/app/projects/production/workflows
/app/projects/production/runs/run_abc123Handles are unique within an organization and form the basis of every project-scoped API endpoint and app route.