A self-hosted Kubernetes platform for Devantler Tech's business services and personal applications. This repository contains the configuration for that live platform, shared as a reference—not a ready-to-use distribution.
The goal is affordable production infrastructure: redundant cluster nodes, replicated storage, backups, monitoring, and reviewed deployments without a managed Kubernetes control-plane fee. You still own its operation and recovery.
Want to build a similar platform for yourself? Start with platform-template, the reusable template for creating your own instance.
Changes are reviewed in Git. Flux applies the published configuration to the cluster automatically. KSail manages the Talos clusters and the workload lifecycle.
- Compute: Talos Linux on Hetzner Cloud, with a smaller Docker-based local test environment.
- Networking: Cilium, Gateway API, Cloudflare DNS, and certificate management.
- Access and secrets: Dex single sign-on, OpenBao, External Secrets, and SOPS-encrypted bootstrap secrets.
- Storage: Longhorn volumes and CloudNativePG-managed PostgreSQL.
- Operations: Coroot observability, autoscaling, progressive delivery, and backup/recovery tooling.
- Applications: shared platform services and tenant apps deployed from their own repositories.
The local environment includes only core infrastructure by default; applications and heavier components are opt-in. See the architecture guide for the component inventory, environment differences, and how the layers fit together.
The configured six-node Hetzner baseline is approximately €87/month for compute and networking, excluding VAT at public prices checked on 11 October 2026. This includes three control-plane nodes, three workers, a load balancer, and IPv4 addresses—not just worker compute. As deployed, the platform also keeps one warm spare worker for fast scale-up, which brings it to about €103/month.
Storage, backups, domains, autoscaled capacity, and operator time are additional. See the cost breakdown for unit prices, a storage example, and the trade-offs behind the estimate. It is a starting budget, not an all-in bill or a managed-service equivalent.
- Explore the design: read the architecture guide, then browse shared components, provider overlays, and cluster definitions.
- Build your own platform: follow the template's bootstrap guide. To adapt this reference instance directly instead, see customization and local development. Its committed secrets cannot be decrypted with your keys; replace them with your own encrypted values.
- Host an application: follow tenant onboarding.
- Contribute a change: start with CONTRIBUTING.md. Most checks do not require a running cluster.
- Cluster access
- Developer platform and workflow self-service
- Secrets and rotation
- Storage and data retention
- Backups and disaster recovery
- Production recovery
More topic-specific guides and design decisions live in docs/.