Getting startedRegion
Where your apps run
Orbits has one region, Abuja in Nigeria (abj-1). Every build and every app runs there.
Orbits runs in one region: Abuja, Nigeria, with the code abj-1. There are no other regions, and no choice to make. The Region field on New project and in a project's settings shows Abuja (abj-1), and it is the only value the API accepts for a project or a team.
What runs there
- Builds. Your code is cloned, installed and built in Abuja.
- Apps. Production and preview deployments run in Abuja, and their addresses, free (
theorbits.app) and custom, are served from there. - Orbits DNS. If you hand a domain's DNS to Orbits, its nameservers answer from there too.
What it means for latency
Visitors reach your app over the internet from wherever they are, and every request travels to Abuja and back. For visitors in Nigeria and West Africa that is a short trip. Visitors further away see the extra distance on every request that reaches the app.
A few things help:
- Keep the app close to its data. If your app talks to a database, put the database near Abuja, so each request doesn't make several long trips.
- Let browsers cache what doesn't change. Fingerprinted assets (a framework's built JavaScript and CSS) can carry long cache lifetimes, so a returning visitor doesn't fetch them again.
- Watch real numbers. Speed Insights reports Web Vitals from your visitors' browsers, and observability shows request durations as the app sees them.
Using the region in the API and CLI
Projects and teams carry their region as abj-1:
{
"slug": "storefront",
"region": "abj-1",
"free_address": "storefront.theorbits.app"
}You don't need to send it when you create a project: it defaults to abj-1, and any other value is refused.