Managed GPU infrastructure · Amsterdam · Frankfurt · Singapore
The compute is yours.
The data-centre layer is ours.
We run GPU racks for our customers in Europe and Asia-Pacific: power, cooling, uplink, spares and 7 × 24 on-site staffing. Monthly uptime goes into the contract, and missing it credits you automatically. The hardware can be bought, rented by the GPU-hour, or already yours.
Typical rack section · schematic
Your compute— GPU nodes you bought or rent by the term.
The layer we run— space, A/B power, cold aisle, uplink, spares, staffing.
- Rack-ready
- 5 – 10 days
- On-site staffing
- 7 × 24
- Part swap
- Spare on site +4 h
- Contracted uptime
- ≥ 99.9%
- Zones
- AMS · FRA · SIN
The layer we take over
What we operate
When one of these six fails, your training should not stop and your people should not be woken up.
PWR
Space and power
A/B utility feeds, UPS and diesel behind them, 12 – 15 kW per rack. Minutes of power loss are reported monthly at rack PDU level.
COOL
Cooling
Contained cold aisle, intake at 22 ± 3 °C and 40 – 60% RH, temperature curve included in the monthly report. We own the intake side; temperatures inside the chassis follow your load profile.
NET
Network
2 × 100 G uplink, direct peering with AMS-IX / DE-CIX / SGIX, BGP with your own IP range. We commit to the rack-to-uplink-port segment.
OPS
Hardware on call
Someone is on site 7 × 24. A dropped GPU, a stopped fan or a tripped PDU is not your 3 a.m. problem: fitted and power-on tested within 4 hours of the spare arriving. Spare arrival time depends on supply and is written into the contract annex.
ASSET
Racking and asset records
Unboxing inspection photographed, cabling, asset labels applied. The delivery list is a CSV you can import straight into your CMDB: serial number, warranty start and end, burn-in report link.
RPT
Monthly report and credits
One per month: uptime, minutes of power loss, intake temperature, ticket response times. Below the contracted figure the credit is automatic and deducted from the following month's invoice — you do not file a claim. Credits are capped at that month's hosting fee for that rack; the measurement basis and the exclusions are in the terms.
What one node looks like, and the seven places we watch
Inside one node · orthographic
Front and top views of a 4 U GPU node. Seven positions are marked: which layer is your asset, and the six we watch every day. Model and configuration are in the plan we send you.
Fig. 01 — 4 U GPU node · front & top
- Front drive baysSystem and local cache drives, hot-swappable. Swapping a drive does not stop the node.
- Perforated intake faceFaces the cold aisle, intake at 22 ± 3 °C. Open area decides whether this node can absorb a full 15 kW rack.
- Status and identityOn-site staff locate by light. The dashed box beside it is the asset label position: serial number and warranty dates go there.
- Rack ears · 19″Standard hole pattern. Racking changes nothing structurally, including for hardware you bring in.
- GPU modules × 8The yellow layer is yours. High-speed inter-GPU links, 72 hours at full load before it leaves the factory; anything short of spec is not racked.
- Fan wallA stopped fan raises a ticket on its own — you do not have to notice. Fitted and power-on tested within 4 hours of the spare arriving.
- Dual power modulesOne A feed and one B feed. Losing either does not stop the node. Minutes of power loss reported monthly at PDU level.
On-demand cloud, your own build, or us
Three ways to get compute
All three work. The dividing lines are term and headcount: a few days, take the first; a facilities team, take the second; otherwise talk to us.
Someone else's machine, rented by the second
Billed by the second, fastest to start, right for an experiment that runs a few days. The trade-off: the machine is not yours, popular configurations queue, and you do not control neighbours or oversubscription.
You carry all of it
Maximum control. The trade-off: rack contracts, power upgrades, cooling work, spares inventory and 7 × 24 staffing are all mandatory, and it usually takes 6 – 12 months before anything runs.
The compute is yours, the operations are ours
The machine can be an asset you bought or one you rent by the term. It runs in our racks, with uptime, swap response and credit percentages written into the contract. Racked 5 – 10 days from signature and hardware arrival.
Three ways to work with us
Buy · rent · host
Purchase
APEXBYTE SUPPLY
Compute on your balance sheet. 72 hours at full load before it ships, asset label and report in the box, serial numbers straight into your register.
Rental
APEXBYTE RENTALS
Billed by the GPU-hour. Get running first, decide on buying later. Shipped to your facility, or left in our racks.
Hosting
APEXBYTE CARE
Space, power, cooling, uplink, spares and 7 × 24 staffing — the whole layer. Hardware you already own is welcome if it meets three requirements.
| Purchase · Supply | Rental · Rentals | Hosting · Care | |
|---|---|---|---|
| Entry scale and price | From one complete machine, priced by configuration; the range narrows with volume | From 8 GPUs · 24 hours, from $0.95 / GPU-hour | From one rack, from $1,650 / rack · month, power metered separately |
| Minimum term | One-off, no term | 24 hours | 3 months |
| Who operates it | You. Inside warranty we swap parts; we do not come to site | You. During the term we replace the machine rather than repair it | Us. Power, cooling, network, part swaps, 7 × 24 staffing |
| Whose books it sits on | Your fixed asset; the 3-year warranty follows the serial number | Our asset. Normal wear is on us; loss or damage while at your site is insured by you | Ownership does not change — what you buy is the operations layer |
| How you exit | The asset is yours. We can assess and take it back at the prevailing market price | 14 days' written notice, 14-day return window | 30 days' written notice; we de-rack and pack, you pay the return freight |
| Credit cap | Part swap or depot repair; if the model is discontinued, refunded at residual value | Downtime deducted hourly from the rent, capped at the rent | Credited on monthly uptime, capped at that month's hosting fee for that rack |
| Who should not pick this | Teams with under 12 months of demand, or still undecided on a GPU generation — renting costs less | Teams running flat out beyond 9 months — by then the rent exceeds the purchase price; buy | Teams needing physical access at will, or whose data cannot leave their own facility |
The three routes mix: rent for a month to validate, then buy for the long run — usually without moving the hardware out of the rack. Whether the same units carry over depends on what is racked and their condition at the time, and the plan says so. Rent is a usage fee and does not offset a purchase price. Prices in the table are indicative ranges and are not an offer.
When to come to us, and when not to
Who this is for
✓ In these cases our route costs less
- The workload runs for more than three months and the on-demand bill no longer adds up
- You want compute on the balance sheet as an asset, not as a floating monthly cloud line
- Nobody on the team is willing or free to handle dropped GPUs, fans and PDUs at night
- Data has to stay inside the EU, or you need Europe and Asia-Pacific covered at once
- You already bought the machines and what you lack is space, power and on-call staffing
- You need an asset register and uptime report you can hand to finance and audit
✕ In these cases, do not come to us
- A few days of experiments — on-demand cloud is simpler; our rental minimum is 24 hours and hosting is 3 months
- Hands on the hardware whenever you like — site access needs 3 business days' notice and an engineer escorts you
- Data that must never leave your own facility — then buy the machines and keep them there; we only supply
- You want us to own the OS, drivers, CUDA and cluster scheduling — that is your boundary
- You want per-second elasticity — we deliver by the term and do not run a burst pool
- You want us to underwrite business losses from an interrupted training run — credits are capped at the period fee and exclude indirect loss
- The end user or end use would not pass export-control review — this is not something we help anyone route around
Setting the boundary before signing is much cheaper than setting it after something breaks.
From one sentence of demand to a monthly report, in four steps
Delivery · day 0 → monthly
01 · Day 0
Describe the workload, get a plan
You tell us what you need to run, for how long, and where. We come back with scale, configuration, unit price and a rack-ready date. Valid 7 days; scale is locked against that day's free capacity.
02 · Days 1 – 3
72 hours at full load
Temperature curves, memory ECC error counts, measured inter-GPU link bandwidth — each one logged. A machine that misses any of them is not racked and does not ship.
03 · Day 4
Racked here, or shipped to your site
In our racks: cabling, asset labels, unboxing and inspection photographed and archived. Shipped to you: install manual in the box, power on and go. The cross-border leg runs at the pace of customs and export licensing and is not counted in the lead time.
04 · Every month
One operations report
Uptime, minutes of power loss, intake temperature curve, ticket response times. Miss the contracted figure and the credit is automatic, deducted from the following month's invoice.
P-06 · Facility photo · 16:9 · SHOT PENDING
Step 03 · Day 4
You can see exactly what racking involved without being there.
Unboxing inspection photographed, cabling dressed, asset labels applied — unit by unit, with photos and serial numbers going into the delivery list.
Front of a rack mid-cabling. An engineer's hands and cable ties in frame, rack door open. Keep the lower-left third in shadow; the type goes there.
Signature → racked · last 12 deliveries
7.0 days average
"Racked in 5 – 10 days" — here are the last 12, drawn out.
Each bar is one completed delivery, counted from the day the contract was signed and the hardware arrived to the day the machine was running in the rack: 5 days at the fastest, 10 at the slowest, held up at customs. The dashed line is the scheduling limit we set ourselves; going over it is explained in the report. It is not a separate credit clause.
Basis: hosting deliveries into our own racks only; customs, export licensing and waiting on your facility are excluded. Past deliveries do not predict future scheduling.
Read how credits are writtenThe racks are in three places
Availability zones · AMS · FRA · SIN
We hold the rack contracts and set the on-call rota ourselves; nothing is subcontracted. Data staying in the EU goes to AMS or FRA, Asia-Pacific coverage goes to SIN, and one contract can be split across zones. The monthly uptime below is a measured 12-month average; the contracted figure is ≥ 99.9% throughout.
P-03 · Facility photo · 16:9 · SHOT PENDING
SHOT PENDING
Cold-aisle perspective, racks in a line, vanishing point about a third in from the right. Camera height around 1.4 m, square on or 45°.
Amsterdam · Netherlands
P-04 · Facility photo · 16:9 · SHOT PENDING
SHOT PENDING
Same camera logic as P-03, at FRA-01. The three sit side by side, so keep eye height, colour temperature and perspective identical.
Frankfurt · Germany
P-05 · Facility photo · 16:9 · SHOT PENDING
SHOT PENDING
Same camera logic as P-03, at SIN-01.
Singapore · Singapore
Every machine runs 72 hours at full load before it is racked
Burn-in · 72 h · serial-tracked
A machine short of spec does not enter a rack. Reports are archived against the serial number for 5 years and can be re-issued any time.
GPU temperature · 72 h at full load
71 °C peak
P-01 · Hardware detail · 4:3 · SHOT PENDING
SHOT PENDING
A node on the burn-in bench, 45° side light, chassis at an angle. Focus on the nameplate or rear ports; heatsink fins must show clear light-to-dark transition.
P-07 · Packing and dispatch · 4:3 · SHOT PENDING
SHOT PENDING
Light ground, flat light, shot from above. An open carton holding a machine in an anti-static bag, asset label and packing list on the lid.
One goes on every machine that leaves. Serial number, SKU and burn-in pass date are printed on it — the same number as the line in the delivery list and the archived report.
The seven questions we get asked
All termsWhat exactly do you provide, and how is it different from on-demand cloud GPUs?
What do you commit to, and what do you not?
Can we claim further after a credit? What is the cap?
How long from first conversation to running?
How are hosting outages credited?
Can you host hardware we already own?
What happens if a rented machine fails mid-term?
Request a quote
A plan within one business day: scale, configuration, unit price, rack-ready date.
Not "we have received your enquiry" — an email setting out how this compute is configured, which zone it sits in, what it costs and the day it can run.
No form. Email, phone, WhatsApp, Telegram and WeChat are on the page — pick one and reach a person. Six things are enough: what you run, the scale, buy or rent or host, the term, where it goes, and how to reach you. We size the configuration to the workload and the budget.
Get the contact detailsSee how hosting works first