Environments

Every Cube Cloud deployment provides a number of environments:

A single production environment.
Multiple staging environments.
Per-user development environments.

Available on all plans.

</InfoBox>

Production environment

This is the main environment. It runs the data model from the main branch.

Availability

The production environment is always available unless suspended.

Resources and costs

Depending on the deployment type, the production environment either runs on a development instance or on a production cluster with multiple API instances, incurring relevant costs.

Cube version

Production environments run a Cube version from the selected update channel.

Staging environments

Staging environments are activated automatically for specific source code branches when a branch is switched to in the Cube Cloud UI. Any development mode changes must be committed to a branch to be available in this environment.

Availability

By default, they are only active and accessible while viewed by at least one user. When no users are viewing the branch, the environment becomes inactive and inaccessible.

If you'd like to update this setting for a specific branch (e.g., for testing purposes), go to <Btn>Settings → Staging Environments</Btn> and check the toggle next to it:

Toggle off (default). A staging environment is only active when viewed by users. When no users are viewing the branch, queries to this environment will fail.
Toggle on. A staging environment remains always active and accessible, regardless of user activity.

Resources and costs

Staging environments run on development instances, incurring relevant costs. However, they automatically suspend after 10 minutes of inactivity, regardless of the availability setting, so you are only charged for the time when staging environments are being used.

Cube version

Staging environments always run the most up-to-date Cube version.

Development environments

A development environment is activated automatically when a user enters the development mode on a specific branch of the source code. It updates automatically when a user saves changes to the data model.

Only one development environment is allocated per user.

Availability

A development environment is only active and accessible while viewed by a user in the development mode. Otherwise, queries to this environment will fail.

Resources and costs

Development environments run on development instances, incurring relevant costs. However, they automatically suspend after 10 minutes of inactivity, so you are only charged for the time when development environments are being used.

Cube version

Development environments always run the most up-to-date Cube version.

{/*

TODO: Consumption? Resources? Move from http://localhost:3000/product/deployment/cloud/deployments#resource-consumption

*/}

API endpoints

Each environment provides its own set of API endpoints.

You can access them on the <Btn>Overview</Btn> page of your deployment or by navigating to the <Btn>Integrations</Btn> page and clicking <Btn>API credentials</Btn>.