Rent a server Frazer owns.
Burned in before. Wiped after.
Pick a region, a server type and a term. Frazer installs Frazer OS, burns the server in and hands it to your pool, dedicated to your organization. When the term ends it is wiped, with a certificate in your audit log, before anyone else gets it.
A rental, stock to stock.
It changes hands only through a wipe.
Same pools.
Different promises.
A rented server and one you bring sit in the same pools and serve the same clusters. What differs is who owns it, what runs on it and how it leaves. For capacity by the second instead, see the Frazer fleet.
| Aspect | Your servers | Rented from Frazer |
|---|---|---|
| Owner | You, or your provider | Frazer |
| Who may run on it | Only your organization | Only your organization, for the term |
| You pay | Your provider for the machine; Frazer per physical core | Provider price + 25 %, monthly, management included |
| Operating system | Frazer-installed Ubuntu, or yours, added with frazer servers add | Frazer OS only |
| Before it takes work | Inspection; burn-in if you ask for it | Inspection and a mandatory burn-in |
| A part fails | You or your provider replace it | Frazer replaces it |
| Identity | Key on disk or sealed in the TPM | Measured boot, checked against a Frazer-signed image |
| When it leaves | Detach any time; keep or wipe the disks | Full wipe, certificate, burn-in check, back to stock |
Wiped before anyone else.
With a certificate you can download.
A reset is not enough between tenants. Every disk Frazer formats is encrypted, so the wipe starts by destroying its key.
- 01
Destroy the key
Every data disk is LUKS2 with a per-server key; the wipe destroys it first.
- 02
Sanitize
NVMe sanitize or a secure format, or ATA secure erase.
- 03
Discard
blkdiscard over every block.
- 04
Verify
Sample reads prove the disks read back empty.
- 05
Certify
Who, when, the method, disk models and serials, the result: in your audit log, downloadable.
A whole machine.
Looked after by us.
Dedicated for the term
The whole machine is yours: no other company’s VMs or containers on it.
Burned in first
CPU, memory, disk and network stress tests before it reaches your pool; GPU servers run a GPU stress test for 24 hours.
Frazer OS
Immutable, A/B updates and measured boot, patched by Frazer in your maintenance window.
Parts swapped
Frazer replaces failed hardware. Part swaps, burn-in and the wipe certificate are in the price.
Your pools, your sharing
A rented server joins a pool in your infrastructure project and is shared to projects like any other.
Longer terms, lower price
12 months −10 %, 36 months −20 %, taken from the margin and never below cost.
A ceiling on rentals
An organization-wide limit on rented servers protects the bill.
GPU servers
Data-center GPUs by order, with a delivery date on the quote before you approve.
An owner approves every order.
Caps never switch a server off.
Who may do what
- Org owner
- Approves the order and its quote, and ends a rental early.
- Billing admin
- Holds the payment method and the budgets and caps that bound the spend.
- Servers admin
- Puts rented servers in pools; sharing a pool with projects takes its own permission.
- Frazer
- Runs the OS and the agent and swaps parts. It has no path to your workload data.
What is logged
- The order, its quote and the owner’s approval
- Provisioning, inspection and the burn-in report, per server
- Every operation Frazer runs on the server, with its result
- The wipe certificate at the end, in your audit log
At the cap
- Budget cap: new orders are refused; a rented server is never powered off during its paid term
- Rental limit: an organization-wide ceiling on rented servers
- Payment: a card on file or an invoice account before the order
- Nothing is ordered before Apply
The provider’s price, plus 25 %.
Management included.
Rented servers are billed monthly at the provider’s price plus a published markup, with management included and setup fees passed through. Longer terms come out of our margin, never below cost.
See every priceServers from Frazer, answered.
Can I install my own operating system?
No. Rented servers run Frazer OS only, so they can prove what they booted and change hands safely. If you need your own OS, bring your own server.
Who else can use my rented server?
Nobody outside your organization, for the whole term. Inside it, the server joins a pool that you share with your projects.
What happens when the term ends?
Frazer drains the server, destroys its disk keys and sanitizes every disk, puts the wipe certificate in your audit log, runs a burn-in check and returns it to stock.
Where are the servers?
In Frazer’s region in Virginia, USA (us-virginia1). Regions and sites explains how a region differs from the site where your other servers are.
What if a part fails?
Frazer drains the server and replaces the part; you do not open a ticket with anyone. Part swaps are included in the price.
Can I move a rented server to another project?
Yes, within your organization. An available server moves between projects of one organization and joins a pool there, under that pool’s wipe policy.
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
- Real hardwareWhat Frazer needs from a server
- How it worksFrom a join token to a running cluster
- Regions and sitesWhere Frazer runs, where servers are