The 2026 Awards are comingnominations open soon · judges announced before they doExplore the categories →

The catalog · 2026

Thirteen categories, twelve of them under four pillars

Each category below is a definition, not a marketing label. Read the lede, what fits, and what does not — then nominate the work that matches.

The thirteenth is Rising Signal, which crosses the pillars. Every one of the thirteen carries the same two co-equal honors, and one non-competitive Sustained Thanks sits outside the competitive set — twenty-seven honors a year.

Learn

Work you go back to when something breaks — the doc you bookmarked, the postmortem that taught the room, the explainer that finally made the system make sense.

Documentation of the Year

/awards/categories/#documentation-of-the-year

For the reference material people keep open while they work — runbooks, architecture notes, how-tos, and docs sites that make a system operable.

What fits

  • A public runbook, ops guide, or architecture decision record anyone can reach
  • A docs site or handbook page that teams actually cite during incidents
  • Vendor-published docs that teach the platform without requiring a sales conversation

Not this

  • Internal wikis behind a login
  • Product marketing pages, feature lists, or “why us” collateral
  • Courseware sold as a product (see Learning Environment if it is a free practice lab)

One primary URL. If the work spans a docs tree, nominate the best entry point and mention the rest in “why.”

Public Postmortem of the Year

/awards/categories/#public-postmortem-of-the-year

For a single incident write-up, published where anyone can read it, that taught the rest of us something we did not have to learn the hard way ourselves.

What fits

  • A blameless public postmortem with timeline, impact, and lasting fixes
  • An outage narrative that names trade-offs and what changed afterward
  • A near-miss write-up that is as honest as a full SEV-1

Not this

  • Status-page updates with no analysis
  • Internal RCA documents that never left the company
  • Marketing “we take reliability seriously” posts with no technical substance

Companies are eligible for the write-up they gave away — never for the product that failed or the one they sell.

Explainer of the Year

/awards/categories/#explainer-of-the-year

For a single piece that made a hard production topic clear — one article, thread, diagram set, or deep dive that people send to teammates with “read this.”

What fits

  • A long-form explainer of a protocol, failure mode, or operational pattern
  • A visual or written walkthrough that demystifies a common pager mystery
  • A public FAQ or field guide that replaces tribal knowledge

Not this

  • Ongoing blogs or series (see Blog or Written Series)
  • Product tutorials that only exist to upsell a paid feature
  • AI-generated filler with no practitioner judgment

Judge the piece, not the author’s whole body of work. Serial teaching belongs under Teach.

Make

Things built and given away: open tools and learning environments that other teams can run, fork, or practice on without buying a seat.

Open Source Tool of the Year

/awards/categories/#open-source-tool-of-the-year

For software given away that helps people run production — operators install it, fork it, or wire it into their stack without buying a license to start.

What fits

  • A CLI, agent, controller, or library used in real ops workflows
  • An open-source observability, deploy, or reliability tool with a public repo
  • A significant open release from a company that still sells something else

Not this

  • Closed-source products with a “community edition” that is the sales funnel
  • Toys and demos that never left a conference booth
  • Repos-walled SaaS with an open client and no usable open core

Nominate the project URL (repo or docs). Commercial companies remain eligible when the nominated work itself is free to use.

Learning Environment of the Year

/awards/categories/#learning-environment-of-the-year

For places to practice — labs, sandboxes, game days, and interactive environments that teach production skills without requiring a paid seat to try.

What fits

  • A free public lab, katacoda-style scenario, or local practice stack
  • An open game-day kit or chaos exercise others can run
  • A browser or CLI training environment aimed at on-call skills

Not this

  • Bootcamps and paid courses (out of scope for year one)
  • Vendor certification tracks that exist to sell badges
  • Slide decks with no hands-on environment

If the environment is free to try and teaches production work, it belongs here even if a company also sells training.

Give

People and groups who spent time on others — communities that held the line, creators who kept publishing, mentors who made room.

Community of the Year

/awards/categories/#community-of-the-year

For a group that held space for practitioners — a Slack/Discord/forum, user group, or working community where people get real answers about running systems.

What fits

  • An active public or clearly joinable community focused on ops / SRE / platform work
  • A regional or remote meetup series with lasting artifacts (notes, recordings)
  • A volunteer-run channel that routinely unblocks strangers

Not this

  • Vendor customer-success Discords that exist to retain paid accounts
  • Communities with no public evidence of activity or membership path
  • One-off event hashtags with no ongoing home

Nominate the community’s public home URL. Moderators and organizers are the “authors” of the work.

Creator of the Year

/awards/categories/#creator-of-the-year

For a person whose public body of work this cycle kept showing up in other people’s toolkits — consistent, free, and aimed at people who run systems.

What fits

  • A practitioner with a public trail of posts, tools, or talks across the cycle
  • Someone whose free work is routinely cited in runbooks and postmortems
  • A creator employed at a vendor whose nominated work is still given away

Not this

  • Influencer accounts that only promote products
  • Corporate brand channels (nominate the human, or use Community / Newsletter)
  • Work that cannot be reached without a paid follow or gated membership

Point at a representative public URL (home page, index, or best entry). The honor is for the person, judged on public work.

Mentor of the Year

/awards/categories/#mentor-of-the-year

For someone who gave time — pairing, office hours, review, sponsorship — in a way that left a public trace others can still find.

What fits

  • Public office hours, mentoring programs, or office-hour recordings
  • A sustained pattern of helpful review, office-hour notes, or mentee-facing guides
  • Someone known for making room for newer on-call engineers in public forums

Not this

  • Paid 1:1 coaching products
  • Private mentoring with no public evidence
  • “Thought leadership” without time given to other people

This category is hard to evidence on purpose. Prefer nominations with a public URL plus a concrete “why” from someone who was helped.

Teach

Serial teaching in public: podcasts, newsletters, written series, and talks that keep explaining how production actually works.

Podcast of the Year

/awards/categories/#podcast-of-the-year

For a show that kept teaching production engineering out loud — interviews, deep dives, or narrative episodes practitioners actually finish.

What fits

  • A public podcast with a production / SRE / platform focus
  • A show that publishes show notes or transcripts someone can search later
  • A new or continuing series that earned trust across the cycle

Not this

  • Vendor product podcasts that are ads with guests
  • Private corporate internal shows
  • Ship It Weekly (publisher rule: Rising Signal only)

Ship It Weekly does not enter this category. It enters Rising Signal and is People’s Choice–only.

Newsletter of the Year

/awards/categories/#newsletter-of-the-year

For a recurring written signal — the inbox brief people forward to their team because it catches what matters in production engineering.

What fits

  • A free public newsletter or brief with an archive anyone can read
  • A curated ops / SRE / platform digest with durable links
  • A company-run newsletter that gives away the knowledge, not the product pitch

Not this

  • Product changelogs dressed as journalism
  • Paid-only digests with no public archive
  • One-off essays (see Explainer or Blog / Written Series)

On Call Brief is publisher-affiliated if entered: People’s Choice only, never Jury Award.

Blog or Written Series of the Year

/awards/categories/#blog-or-written-series-of-the-year

For ongoing writing — a blog, column, or series that kept publishing useful production engineering work across the cycle.

What fits

  • A personal or team blog with multiple substantive posts in the cycle
  • A numbered series that builds on itself (reliability, Kubernetes ops, etc.)
  • Engineering blogs that publish real operating experience, not launch posts

Not this

  • A single standout article (nominate Explainer instead)
  • SEO content farms and affiliate listicles
  • Release-note blogs with no practitioner insight

Nominate the series home or best index URL. Judges look for sustained quality, not one viral hit.

Conference Talk of the Year

/awards/categories/#conference-talk-of-the-year

For a talk that traveled — a conference or meetup session whose recording or materials still teach after the hallway track ended.

What fits

  • A publicly recorded conference or meetup talk on production engineering
  • A talk with slides or companion notes anyone can reach
  • A keynote or deep dive that changed how a team operates afterward

Not this

  • Sales keynotes and product demos
  • Talks with no public recording or materials
  • Internal all-hands presentations

Prefer a URL to the recording or canonical talk page. “You had to be there” is not enough.

Cross-pillar

One cross-pillar category for work launched in the last twelve months — any medium, same eligibility rules, same two honors.

Rising Signal

/awards/categories/#rising-signal

For work launched in the last twelve months — any medium — that already punches above its age. Cross-pillar on purpose.

What fits

  • A new podcast, tool, newsletter, docs site, community, or series that started this cycle
  • A relaunch that is materially new (not a rename of a decade-old brand)
  • Ship It Weekly (People’s Choice only; publisher-affiliated)

Not this

  • Long-running projects with a fresh coat of paint
  • Work that belongs cleanly in a pillar category and is not newly launched
  • Products that launched but are not given away

Ship It Weekly enters Rising Signal only. Publisher-affiliated entrants carry a visible marker and cannot receive the Jury Award.

Outside the competitive set

Sustained Thanks

A non-competitive, editor-selected honor for long-running work that kept helping people run production systems — often for years — without fitting neatly into a single annual category race. There is no nomination form for Sustained Thanks; the editors name it when results publish.

Scroll to Top