Skip to main content
A project groups resources. It owns files, agents, jobs, deployments, integrations, access, logs, and usage. An environment is a named configuration inside a project. It scopes variables, secrets, domains, and deployment targets.

​
Why they are separate

Projects define ownership. Environments define runtime configuration. This keeps production settings separate from development or preview settings. Runtime state stays attached to the project that owns the work.

​
What belongs where

AreaOwns
ProjectMembers, API keys, integrations, source, agents, jobs, deployments, logs, and usage.
EnvironmentVariables, secrets, domains, deployment targets, and runtime settings.

​
When to add an environment

Use one project for an app or agent system. Use environments such as development, preview, and production for different secrets, domains, or deployment targets.