Hub Cloud · Instances
Same app. Separate environments.
Keep production and staging separate, with independent URLs, releases, environment variables, access, and data volumes.
A place to test the next change.
Name the instance when deploying. The default is prod; my-app and my-app/prod are equivalent.
Run from your project after installing the CLI and signing in.
Terminal · Deploy to staging
hub deploy --name my-app --instance stagingSeparate configuration and releases.
Staging changes leave production untouched. GitHub-connected instances can follow different branches.
Access for each environment.
Keep staging restricted while production is public. App invitations still cover every instance.
Choose who can open it →Independent persistent data.
Each instance has its own service project and named volumes. New instances do not copy the database.
The same tools, a different target.
Target app/instance in the CLI. Your agent and workspace use the same environments.
Start with the Skill and hosted MCP, or use the CLI for local files.
Terminal · Inspect staging
hub app my-app/staging status
hub app my-app/staging logs