About BuyVPS

Built by Operators

We have been building hosting infrastructure since 2002 and 2006.

Over the last 20 years we have done many projects, hosted VPS networks in many locations, dealt with countless hardware replacements and maintenance, negotiated with many upstreams and tried out many different hosting models in order to figure out what works and what does not.

BuyVPS is not an experiment.
It is the result of that experience.

We built this company for one reason: to build the VPS infrastructure we'd like to buy ourselves.

Defined limits Documented measurements Disciplined capacity planning
BuyVPS team
Our story

Why we built BuyVPS

After years inside the hosting industry, certain patterns became obvious.

  • Nodes filled to theoretical capacity.
  • Benchmarks shown without configuration context.
  • Density optimised for margin, not stability.
  • Pricing structured around introductory discounts.

None of those decisions are accidental. They are business models.

We chose a different one.

We are focusing on predictable resource assignment, controlled node packing density and real world performance – as opposed to theoretical benchmarks and artificial performance governors.

The goal is not maximum utilisation.
The goal is infrastructure that behaves consistently over time.

How we operate

Our operating model

We operate under a low-density node policy.

  • Usable memory per node is capped.
  • We do not allocate to theoretical maximum.
  • Capacity buffers are deliberate, not incidental.

Benchmark results are published as median and p95 values from multiple runs.
Test configurations are documented.
Public links are provided where applicable.

Numbers without context are marketing.
Numbers with methodology are information.

Every architectural decision follows a strategic principle:

Consistency scales. Instability compounds.

Infrastructure

Architecture standards

All our VPSes run on KVM technology and a separate kernel. Resources such as RAM, CPU and disk space are allocated per VPS in predefined quantities.

Storage is based on locally attached NVMe arrays with I/O patterns being monitored and verified under repeatable workload conditions.

We're running the exact same virtualization stack, the same control plane and operational policy in Amsterdam and New York. We will follow the same pattern as we expand into other regions.

Infrastructure should not behave differently because marketing changed.

Target segment

Strategic positioning

We are not structured as a volume-driven provider.

BuyVPS is designed for:

SaaS platforms
Agencies managing client environments
High-concurrency APIs
Production databases

Every team wants to plan their capacity, track latency percentiles, and predict the future. So they need a fairly predictable platform.

That is the segment we serve.

Leadership

Founders

Robert Bolder, BuyVPS founder and infrastructure lead

Robert Bolder

Founder, Infrastructure & Strategy

I am a 17 year veteran in the infrastructure & hosting industry. Founder of Hosted.nl, Global Cloud Infrastructure provider with 15+ locations around the world and Hostingway.

Robert works on architecture design, infrastructure validation and long-term platform strategy. His experience spans multi-region VPS deployments and operational scaling.

Sjoerd Klein Meulekamp, BuyVPS co-founder and operations lead

Sjoerd Klein Meulekamp

Founder, Operations & Infrastructure

Web hosting and infrastructure services provider since 2002. We have managed hosting services, including when I was COO of Hostingway and before that CIO of Managed Hosting Services.

Sjoerd is involved in the development of automation frameworks, capacity governance, maintenance planning and standard operating procedures on all kinds of environments.

Structure

The team behind BuyVPS

BuyVPS operates with a structured technical organisation.

Infrastructure Engineering

Hypervisor deployment, storage layout, RAID configuration, kernel tuning, capacity validation.

Network & Routing

Upstream coordination, ASN management, routing optimisation, latency monitoring.

Automation & Platform Engineering

Provisioning systems, API lifecycle management, monitoring architecture.

Security & Policy

Isolation standards, access control, incident processes, abuse governance.

Operations & Capacity Planning

Node density enforcement, hardware lifecycle management, vendor coordination.

Reliable infrastructure is built through process discipline, not improvisation.

Values

Our philosophy

Infrastructure should be:

  • Predictable
  • Transparent
  • Measurable
  • Sustainable

Growth must be deliberate.

Capacity must be justified.

Performance must be documented.

Stability

Long-term commitment

BuyVPS is financially independent and built for continuity.

In Amsterdam and New York we work under the same conditions and with the same rules. Our expansion is based solely on architectural principles and not on the marketing of the time.

We are not optimising for short-term volume.

We are building infrastructure that behaves as designed.

Our promise

Final statement

BuyVPS is not defined by slogans.

It is defined by:

Defined allocation boundaries.
Published methodology.
Controlled density.
Transparent pricing.

Infrastructure should not surprise you.

It should behave as expected.

View plans
Get in touch

Talk to us

Questions about our infrastructure, benchmarks or approach? We are happy to explain.

About BuyVPS

About us FAQ

Common questions about BuyVPS, our founders, infrastructure approach and long-term commitment.