Infrastructure people, building infrastructure.
Why Racktrail exists
Most teams evaluating infrastructure get two bad options.
A hyperscaler
Enormous capability, a bill that grows faster than the business, and a dependency that gets harder to unwind every quarter you stay.
Doing it yourself
Better economics on paper, provided you can hire people who have run OpenStack or Ceph in production, and provided you wanted to be in the infrastructure business.
Dedicated open infrastructure
Operated by people who do this professionally, that you could take over or take elsewhere — mostly existed as a promise. Providers sold open source and delivered dependency.
We built Racktrail to be the third option properly, which mainly means being disciplined about the boring parts: staying upstream, documenting everything, and writing down how to leave.
What we believe
Open by default.
Upstream distributions, unmodified. If we need to change something, we contribute it back rather than keeping it.
No lock-in.
Standard APIs, portable automation, documented exit. Customers should stay because leaving would be a bad idea, not because it would be hard.
Honest pricing.
Fixed costs, egress quoted up front, no line items designed to be discovered later.
Engineers on the phone.
The person who answers should be able to fix it.
The team
Where we are
Hazesoft Private Limited
Part of HDL Group.
Europe · North America · Asia
Eleven locations, plus customer facilities. The full list is on the Private Cloud page.
Europe, North America and Asia
Tell us what needs to run.
Send us the workload, the constraints, and the region it has to live in. An engineer — not a sales rep — will tell you honestly whether we're the right fit.