Hetzner and the Price-to-Performance Argument

Hetzner comes up in almost every conversation about getting more compute for a given budget. That reputation is specific rather than general, and understanding what it covers helps you judge whether it fits your workload.

What the reputation is based on

Hetzner operates its own data centres in Europe and sells compute with a narrow, well-defined product line. There is no large catalogue of managed databases, queues and analytics services to subsidise. The offering is servers, storage, networking and the tooling needed to run them.

A narrow product line is cheaper to operate, and that shows up in what a given monthly figure buys. It also means you assemble more of the stack yourself.

The trade-off stated plainly

If your architecture is application servers, a database you manage, and some object storage, the narrow catalogue costs you nothing. If your architecture assumes managed services handling queuing, identity, streaming and analytics, you will be rebuilding those yourself or connecting to them elsewhere.

Neither is a flaw. It is a question of which parts of the stack you want to own.

Counting servers

Catalogue configurations are expressed in server counts, which maps onto how many separate machines an environment holds. A handful of servers covers an application, a database and a staging environment. Larger counts describe estates with redundancy or several isolated projects.

How many machines you need before you need bigger ones is discussed in scaling vertically before horizontally.

European placement

Hetzner’s locations are predominantly European, which matters for latency to European users and for data-residency obligations. For an audience concentrated in North America or Asia, the physical distance is a real and unavoidable cost in round-trip time.

Outbound mail

Outbound port 25 is restricted by default and enabling it is an account-level decision. Configurations carrying that permission suit applications delivering mail directly rather than through a third-party relay.

Current catalogue options

After taking control

• Change the account password and enable two-factor authentication.
• Rotate API tokens and remove any you did not create.
• Review authorised SSH keys on every server.
• Check firewall rules, which were written for someone else’s application.
• Snapshot anything you intend to keep before changing it.

Hetzner’s terms of service continue to apply to the account and its use.