--- title: "Provider accounts: servers you rent, joined through the provider’s API · Frazer" description: "Connect an OVHcloud account with a key scoped to its dedicated servers. Frazer reinstalls the servers you pick with its agent and a token bound to each, and they join a pool with their private network." url: https://frazer.ai/providers index: https://frazer.ai/llms.txt tokens: 2175 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Provider accounts: servers you rent, joined through the provider’s API · Frazer **Servers** frazer.ai # Connect your provider account. The servers you rent join themselves. Give Frazer a key scoped to your dedicated servers at OVHcloud. Pick the servers and type one confirmation: Frazer reinstalls them with its agent and a token bound to each, and they join a pool with their private network. Nothing to install by hand. [Connect a provider](https://frazer.ai/start?product=servers) [Read the docs](https://frazer.ai/docs) *The Import servers screen in the Frazer console. 3 of 5 servers in the OVHcloud account acme-ovh are selected; the reinstall that erases them is confirmed by typing “erase 3 servers”; the plan reinstalls each with Ubuntu 26.04 and a bound join token, accepts it automatically, inspects it and adds it as a substrate host in the pool vint-hill-default. On the right: the scoped API credential, stored in Frazer Secrets and never shown again, and five passed prerequisites with one warning.* Import three servers from an OVHcloud account product UI, demo organization 01 · How it works Fig. 1 ## From an API key to a pool. Each server bound to its own token. **Fig. 1** An import through a provider account, lane by lane 02 · The key and the plan ## A key that can do four things. A plan before anything is erased. Frazer shows the exact rights it needs and refuses a key with more. The import is a plan you read first, from the console or the CLI. `GET /dedicated/server/*` List the account’s dedicated servers with model, datacenter and IPs. `POST …/reinstall` Reinstall the servers you picked, with the agent and a bound token in the user data. `POST …/reboot` Reboot or power-cycle a server that stops answering. IP moves Move the additional IP blocks your site uses for load-balancer addresses. ``` $ frazer servers import ovh --account acme-ovh \ --servers ns5012345,ns5012346,ns5012347 \ --pool vint-hill-default --dry-run Plan p-0031 · 3 servers · expires in 24 h or when acme-ovh changes ! Reinstall erases every disk on 3 servers + Server Atlas, Borealis, Cobalt · Ubuntu 26.04 · bound join token + ServerPool vint-hill-default · substrate host · wipe crypto-erase + Substrate acme-vint-hill · forms at 3 hosts · Acme only Cost 96 physical cores · $144.00 a month while accepted ? Type "erase 3 servers" to apply: ▌ ``` 03 · Providers ## OVHcloud, Hetzner and more. One import for every provider. Providers Frazer supports through a provider account | Provider | What Frazer does | Private network | Credential | | --- | --- | --- | --- | | OVHcloud | Lists your dedicated servers, reinstalls the ones you pick through the API with the agent in the user data, reboots them and moves IPs. | vRack, plus additional IP blocks routed to it | Scoped consumer key | | Hetzner | Boots the rescue system with a one-time SSH key, writes the image from rescue and reboots; the same bound token. | vSwitch | API token + Robot user | | Latitude.sh | Reinstalls the servers you pick through the provider’s API. | — | API key | | Vultr bare metal | Reinstalls the servers you pick through the provider’s API. | — | API key | | Scaleway Elastic Metal | Reinstalls the servers you pick through the provider’s API. | — | API key | | Any other provider | Add it with [`frazer servers add`](https://frazer.ai/docs/servers#add-a-server-with-the-cli), or run the install command or boot the image on the server; no provider account needed. | Your own | Join token | 04 · What you get ## Your servers, our install. Nothing to do by hand. - ### Four routes, nothing broader Frazer checks the key’s scope and refuses a key with more rights than it needs. - ### Shown once The key is tested, kept in Frazer Secrets in your infrastructure project, and shown afterwards only as a fingerprint. - ### A token per server Single use, valid 3 hours, bound to the provider’s service name, and delivered only inside the reinstall. - ### No accept click The pool accepts a join only when token, service name and the server’s IP all match. Any other join waits for a person. - ### Typed confirmation A reinstall erases every disk, so you type it out: `erase 3 servers`. - ### The private network comes along The provider’s private network and IP blocks become the site’s network and its load-balancer addresses. - ### Power-cycled through the API A server that stops answering is power-cycled through the provider, one server, or 10 %, per pool at a time. - ### Hetzner Rescue boot with a one-time SSH key, the image written from rescue, the same token binding. 05 · Controls ## Every erase is typed out. And on the record. ### Who may do what Owner or Admin Connects a provider account and applies an import plan. Servers admin Picks the site, the pool and its accept rule. Sharing the pool with projects takes its own permission. Agents Read through MCP by default; a reinstall always needs an admin’s typed confirmation. Frazer Calls only the routes the key allows, and only from a plan you applied. ### What is logged - The plan, the typed confirmation and the provider’s task IDs - The key test and its fingerprint, never the key - Each join: the token, the service name and the rule that accepted it - Every reinstall, reboot and power cycle, with its result ### At the cap - **Key scope:** a key with more than the four routes is refused - **Plan:** expires in 24 h, or when the provider account changes - **Repairs:** at most one server, or 10 %, per pool at a time - **Budget cap:** refuses new billable items, such as accepting more servers; workloads on your servers never stop 06 · Pricing ## Your provider bills the server. Frazer bills the management. You keep paying your provider for the machine, as today. Frazer charges its management fee per physical core while a server is accepted; the provider connection is included. [See every price](https://frazer.ai/pricing#lines) Your provider The server, on your own account Frazer $1.50 per physical core / month · min $15, max $150 per server · first server ≤ 16 cores free Connection **Included** Questions ## Provider accounts, answered. Which providers can I connect? OVHcloud, through a key scoped to its dedicated servers; Hetzner, through an API token and a Robot user; Latitude.sh, Vultr bare metal and Scaleway Elastic Metal, through an API key. A server at any other provider joins with the install command or the boot image instead. What does the reinstall erase? Every disk on the servers you pick. Anything still running on them has to move first. The plan names each server, and you type the confirmation before Frazer calls the provider. Why do these servers skip the accept step? Frazer started the reinstall itself, and each server’s token is single use, valid 3 hours and bound to that server’s service name. The pool accepts the join only when token, service name and IP all match. Any other join waits for a person. What can Frazer do with my key? List your dedicated servers, reinstall and reboot the ones you imported, and move IP addresses. Frazer refuses a key with broader rights, keeps it in Frazer Secrets in your infrastructure project and never shows it again. Can I bring a server without reinstalling it? Not through the provider account: the reinstall is what binds the server to its token. To keep a running system, add it with [`frazer servers add`](https://frazer.ai/docs/servers#add-a-server-with-the-cli) or the install command. Nothing is wiped; it joins as a dedicated node, and you keep patching its OS. Do I still pay my provider? Yes. The server stays on your provider account and your invoice. Frazer bills its per-core management fee; detach the server to stop it, and cancel the server at your provider. ## More in Servers - [**Bring your own** Install command, boot image or provider account](https://frazer.ai/servers) - [**Your cloud accounts** Instances join, clusters attach](https://frazer.ai/cloud) - [**Buy from Frazer** Dedicated servers by the month](https://frazer.ai/servers/buy) - [**Real hardware** What Frazer needs from a server](https://frazer.ai/hardware) - [**How it works** From a join token to a running cluster](https://frazer.ai/how-it-works) - [**Regions and sites** Where Frazer runs, where servers are](https://frazer.ai/regions) ## Connect your provider. Your servers join on their own. [Connect a provider](https://frazer.ai/start?product=servers) [Read the docs](https://frazer.ai/docs)