Project environments
Give each application environment the source, settings, and destination it needs while keeping production changes deliberate.
Open the guideHow it works
Use environment-specific projects and supported environment configuration for branches and destinations. Review source, variables, domains, and dependencies before deployment.
Previews add a pull-request lifecycle; production should use its intended branch and release checks. Database access and persistent data remain explicit choices for each environment.
What you can do
Separate settings
Review variables, domains, and destinations.
Branch context
Deploy the revision intended for staging or production.
Shared visibility
Give teammates access to the required project context.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.