Deployment Regions

Deploy preview environments closer to your users for faster load times. prev.sh operates edge nodes in four regions worldwide, each running a fully independent stack.

Available Regions

Region Architecture

Each region runs a fully independent edge node with its own API server, container orchestration, image registry, and TLS-terminating proxy. Your preview environments are served entirely from the region you choose — no cross-region hops for requests.

Selecting a Region

Individual Plan

Individual plan users select their deployment region once in the Dashboard Settings. This is a one-time choice — once confirmed, all your environments will deploy to that region. The --region CLI flag is not used; your configured region is applied automatically.

> Note: You must select a region in the dashboard before creating your first environment. The CLI will prompt you to visit the dashboard settings if no region has been configured yet.

Business Plan

Use the --region flag when creating an environment:

prev create . --region eu

If no region is specified, environments are deployed to us by default.

Choosing the Right Region

Pick the region closest to the people who will be viewing your previews:

• US — Best for North American teams and clients
• EU — Best for European teams, also good for UK and Middle East
• APAC — Best for Southeast Asia, Australia, India, and East Asia
• LATAM — Best for South American teams and clients

Plan Requirements

• Individual plan: Choose one region from all 4 available regions (set once in dashboard settings)
• Business plan: Choose from all 4 regions per environment

Using with Templates (Business)

Set a default region in your deployment template:

prev create . --template eu-staging

You can still override the template's region:

prev create . --template eu-staging --region apac

Preview URLs

Your preview URL includes the region code:

https://<subdomain>.<region>.prev.sh

For example: https://cosmic-falcon.eu.prev.sh