Self-managed¶

By default, Tinybird runs on Tinybird managed regions. Self-managed regions let you run Tinybird infrastructure in your own cloud environment while Tinybird Cloud manages the control plane. Use them when you need control over data residency, compliance requirements, or infrastructure costs.

Key benefits¶

Key benefits of self-managed regions include:

• Data sovereignty and compliance: Keep your data in specific geographic locations to meet regulatory requirements.
• Integration: Connect directly to your existing data sources and internal systems without data leaving your network.
• Infrastructure control: Tune hardware resources for your workload patterns.
• Cost efficiency: Avoid egress fees and use your existing cloud commitments and reserved instances.

Limitations¶

Self-managed regions have some limitations compared to Tinybird managed regions:

• You are responsible for infrastructure maintenance, scaling, and security.
• Some advanced features may require additional configuration.
• Performance tuning and optimization are your responsibility.
• Upgrades must be managed manually by redeploying with newer container versions.

How self-managed regions work¶

When you set up a self-managed region:

1. You register a region with Tinybird Cloud.
2. You deploy the Tinybird Local container in your cloud environment.
3. You interact with your self-managed region directly using the Tinybird CLI with the --cloud flag.

This approach keeps your data and infrastructure in your cloud environment while Tinybird Cloud manages the region metadata.

Add a self-managed region¶

There are two main ways to create a self-managed region:

• Manually: See Create a self-managed region manually.
• Using the CLI: See Use the CLI to add a self-managed region.

Supported clouds¶

The following cloud service providers are supported:

• AWS
• GCP (Coming soon)
• Azure (Coming soon)

When deploying Tinybird Local on a PaaS, make sure to expose the following environment variables to the container:

• TB_INFRA_TOKEN
• TB_INFRA_WORKSPACE
• TB_INFRA_ORGANIZATION
• TB_INFRA_USER

See tb infra for more information.