Tinybird deployments

Changing state in data infrastructure can be complex. Each state transition must ensure data integrity and consistency.

Tinybird deployments simplify this process by providing robust mechanisms for managing state changes, allowing you to validate and push updates seamlessly while minimizing the risk of data conflicts or loss.

Deployment methods

The following deployment methods are available:

Deployment lifecycle

The following steps describe the typical deployment lifecycle.

1

Local development

First, you develop locally using the Tinybird Local container.

When your development is complete, build the project to validate your changes. See tb build.

After the build completes, you can create a local deployment to ensure a successful migration between project states. See tb deployment create.

2

Preview your changes

Once your local deployment succeeds, you can create a preview deployment in Tinybird Cloud.

Tinybird creates this deployment in a staging environment to validate your changes and test them against the same data as the live deployment. See tb deployment create.

Preview deployments use the same database resources as the live deployment.

3

Promote your changes

After you validate the preview, promote it to a live deployment to make the changes available to your end users. See tb deployment promote.

Tinybird only supports one live and one preview deployment per Workspace.

Next steps