Independent server testing

What will you run?

Benchmarks for VPS and cloud servers. Pick a workload and inspect the recorded measurements.

Compare VPS byin

Explore published provider reports

VultrDigitalOcean
Same workloads. Reviewable evidence.Read the methodology
The benchmark explorer

Matched plans.
Real measurements.

6 reports from DigitalOcean and Vultr.
Shared and dedicated CPU, matched plan sizes.

Published measurements
London, UK
PostgreSQL in-memory dataset · higher is betterBar: median of recorded repetitions · highest repetition
ProviderTransactions / secAvg latency
DigitalOceans-2vcpu-4gbShared CPU · 2 vCPU · 3.8 GiB
1,479
2.70 ms
Vultrvc2-2c-4gbShared CPU · 2 vCPU · 3.8 GiB
2,073
1.93 ms
DigitalOceanc2-2vcpu-4gbDedicated CPU · 2 vCPU · 3.8 GiB
1,612
2.48 ms
Vultrvoc-c-2c-4gb-50s-amdDedicated CPU · 2 vCPU · 3.8 GiB
4,171
0.96 ms
DigitalOceanc-4Dedicated CPU · 4 vCPU · 7.8 GiB
4,224
0.95 ms
Vultrvoc-c-4c-8gb-75s-amdDedicated CPU · 4 vCPU · 7.7 GiB
5,451
0.73 ms
2 reports selectedCompare selected
More
Newest London run per matched plan · observed RAM · original units.Individual observations, not provider rankings. No 24-hour consistency runs yet.
Behind the numbers

Every number.
Backed by a test.

Recorded hardware. Repeatable workloads.
Results you can inspect.

Read the methodology
Recorded configurationABCSeparate test recordsCPUMemoryDiskNetworkDatabaseStartRecorded test windowEnd
Published record
  • Report JSON
  • Test context
  • Private evidence
Sanitized report + context
01 /

Record the deployment

Keep provider, plan, region, observed hardware and agent version with the result.

02 /

Repeat the workload

Retain the recorded repetitions and their original units. Missing measurements do not become scores.

03 /

Publish the evidence

Connect each reviewed result to its test version, limitations and sanitized report.

A score is useful when you can explain it.Inspect a published test record

Methodology concept · process illustration, not measured chart data. Pilot results do not establish 24-hour consistency or physical-host independence.

From the journal

Choose with confidence.

Practical guides to the decisions behind your infrastructure.

Visit the journal
Web appsBackground jobsDatabasesAnalyticsShared CPUYour appDedicated CPUThe essentials · Practical guides

Infrastructure decisions.
Understand what you’re paying for.

Explore Linux, databases, networking, and the workloads behind your next server.

Read the journal

Explore the journal

Storage

Disk performance beyond headline speeds

Methodology

Read a benchmark with confidence

Networking

Choose a region for your workload

Explore by topicLinuxDatabasesNetworkingPerformance
A few more details

Before
you choose.

A little context for a better decision.

Does shape.host sell hosting?

Shape.host publishes server benchmark evidence and a technical journal to help readers inspect hosting infrastructure.

How do I compare different providers?

Inspect each deployment’s resources, architecture, region, workload settings and test date. Individual reports and their repeated measurements are not provider-wide rankings.

Can I inspect the test results?

Each published report includes the approved, sanitized JSON snapshot. Raw intake logs and private review evidence stay in administration.

Do pilot tests establish consistency?

A pilot measures its recorded test window. It does not establish 24-hour consistency or long-term reliability. Each report retains its review and limitations.

Find your next server.

Start with your workload. Compare the evidence.

Explore benchmarks