Polycrate: Automated Infrastructure in Modular Packages
Automation must become manageable again. At ayedo, we are building a framework with Polycrate that …

Digital sovereignty is not a feature – it is an architectural principle. After transitioning our toolchain to open source, the next step was to strategically rethink the infrastructure behind the tools.
In this post, we showcase how our modern IT architecture looks – container-based, automated, scalable, and fully under our control.
Many companies replace individual tools but remain structurally dependent:
Our goal was clear: To create a foundation that offers us maximum control, flexibility, and future-proofing.
We rely on a modular infrastructure that aligns with DevOps principles – built on open standards and fully documentable.
| Area | Solution / Technology | Why We Use It |
|---|---|---|
| Orchestration & Containerization | Kubernetes | Standardized, scalable, Cloud-native ready |
| Hosting | Bare Metal & Kubernetes | Full control, no vendor lock-in |
| Configuration Management | Ansible | Automated provisioning and updates |
| CI/CD | GitLab CI | GitOps-compatible, self-hosted |
| Monitoring & Logging | VictoriaMetrics, Grafana, VictoriaLogs | High performance, metric-driven alerting |
| Storage & Backup | Velero, Restic, MinIO | Kubernetes-native, S3-compatible, automated |
| Secrets Management | Vault, Infisical | API-driven, Zero Trust ready |
| Authentication | Keycloak, Authentic | Central identity, OpenID Connect, multi-factor possible |
All changes to the infrastructure are versioned – no manual clicking around, no opacity. This brings:
Not everything has to go live automatically immediately. We rely on staged pipelines with manual gates for security-critical deployments.
And above all: We have regained oversight – and control.
Of course, not everything went smoothly. A few learnings from the transformation:
| Challenge | Solution |
|---|---|
| Resource consumption of Kubernetes | Fine-tuning of nodes and workloads |
| Complexity in monitoring | Standardized dashboards & alert rules |
| Storage redundancy | MinIO + automated backup with Velero |
| Internal skill gaps | Training & pairing in DevOps teams |
In part 4 of our blog series, we will show:
Our infrastructure is no secret – it is an invitation to dialogue. For those on similar paths or looking to start: Let’s talk.
What architectural decisions have you made?
What works for you – and what doesn’t?
We look forward to the exchange.
Automation must become manageable again. At ayedo, we are building a framework with Polycrate that …
Digital sovereignty doesn’t end with tool selection or architecture. It only reaches its full …
Kubernetes Make or Buy – Considerations for Decision Makers In few other technology sectors is …