Self-Hosted Kubernetes Cluster
Container orchestration on your own infrastructure. Distribute applications across multiple servers, deploy updates without downtime, and let Kubernetes react automatically to failures. On dedicated hardware in Germany, billed hourly, without vendor lock-in.
3 Nodes, ein Cluster
When a single server is no longer enough
Updates without downtime
On a single server, every update causes a brief outage. In a cluster, new instances of your application start before the old ones are stopped. Your users notice nothing.
Automatic failover
If a server fails, Kubernetes detects it within seconds. Applications are automatically restarted on the remaining servers. No manual intervention, no maintenance window in the middle of the night.
Horizontal scaling
Instead of buying a bigger server when load increases, distribute workloads across multiple ones. Add more servers as needed and expand your cluster without interrupting existing applications.
Multiple applications, one infrastructure
Run production, staging, and internal tools on the same infrastructure, isolated from each other. Each application receives defined resource allocations. One cluster instead of many individual servers.
From the first installation
Encrypted communication
All communication between your cluster nodes is encrypted. No unprotected traffic, even when servers are connected via public networks.
Replicated storage
Persistent data is stored on multiple nodes. If a server fails, your databases and volumes remain available on the remaining nodes.
Built-in ingress controller
HTTPS certificates are issued automatically via Let's Encrypt. Incoming traffic is internally routed to the correct application.
Full Kubernetes API
Standard ecosystem tools: kubectl, Helm charts, YAML manifests. Combinable with GitOps, CI/CD pipelines, and everything that supports the Kubernetes API.
Infrastructure as Code
Your cluster state lives in YAML manifests and Helm charts. Reproducible, versionable, auditable. Deployments can be automated via Git repositories.
Dedicated resources
Each server in your cluster has dedicated CPU cores and RAM. No overselling, no shared hardware. You determine exactly which resources are available for your workloads.
The proven solution for your cluster
k3s 33,000+ GitHub Stars, CNCF-certified
Lightweight, certified Kubernetes distribution. A single binary, ~550 MB RAM overhead per node. Ships with Traefik as ingress controller, a built-in load balancer, and embedded etcd for a highly available control plane. Fully conformant with the Kubernetes API: everything that runs on Kubernetes runs on k3s.
Suited for: Production clusters, edge computing, IoT, CI/CD infrastructure.
Self-hosted cluster or managed Kubernetes?
Self-hosted cluster
Best choice for teams who prioritize full control and cost efficiency.
- No control plane fee, no egress costs, no load balancer surcharges
- Full control over configuration, updates, networking, and add-ons
- Data in Germany, GDPR-compliant, no vendor lock-in
- Hourly billing without minimum contract
- Cluster configuration as Infrastructure as Code
- Networking, storage, and updates are your responsibility
- Monitoring and alerting setup required
- Linux and Kubernetes knowledge required
Managed Kubernetes
Best choice for teams who prioritize minimal operational overhead.
- No operational overhead for control plane, automatic updates
- Integrated monitoring, logging, and alerting
- SLA for control plane availability
- Managed add-ons (ingress, DNS, cert-manager, load balancer)
- Fast provisioning without infrastructure setup
- Control plane fee on top of server costs
- Egress costs and load balancer fees
- Limited configuration options
- Vendor lock-in with proprietary integrations
A self-hosted cluster is worthwhile for teams with Kubernetes experience who prioritize cost control, data sovereignty, and full configuration freedom. Managed Kubernetes is the better choice for teams without dedicated platform engineering who need fast provisioning and minimal operational overhead.
How to start
Create servers
Create three servers with the right resources for your use case. Our guide includes concrete sizing recommendations. All servers in the same location for low latency.
Set up cluster
Our step-by-step guide walks you through the setup: encrypted networking between servers, Kubernetes installation, storage configuration. Every command is explained.
Deploy applications
Deploy your first application to the cluster. Rolling updates, automatic HTTPS certificates, and failover work from the first deployment.
Step-by-step setup
Detailed tutorials by our engineers, tested on a current dataforest Seed. Accessible without an account.
Configure a seed
Billed hourly, no minimum contract, no setup fee. You only pay for the servers that form your cluster.
Entry
Beginner
Standard
All-rounder
Performance
CPU-optimized
All prices incl. 19% VAT
Why dataforest Cloud?
Data sovereignty
Your data stays in Germany. All seeds run in certified data centers in Frankfurt. No data transfers to third countries, full GDPR compliance.
Deployed in seconds
Seeds are provisioned automatically. From configuration to a running server takes only seconds. No waiting, no tickets.
Hourly billing
You only pay for what you use. No minimum terms, no setup fees. Seeds can be created and deleted at any time.
Full control
Root access, public API and full transparency. You decide what runs on your seed. No vendor lock-in, no hidden restrictions.
Bevor Sie loslegen.
What is Kubernetes?
Do I need Kubernetes or is a single server enough?
What prerequisites do I need?
How many servers do I need?
What happens when a server fails?
Is a self-hosted cluster cheaper than managed Kubernetes?
Do I need to handle updates myself?
How do I back up my cluster?
How does this differ from the deployment platform?
What applications can I run on the cluster?
Any questions?
Then our experts are happy to help. You'll be surprised how fast we are.
