> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing Geography

> Choose where your published project runs and stores data by selecting a publishing geography.

When you publish a Replit project, you can choose the geographic region where your project's compute and storage resources are hosted. By default, Replit recommends the geography closest to you. This helps reduce latency for your app's visitors and meet data residency requirements.

<Note>
  Publishing geography selection is available to builders on Core, Pro, and Enterprise plans.
  Free plan builders publish to the North America geography by default.
</Note>

## Available geographies

Replit supports the following publishing geographies:

| Geography         | Description                                   |
| :---------------- | :-------------------------------------------- |
| **North America** | Hosts your project in North America (default) |
| **Europe (EU)**   | Hosts your project in the European Union      |
| **South America** | Hosts your project in South America           |
| **Australia**     | Hosts your project in Australia               |
| **Asia**          | Hosts your project in Asia                    |

<Note>
  North America and Europe (EU) are available to all eligible builders. South
  America, Asia, and Australia are rolling out gradually and may not yet be
  visible in the geography dropdown. If you don't see a geography you need,
  contact Replit support.
</Note>

When you select a geography, all published artifacts for your project (such as compute, database, and Object Storage) are automatically colocated in the same region. A geography-specific proxy also helps reduce latency for your app's visitors.

## Selecting a geography

By default, Replit recommends the geography closest to you. To choose a different geography:

<Steps>
  <Step>
    Open the **Publishing** tool in your Replit project.
  </Step>

  <Step>
    Expand the **Advanced** settings.
  </Step>

  <Step>
    Select your preferred geography from the **Geography** dropdown.
  </Step>

  <Step>
    Select **Publish** to publish your project to the selected geography.
  </Step>
</Steps>

<Frame>
  <img src="https://mintcdn.com/replit/rgMTJtOfbKf1GQ8o/images/changelog/2026-04-10/geography-dropdown.png?fit=max&auto=format&n=rgMTJtOfbKf1GQ8o&q=85&s=3cfc403cf106ba26e1899a7b5c383704" alt="Geography dropdown in the publishing Advanced settings showing Europe selected as Closest, with North America, South America, Asia, and Australia also available" width="1368" height="690" data-path="images/changelog/2026-04-10/geography-dropdown.png" />
</Frame>

## Enforcing a geography on published projects

Enterprise admins can enforce a publishing geography for all projects across their organization. When a policy is set, builders in the organization publish to the configured geography. This policy applies only to projects that have not yet been published — projects already published to a different geography are not affected.

<Note>
  Enforcing a publishing geography is an Enterprise feature. To learn more about Enterprise plans, see [Pricing](https://replit.com/pricing/).
</Note>

<Steps>
  <Step>
    Navigate to your **Account settings**.
  </Step>

  <Step>
    Select **Advanced**.
  </Step>

  <Step>
    Choose the geography that all projects published for the first time must use.
  </Step>
</Steps>

## Limitations

Before selecting a geography, keep the following limitations in mind:

* **Geography cannot be changed after publishing.** Once you publish your project to a geography, that selection is permanent. You cannot migrate a published project to a different geography.
* **Development environment artifacts may not match your published geography.** Resources such as Object Storage can be created before you publish. All development environments currently run in North America. Support for hosting your development environment in the nearest publishing region is coming soon.

## Next steps

* [Autoscale Deployments](/cloud-services/deployments/autoscale-deployments/): Learn how autoscaling adjusts capacity based on traffic.
* [Reserved VM Deployments](/cloud-services/deployments/reserved-vm-deployments/): Publish your project to a dedicated virtual machine.
* [Published App Monitoring](/cloud-services/deployments/monitoring-a-deployment/): View logs and monitor your published project.

To learn more about how Replit handles data processing, see the [Data Processing Addendum](https://replit.com/dpa).