HETZNER // CLOUD AND METAL KUBERNETES-NATIVE FOUNDATION

Kubernetes on Hetzner Cloud

Cloud and Metal instances on Hetzner, with Kubernetes built in.

Edka provisions a production ready Kubernetes platform in your own Hetzner account: apps, databases, private networking, automations, AI agent runtimes, and dedicated Metal servers for sustained capacity.

Cloud and Metal
your Hetzner account
Apps + data + agents
one controlled platform
Kubernetes native
portable foundation
What Edka gives you on Hetzner
  • Kubernetes cluster in your own Hetzner account
  • Hetzner Metal server pools over vSwitch
  • Apps, deployments, and GitOps workflows
  • PostgreSQL, MySQL, Valkey, ClickHouse, and backups
  • Private networking with Tailscale, Cloudflare, Gateway API, and TLS
  • Hermes and OpenClaw agent runtimes
  • Logs, metrics, diagnostics, and operational support

SUPPORTED PROVIDER // HETZNER TODAY

Hetzner is Edka's supported foundation for controlled Cloud and Metal infrastructure today.

Use Hetzner to run infrastructure you control: Cloud instances for speed, Metal instances for sustained capacity. Edka manages the Kubernetes foundation, add-ons, deployments, databases, observability, and runtime operations while the infrastructure stays in your account.

WHY TEAMS CHOOSE IT 3 CORE BENEFITS

Hetzner-hosted ownership

Run the cloud foundation in your own Hetzner account, then attach Hetzner Robot dedicated servers as Metal servers when sustained workloads need owned capacity.

Cloud and Metal instances

Start with Hetzner Cloud instances for speed, then add dedicated Metal servers for long-running agents, automations, and data-heavy workloads.

Kubernetes native portability

Keep kubectl access, GitOps workflows, open components, and a practical detach path if your infrastructure needs change.

HETZNER // WORKLOAD PATH CLUSTER → PLATFORM → WORKLOADS

1. Provision the foundation

Start a Hetzner Kubernetes cluster from the Edka console and keep the cloud foundation in your own account from day one.

2. Enable platform capabilities

Add private networking, TLS, databases, observability, storage, registry, and optional Hetzner Metal server pools with sane defaults.

3. Run apps, data, automations, and agents

Deploy applications, databases, workflow services, and agent runtimes with GitOps, logs, metrics, backups, and rollback paths.

FAQ // SEARCH INTENT 7 ANSWERS

What is Edka for Hetzner Kubernetes?

Edka helps teams run Kubernetes based infrastructure on Hetzner with Cloud and Metal instances in their own account. It provisions clusters, can attach dedicated Metal servers, and adds workflows for apps, databases, deployments, add-ons, TLS, observability, automations, and private agent runtimes.

Is Edka only for Kubernetes on Hetzner?

Hetzner is Edka's supported provider today, and Kubernetes is the portable foundation. The product experience is broader: apps, data services, automations, and private AI agent runtimes running on infrastructure you control.

Can I run Kubernetes in my own Hetzner account?

Yes. Edka creates and manages the Kubernetes environment inside your own Hetzner Cloud account, so you keep ownership of the underlying infrastructure and direct Hetzner billing.

Can I attach Hetzner dedicated servers to an Edka cluster?

Yes. Edka supports Hetzner Metal server pools: your own Robot dedicated servers join the cloud control plane over a vSwitch, giving sustained capacity for agents, automations, and data workloads.

Can I run AI agents on Hetzner with Edka?

Yes. Edka supports private agent runtimes such as Hermes and OpenClaw, including profiles, webhooks, logs, health, and state backups in your own cluster.

How quickly can I provision Kubernetes on Hetzner?

Edka is designed to provision production ready Hetzner Kubernetes clusters in about 2 minutes, including the core infrastructure and platform defaults needed to start deploying workloads.

What does Edka automate on top of Kubernetes and Hetzner?

Edka automates cluster bootstrap, networking, TLS, GitOps-friendly deployment flows, add-on installation, databases, observability, and Hetzner-specific infrastructure defaults such as load balancers and storage integration.