
OpenStack Support: In-House vs. Managed Services
Compare in-house OpenStack operations, expert support, and managed services. Learn who should handle upgrades, incidents, and ongoing cloud operations.
Read field noteField notes / Latest
Engineering notes from operating open infrastructure: the failures, design decisions, and upstream work that make open infrastructure better.
Browse all field notes
Compare in-house OpenStack operations, expert support, and managed services. Learn who should handle upgrades, incidents, and ongoing cloud operations.
Read field note
Air gapped cloud on OpenStack: how Atmosphere's digest-pinned release manifests move a release across the boundary, and what the manifest leaves out.
Read field note
Learn when your team needs OpenStack consulting services and how expert support can help with deployments, migrations, upgrades, and operations.
Read field noteTrends, best practices, and technical deep dives on open source cloud infrastructure.

Hardware cycles are accelerating, regulations are multiplying, and costs are rising. A framework for AI infrastructure decisions that last through 2031.

Learn how mTLS, workload identity, and fine-grained authorization enforce Zero Trust in Kubernetes, a practical guide using Istio, Cilium, and the Navos stack.
OpenStack security is a set of decisions distributed across Keystone, Neutron, Nova, and Barbican. What to change, why it matters, and what breaks if you skip it.
Managed Kubernetes looks affordable — until you add monitoring, security, egress, and labour. Learn what TCO really looks like vs. the sticker price.
88% of CFOs say cloud costs are rising. The board wants answers. Learn how to present a plan built on infrastructure control, not just cost optimization.
OpenStack isn't the right answer for every team or workload, and knowing when it isn't matters as much as knowing when it is. An honest guide to fit, from a team that's been operating it since 2011.
Most organizations waste 95% of their GPU spend without knowing it. Run this five minute audit to find the leaks and fix them before the next invoice.
The fix to platform team understaffing isn't hiring more — it's building on infrastructure where monitoring, security, and upgrades come built in.
Upstream contribution costs real engineering time. It also compounds over time in ways that internal fixes never do. What fifteen years of contributing to OpenStack, Kubernetes, and Ceph actually looks like.
A technical deep-dive into how Navos manages zero-downtime Kubernetes cluster upgrades — the sequencing, primitives, and operational process behind every upgrade.