Your sites. Our regions.
Joined by an outbound link.
A site is where your servers are: one data center, rack or office with a fast private network, and one failure domain. A region is where Frazer runs the control plane and the Frazer Link gateways your sites dial out to. Frazer’s region is us-virginia1, in Virginia, USA.
Sites dial out to a region.
Nothing dials in to a site.
Where Frazer runs.
Named for the place.
A region holds a complete copy of Frazer’s control plane and the Frazer Link gateways your agents connect to. Regional services carry the region in their host name. Each region has one zone: its servers share one hall, so they are one failure domain.
| Region | Location | Zone | What runs there |
|---|---|---|---|
us-virginia1 | Virginia, USA | us-virginia1-a | The control plane and Frazer Link for the organizations that live here; the global layer; servers from Frazer |
A site is one failure domain.
A cluster never spans two.
Servers in a site sit under 2 ms apart on one private network: a provider data center and its private network, a rack, an office. A site lives in your infrastructure project and holds its network mode, its address pools and its requirement checklist.
| The site has | Public traffic reaches it |
|---|---|
| Public IPs on its servers, as at OVHcloud or Hetzner | Gateways on addresses from the site’s IP pools, such as additional IP blocks routed to the private network |
| A private LAN whose router speaks BGP | Your router advertises the addresses upstream |
| A private LAN without BGP | You forward a public IP to an address Frazer announces on the LAN |
| NAT only, no public IPs | Through an outbound tunnel from the cluster’s gateway; or internal only |
Your workloads stay at your site.
The control plane stays in the region.
| Where | What runs there | Who sees it |
|---|---|---|
| Your site, on your servers | Your project clusters, as VMs on the pool substrate or on whole servers. The Frazer-run clusters behind serverless, managed databases and runners. Frazer Cache. | Your projects. The Frazer-run clusters never appear in a project’s cluster list. |
| The region | The API, workers, Frazer Link, the registry and secrets, the LLM gateway, Security Center, dashboards and alerts. | Frazer runs it. Your records in it are keyed to your projects. |
| Global | Accounts and sign-in, the organization directory, billing and the console’s static files. | Frazer runs it. |
| Off-site | Encrypted backups of the control plane, at a second provider. | Frazer, for recovery. |
Servers wherever you have them.
A control plane nearby.
Your organization lives in one region
Chosen at sign-up, usually the one nearest your servers. A move is a planned migration.
Regions share nothing
Each region’s control plane has its own database and credentials.
Sites anywhere
Any data center, rack or office with egress on 443, NTP and DNS. An HTTP proxy works.
A cluster in one site
Its control-plane VMs spread over three servers and racks inside that site.
Names carry the place
projects/acme-infra/locations/us-virginia1/sites/ovh-vint-hillRegional host names
registry.us-virginia1.frazer.aiandlink.us-virginia1.frazer.ai.Your clusters keep running
If the region is unreachable, agents keep their local state and the cluster’s GitOps keeps syncing.
Public names for NAT-only sites
An outbound tunnel from the cluster’s gateway to the Frazer edge.
Sites change by plan.
Each change a revision.
Who may do what
- Servers admin
- Creates and edits sites as plans; every edit is a revision.
- Whoever creates the organization
- Picks its region at sign-up. A later move is a planned migration.
- Projects
- Get capacity at a site only through pools shared with them.
What is logged
- Site changes, with the plan and the revision
- The requirement checks the agents run on each server
- Placements on a site’s pools, in both projects’ audit logs
At the cap
- One site per cluster: a cluster never spans two sites
- Addresses: gateways get addresses only from the site’s IP pools
- Placement: a production cluster’s three control-plane VMs always go to three servers
- Full pool: new creates are refused; nothing is evicted
Regions and sites, answered.
Where can my servers be?
Anywhere they can reach Frazer outbound: a provider data center, a colocation rack or your office. A site needs egress on TCP 443 and UDP 51820 (or 443 only), NTP and DNS; an HTTP proxy works.
What is the difference between a region and a site?
A region is Frazer’s: it runs the control plane and the Frazer Link gateways. A site is yours: it is where your servers are. Each site is served by one region, and the region is part of the site’s name, as in projects/acme-infra/locations/us-virginia1/sites/ovh-vint-hill.
Can a cluster span two sites?
No. A site is one failure domain, under 2 ms between servers, and a cluster lives in one site. For two sites, run two clusters.
Where is my data stored?
Your workload data stays on your servers at your site. The control plane in your region keeps metadata, never workload data, and backs it up encrypted to a second provider.
Which region does my organization use?
One region, chosen at sign-up, usually the one nearest your servers. Moving to another region is a planned migration.
What if my data has to stay in another country?
Tell us where. A region is added where customers need their data, with its own control plane, and an organization moves to it as a planned migration.
More in Servers
- Bring your ownInstall command, boot image or provider account
- Provider accountsServers you rent, joined through the API
- Your cloud accountsInstances join, clusters attach
- Buy from FrazerDedicated servers by the month
- Real hardwareWhat Frazer needs from a server
- How it worksFrom a join token to a running cluster