Skip to main content
Customer story daily.dev delivers 12.8× more signups than Reddit. Read now →

How to advertise to SRE and platform engineers

To advertise to SRE and platform engineers, be where they read every day: daily.dev Ads, SRE Weekly, KubeCon and r/sre. daily.dev gives you a verified company page they follow and puts your posts and releases in the feed of developers who read #platform-engineering and #sre, and in the DevOps and Cloud newsletter, in one plan we run for you.

Explore my options→ See how plans work

Who are the SRE and platform engineers on daily.dev?

What they read, where it comes from, and what else they follow: the signals a campaign is targeted on.

The tags that reach them

Target any mix; your plan runs the campaign on them.

  • #platform-engineering
  • #sre
  • #kubernetes
  • #observability
  • #infrastructure
  • #cicd

800+ targetable keywords in all (daily.dev Media Kit 2.0, August 2026 — targeting).

Where SRE and platform engineers get their news

The sources that publish most on these tags, ranked by followers on daily.dev.

  1. 1 Cloud Native Now
  2. 2 The New Stack
  3. 3 Awesome Go
  4. 4 CNCF
  5. 5 Fireship
  6. 6 freeCodeCamp

What they also read

Tags on the same recent posts, as a share of them. Worth adding to a campaign.

  • #ai-agents19%
  • #devops19%
  • #open-source4%
  • #opentelemetry4%
  • #mcp3%
  • #security3%

Tags, sources and co-reading: daily.dev public API snapshot.

How do you reach SRE and platform engineers?

Developers are the audience that taught the industry to block ads. The way in is not a louder interruption; it is the reading they chose, in the place they open every day. That is why daily.dev Ads exists: to help brands earn a place in that reading, week after week.

13K+
companies whose developers read daily.dev
800+
targetable stacks and topics
2,000+
content sources in the feed

Written by the daily.dev Ads team, which plans and runs every campaign on the platform. Sources on the audience overview.

  1. They run a proof of concept before they believe anything.

    Publish the Helm chart, the operator or the Terraform module with each release post, and say what it takes to remove it again. That turns the post into an invitation to try it in staging.

  2. Reliability claims need an SLO behind them.

    This audience thinks in error budgets and percentiles. State the availability target you meet and how it is measured, in the post, and it reads as engineering rather than marketing.

  3. Show the developer experience, not the control plane.

    Platform teams are judged by whether product engineers use what they ship. Publish the golden path from the product developer’s side: the template they clone and the deploy they get.

  4. Openness is a feature to this audience.

    SRE and platform teams distrust lock-in and look for OpenTelemetry, the Kubernetes API and Terraform providers. Write plainly about what is open, what is portable and what the exit looks like.

Postmark
“It wasn’t just ‘here’s your campaign, good luck.’ The team brought creative guidance, audience intel, and suggestions around targeting and budget shifts.”

Trevor Rawls

Senior Marketing Manager

Read the case study →

Why do developers pay attention on daily.dev?

Harry on earning developer attention: lead with what your product does, respect a skeptical audience, cut time to value, and show up in the right context instead of interrupting.

More from the team: the developer marketing series →

What do SRE and platform engineers read, and what should your brand say?

A few things they read and discuss

Examples of popular posts on these tags that SRE and platform engineers read and talk about on daily.dev. Open any of them to join the conversation.

  1. Observability on Kubernetes: OpenTelemetry, Camel & Quarkus Piotr Minkowski TechBlog 1 5
  2. Retirement of Kubernetes integration jobs for unsupported Kubernetes versions Istio 1 4
  3. We built the platform. Nobody used it LeadDev 1 0

Each post opens on daily.dev with its discussion.

What that means for your message

Your takeaways from what they discuss. Our team writes the creative with you.

  • Toil reduction Publish the manual task your product removes and how often it recurred before
  • Incident response Share a real incident write-up with the minutes from alert to root cause
  • Golden paths Show the template a product team gets, not the platform diagram

How do you target SRE and platform engineers on daily.dev?

Targeting is built on what developers read on daily.dev, not a self-declared profile. You set it once with your campaign manager; your plan runs it, and we optimise it every week.

Tags
#platform-engineering, #sre, #kubernetes, #observability, #infrastructure, #cicd, and any of the 800+ targetable keywords
Seniority
Junior, mid-level, senior and leadership, from on-platform activity
Region
Global, or by region and country
In your plan
  • Your verified company page
  • Your posts in their feed
  • The DevOps and Cloud newsletter
  • Your logo on the daily.dev homepage
  • A weekly report and a campaign manager
Creative

Our team works with you to shape, finish and test your creative, so it reads like the posts around it.

Creative specs for every placement

Pick a size

Same work in every size. The size sets your reach.

Plan size
Explore my options →

Prices are quoted per company. See how plans work →

Where else can you reach SRE and platform engineers?

Where SRE and platform engineers can be reached with paid media, and what each channel is good at. Most teams combine two or three; a plan here is the always-on part.

Compare daily.dev with

daily.dev Ads
SRE and DevOps newsletters SRE Weekly, DevOps Weekly
Format
Your verified company page, your posts in their feed, the newsletter they chose, the homepage One sponsor slot per issue
Target by stack
Yes: #platform-engineering, #sre, #kubernetes, #observability, seniority, region By list
How you buy
Managed monthly plan Per issue
Best for
Building a brand developers follow, every week, with creative and reporting done for you Launch-week spikes

Channel facts from each channel's own public pages, October 2026. Prices are not compared.

What do teams build with SRE and platform engineers on daily.dev?

Build your brand with them

Show up every day in the reading SRE and platform engineers chose, with your posts, releases and point of view, so yours is the name they know when they pick a tool.

Grow a community around your product

Your verified company page is where SRE and platform engineers follow you, discuss your posts and come back for your next release.

Strengthen your employer brand

Share engineering stories, culture and open roles with SRE and platform engineers where they already discover tools and ideas.

Brands building with developers on daily.dev

Brands building with developers on daily.dev

Google
Okta
AWS
Vanta
RevenueCat
JetBrains
ClickHouse
Neo4j
Appwrite
Pulumi
OpenRouter
Postmark
Google
Okta
AWS
Vanta
RevenueCat
JetBrains
ClickHouse
Neo4j
Appwrite
Pulumi
OpenRouter
Postmark
Atlassian
Sentry
Google Cloud
Zoho
QA Wolf
Postman
PostHog
Temporal
dbt Labs
CodeRabbit
Bright Data
Novu
Atlassian
Sentry
Google Cloud
Zoho
QA Wolf
Postman
PostHog
Temporal
dbt Labs
CodeRabbit
Bright Data
Novu
Notion
Datadog
Cursor
Edge Impulse
TigerData
Snyk
LaunchDarkly
Sonar
Retool
Windsurf
Stream
context.dev
Notion
Datadog
Cursor
Edge Impulse
TigerData
Snyk
LaunchDarkly
Sonar
Retool
Windsurf
Stream
context.dev

Google, AWS, Google Cloud, Cursor, Vanta, Zoho, Atlassian, Notion, Okta, Sentry, Datadog, JetBrains, Postman, Snyk, ClickHouse, Edge Impulse, RevenueCat, QA Wolf, TigerData, PostHog, LaunchDarkly, Neo4j, Temporal, Sonar, Appwrite, dbt Labs, Retool, Pulumi, CodeRabbit, Windsurf, OpenRouter, Bright Data, Stream, Postmark, Novu, context.dev

Postmark drove 12.8× more signups context.dev hit 3× the industry CTR benchmark

Guides on reaching SRE and platform engineers

All guides: developer marketing resources →

Advertising to SRE and platform engineers: your questions

daily.dev reaches millions of developers, and SRE and platform engineers there read about Kubernetes, observability and incident write-ups. We do not publish audience sizes per segment; tell us the regions and seniority you need and your plan proposal comes back with the reach it buys. 75% of active developers across the network are mid-level or senior.

Yes. Your posts can reach only developers who read #sre or #platform-engineering, or those tags with #kubernetes, #observability and #cicd, with seniority and region on top. It is built on what developers read, not a self-declared job title.

Your verified company page comes first, with postmortems, release notes and the reliability write-ups this audience follows. Your plan puts them in the feed of developers who read #sre, #platform-engineering and #kubernetes and in the DevOps and Cloud newsletter. An incident guide is a strong post to lead with.

Yes. Every plan includes a verified company page that developers follow. What you publish there (releases, tutorials, engineering posts) reaches your followers, and your plan puts it in the feed of SRE and platform engineers who read #platform-engineering, #sre, #kubernetes. The following stays yours between campaigns.

Yes. Engineering stories, culture and open-source work published on your company page reach SRE and platform engineers where they already read, which is what makes an employer brand stick. To hire them directly, recruiter.daily.dev matches roles to developers who opt in.

daily.dev Ads is one managed monthly plan in three sizes, Starter, Growth and Scale. Every size includes your verified company page, your posts and releases in their feed and newsletter, creative made with you and a weekly report; the size sets the reach. Prices are quoted per company, so tell us the audience and regions you need and we come back with a size and a quote.

Pick a plan. We reach
SRE and platform engineers for you.

Tell us what you sell and the regions you need. We come back with a plan size, the reach it buys and a quote.

Explore my options → See how plans work

Other audiences: DevOps engineers Cloud engineers Backend developers All audiences →