Co-founder · CEO
Founder name
Plans which racks we lease next and signs every reserved deal.
- Based
- EU-AMS-1
- Owns
- Capacity, contracts
About Nexpod
GIGABYTE G894-ZD3-AAX7
8 x NVIDIA B300 SXM · 8U
NVIDIA DGX H200
8 x NVIDIA H200 · 8U
ASUS ESC N8A-E12
8 x NVIDIA H100 · 7U
Servers
3 × 8 GPU
Inlet
22 °C
Fabric
400G
Mission
Most clouds sell a slice of a GPU and a bill you need a spreadsheet to read. We went the other way.
Every Nexpod server is a full 8-GPU machine that belongs to one customer for as long as it runs. No slices, no neighbours.
We rack the hardware ourselves, meter it by the second and invoice from the EU. Nothing clever on top, just the basics done with care.
What we hold to
No GPU slices, no shared hosts. A node is eight GPUs and one tenant.
Billing starts when the server boots and stops when it does. To the second.
EU entity, EU invoice, reverse-charge VAT. No exchange-rate surprises.
Incidents go on the status page while they happen. Postmortems go up in full.
Pick a region. Data, backups and support access stay inside it.
Since 2024
Sample datesWe grew one rack at a time, and only into places where we run the hardware ourselves.
Three engineers, one rented cage and a plan to rent GPU servers whole, never in slices.
The first H100 and H200 servers, billed per second from day one.
Autoscaling GPU endpoints for inference, with workers that scale to zero.
A second EU region for redundancy and a first US region for east-coast teams.
Multi-node clusters of 8-GPU servers on one 400G fabric, ready in minutes.
NVIDIA DGX B300 and GIGABYTE B300 servers join the fleet, next to B200.
A fourth region in Helsinki, with free-air cooling for most of the year.
Careers
If you like hardware you can touch and software that has to be right, we should talk.
How we work
Support is not a separate floor. The people who write the scheduler read the tickets about it, so the fix and the reply usually come from the same person.
Every change bigger than a day starts as a short doc that anyone can comment on. Decisions live next to the reasoning, so nobody has to ask twice why a thing is the way it is.
A team owns a problem from the rack to the invoice line. Fewer handoffs means fewer gaps, and the person on call understands the system they are paged for.
Boot times, queue depth, failure rates per GPU family. We put the number on the table before the opinion, and we change our mind when the number says so.
Label the cable, update the runbook, delete the dead flag. Small acts of care compound across every 8-GPU node we run, and so does the lack of them.
Amsterdam
CET
Frankfurt
CET
Helsinki
EET
New York
ET
Remote and hybrid
Most of us work near a data center: Amsterdam, Frankfurt or New York. Everyone else works remotely from Europe. Two shared core hours keep the time zones honest.
Team
PlaceholderCo-founder · CEO
Founder name
Plans which racks we lease next and signs every reserved deal.
Co-founder · CTO
Founder name
Owns the placement engine, the 400G fabric and the on-call rota.
Roster · 8 people
Start here
Pick a GPU family and a region. Your server boots in about a minute, and the meter stops the second you stop it.