About Gravy
An independent engineering journal about shipping and operating software — served warm, twice a week.
A small publication, on purpose
Gravy started as a shared document between six engineers who were tired of two kinds of writing: the vendor blog post and the tweet thread. We wanted something in between — careful, useful, and occasionally funny.
We publish two or three pieces a week, plus a letter on Sundays. There are no sponsored posts inside the essays, and no AI-generated filler disguised as reporting. If we do not have something to say, we do not publish.
What we write about
- Containers and the kernel — how the machinery underneath actually behaves, including the surprising parts.
- Delivery and infrastructure as code — pipelines, state and the discipline of reversible change.
- Observability and incidents — what your telemetry can and cannot tell you at 3am.
We are less interested in being trendy than in being correct.
Who we are
A very small team of working engineers and editors across five cities, all of whom have carried a pager. You can find each of us on the author pages, along with everything we have published here.
How it is funded
Mostly by members and the Sunday letter, plus a handful of workshops each year. This means our incentives are boring in the way we like: keep readers happy, avoid publishing things that waste their time.
Get in touch
Corrections, disagreements and war stories are all welcome. Write to us at hello@gravy.local or use the contact page.