Wombat: The New Voice of WAF++
The framework was open. The licenses were open. The name wasn't. On 28 October 2026, WAF++ became Wombat — and that is a bug fix, not a rebrand.
Read more →Writing from the people building Wombat — architecture, governance, and the occasional opinion.
The framework was open. The licenses were open. The name wasn't. On 28 October 2026, WAF++ became Wombat — and that is a bug fix, not a rebrand.
Read more →
Sovereignty begins with visibility — not with migration. Those who flee the cloud without knowing what they have simply trade one dependency for mo...
Read more →
There is a specific kind of frustration that every seasoned cloud architect knows. You sit in a room, reviewing an infrastructure design. The work ...
Read more →
Great ideas rarely happen when you plan them — most of the time they emerge somewhere between a dead battery, an overheating laptop, and a drink yo...
Read more →
Cloud architectures are under enormous pressure today: rising regulatory requirements, growing demand for multi-cloud flexibility, and the desire t...
Read more →The Wombat blog is community-written and open source. If you work in cloud architecture, platform engineering, or governance — your experience belongs here.
Deep dives into Wombat pillars, cloud sovereignty, multi-cloud patterns, or framework comparisons — grounded in real engineering decisions.
Applied Wombat in a real project? Ran an assessment? Encountered a gap in existing frameworks? Write it up — the community learns from concrete examples.
Posts live in the GitHub repo as Markdown. Draft in a branch, open a PR — the editorial process is fully transparent and community-reviewed.
Follow the blog, the changelog, or the RFC tracker. Wombat is built in public and every update is shared with the community.