How AnubizHost came to be
We started as a general-purpose technical shop, realized hosting was the part we were best at and cared about most, and spent the next five years building it into something specific and defensible. This is that story.
Timeline
Three phases, one continuous team
Founded as Anubiz Labs
The company started as Anubiz Labs, offering both managed hosting and DevOps consulting. The core team came from system administration backgrounds - people who had spent years running infrastructure for others and saw the gap firsthand. From day one, privacy was a design constraint, not an afterthought. Early clients were small businesses and individual developers who needed reliable servers without the compliance overhead of the big cloud providers.
Pivoted to hosting exclusively
After three years of running both hosting and project-based DevOps work, the team made a deliberate choice. The hosting side of the business was growing faster, the demand for offshore and privacy-respecting infrastructure was real and underserved, and splitting focus between project delivery and keeping hundreds of servers running was costing everyone. In 2023 we exited the consulting pipeline and went all-in on hosting - expanding the node footprint, building out the provisioning platform, and sharpening the product lineup around the use cases we understood best.
The hosting line becomes AnubizHost
By 2025 it was clear the hosting business had its own identity, its own audience, and its own market positioning. The hosting line was brought under its own brand - AnubizHost. Anubiz Labs did not disappear. It continues as the operations and DevOps arm, the part of the team that keeps the infrastructure running and builds the internal tooling. AnubizHost is the name clients see on invoices and the brand we put behind the product. The team is continuous across all three phases; only the label on the door changed.
Constants
What stayed the same across all three phases
Privacy as architecture
We never collected ID documents. We never stored payment credentials linked to identity. From the first server we rented, the posture was: collect only what provisioning requires, keep nothing you do not need.
Operators, not resellers
The team runs the infrastructure itself. When something breaks at 03:00, the person who picks up the ticket is the same person who knows where the disks are. That accountability is not scalable by design.
Offshore-first thinking
Every jurisdiction decision from 2020 onward was made with the same question: where can a client run a legal-but-controversial workload without a letter from a US lawyer forcing us to pull the plug? That question shaped the node selection map we have today.
No-frills provisioning
Clients do not need a sales call to get a server. They never did. The product was built to let a person pay in crypto, pick a plan, and have root access in minutes - no account manager in the loop.
Today
Where we operate now
AnubizHost operates from a Romania-primary offshore jurisdiction, with data centers in Romania (primary), Iceland, Ukraine, Netherlands, and Finland. Romania is the legal anchor - no mandatory data retention, no automatic DMCA enforcement, court orders required from Romanian courts before any disclosure. Iceland adds a second jurisdiction with strong free speech protections and Scandinavian latency.
The infrastructure is operated directly, not through a reseller chain. That means abuse decisions, uptime commitments, and hardware choices all live on our side of the wall. When something goes wrong, the fix is internal - not a support ticket filed with a third party who has no accountability to you.