01
Engineering foundations
Linux, networks, storage and protocols understood deeply enough to debug them under pressure.
Platform Engineering Academy
Build the systems. Become the engineer.
A structured route from Linux foundations to production platform engineering—through real systems, a serious homelab and feedback from people doing the work.
Apply for the founding cohort
€1,500.00/year ex VAT
Application-based · small cohort · no passive certificate collecting
Build first
Every stage produces working infrastructure.
Sovereignty first
Own the system, the data and the trade-offs.
Explain the why
Tools change. Engineering judgement compounds.
The problem
Tutorials teach commands. The job requires judgement.
You can finish another playlist and still have nothing to show except notes and a certificate.
Platform engineers are paid to connect systems, make trade-offs, recover from failure and explain decisions. That competence only appears when you build and operate the whole thing.
The programme
A complete path, not another pile of tutorials
The sequence matters: foundations before abstractions, operations before platform promises, evidence before job applications.
02
A production-grade homelab
Design, automate, secure and operate infrastructure you control. The result becomes evidence, not homework.
03
Infrastructure as code
Terraform, configuration management and CI/CD used as operating disciplines rather than résumé keywords.
04
Platform engineering
Containers, Kubernetes and internal-platform patterns—with equal attention to when they are the wrong answer.
05
Security and sovereignty
Identity, PKI, secrets and observability built in from the start, with a deliberate self-hosted and EU-first bias.
06
Career proof
Architecture decisions, incident write-ups, repositories and demos that give an interviewer something concrete to inspect.
Your portfolio repository
- ├── architecture/decision-records/
- ├── terraform/modules/
- ├── configuration/policies/
- ├── pipelines/verified-builds/
- ├── observability/dashboards/
- ├── security/threat-model.md
- └── runbooks/incident-recovery.md
The outcome
Build proof that hiring managers can inspect
Your homelab becomes a coherent engineering case study: architecture, automation, security controls, observability, failure recovery and the written decisions behind it.
Not a toy cluster. Not screenshots of a cloud console. A system you can demonstrate, defend and keep improving.
Three steps. A lot of real work.
01
Apply
Tell us where you are, where you want to go and what keeps blocking you.
02
Engineer
Follow the path, build the lab, join live sessions and get feedback when the system fights back.
03
Prove
Turn the result into a portfolio and practise explaining it like the engineer who designed it.
This fits if you…
- • want to understand systems instead of memorising tools;
- • are willing to build, break, document and rebuild;
- • want direct feedback and an active technical peer group;
- • care about security, ownership and engineering trade-offs.
This does not fit if you…
- • want a certificate without operating anything;
- • expect Kubernetes to be the answer before the question;
- • need a guaranteed result without consistent work;
- • prefer passive content over critique and iteration.
FAQ
Questions, answered plainly
Is this another video course?
No. The curriculum supports the work, but the product is the path, the projects, the feedback and the community. Watching is not progress; building is.
Do I need professional infrastructure experience?
No. You do need working Linux basics, curiosity and the willingness to troubleshoot. The path starts at foundations and gets serious quickly.
Do I need expensive homelab hardware?
No. Start with a used mini PC, an old laptop or virtual machines. Good engineering is visible in the decisions and automation, not the size of the rack.
Is everything based on a hyperscaler?
No. You will understand public cloud, but cloud is treated as an engineering choice—not a default. Self-hosted and EU-sovereign options are first-class.
How much time should I reserve?
Plan for consistent weekly work. This is designed around people with jobs and families, but there is no passive route through it.
Why is membership application-based?
A small, active cohort is more useful than a large silent library. The application checks whether the programme matches your goal and whether you can commit to doing the work.
Stop collecting tabs. Start building systems.
Ready to engineer your cloud?
Apply for the founding cohort. If the programme is not a fit for your goal or current level, we will say so.
€1,500.00/year ex VAT
Apply for the founding cohortCommunities