Last update: 2025-06-10T22:41:34.000Z
Content:
---
title: "Self-managed regions · Tinybird Docs"
theme-color: "#171612"
description: "Create your own Tinybird Cloud region in the cloud service provider of your choice."
inkeep:version: "forward"
---




# Self-managed regions [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#self-managed-regions)

Copy as MD By default, Tinybird relies on [Tinybird managed regions](/docs/api-reference#regions-and-endpoints) . Self-managed regions allow you to run Tinybird infrastructure in your own cloud environment while still benefiting from Tinybird Cloud's management capabilities. This gives you more control over data residency, compliance requirements, and infrastructure costs while maintaining the same Tinybird experience.

Self-managed regions are currently in beta. Use them for development environments only; avoid production workloads. Features, requirements, and implementation details might change as we continue to improve this capability.

## Key benefits [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#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.
- Complete customization: Tailor performance by optimizing hardware resources for your specific workload patterns.
- Cost efficiency: Avoid egress fees and leverage your existing cloud commitments and reserved instances.

## Limitations [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#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 [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#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 gives you complete control over your data and infrastructure while maintaining the familiar Tinybird developer experience.

## Add a self-managed region [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#add-a-self-managed-region)

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

- Manually. See[  Create a self-managed region manually](/docs/forward/install-tinybird/self-managed/manual)  .
- Using the `tb infra init`   command. See[  Use the CLI to add a self-managed region](/docs/forward/install-tinybird/self-managed/assisted)  .

## Supported clouds [¶](https://www.tinybird.co/docs/forward/install-tinybird/self-managed#supported-clouds)

The following cloud service providers are supported:

- AWS
- GCP (Coming soon)
- Azure (Coming soon)



You can also create a self-managed region by deploying the container on the following Platform as a Service (PaaS) providers:

- Fly.io
- Zeet
- Google Cloud Run
- CloudFoundry
- Azure Container Instances
- DigitalOcean App Platform

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](/docs/forward/dev-reference/commands/tb-infra) for more information.


