Kinsta and Hetzner are not competing for the same operator. Kinsta keeps WordPress infrastructure inside its managed platform -- isolated containers on GCP C2, no root access, no OS surface. Hetzner provides raw EU compute at high density, where every configuration decision is the operator's to own.

What you get that Hetzner doesn't offer

Container isolation per WordPress site -- dedicated PHP, database, and filesystem with no resource contention. GCP C2 as the infrastructure baseline with no configuration required to reach it. Automated backups, CDN, Cloudflare integration, and staging built into the platform. WordPress-specialist support throughout. Kinsta deliberately removes server-level developer control: no root access, no OS configuration, no custom stack.

What you give up

Hetzner's compute density per euro -- equivalent CPU and RAM cost measurably less. ISO 27001 certification with data centers in Germany and Finland. Full root access and unrestricted server configuration. Dedicated server options and a scalability path to bare metal. Kinsta is WordPress and WooCommerce only -- switching away requires a full migration.

What you get that Kinsta doesn't offer

Full root access and unrestricted server and OS configuration. More CPU, RAM, and storage per euro for EU-based deployments. ISO 27001 certification with data centers exclusively in Germany and Finland. Dedicated server options alongside cloud VPS under the same account. Any stack, any application, any workload -- no platform boundary.

What you give up

Kinsta's container isolation per WordPress site -- dedicated resources with no neighbor contention. GCP C2 infrastructure without configuration. Automated backups, CDN, staging, and WordPress-specialist support. Hetzner's interface assumes Linux administration familiarity -- there is no guided WordPress operations layer.