How to advertise to security engineers

To advertise to security engineers, be where they read every day: daily.dev Ads, tl;dr sec, r/netsec and BSides. daily.dev gives you a verified company page they follow and puts your advisories, posts and releases in the feed of developers who read #security, #appsec and #devsecops, plus the Security and AppSec newsletter, in one plan we run for you.

Explore my options→ See how plans work

Security engineers #security #appsec #devsecops

You Join Squad

Your company

Where security engineers follow your releases, posts and launches.

Your latest release, explained

How we built it

In their feed Native posts on #security, #appsec, #devsecops

In their inbox A spot in Security and AppSec

On the homepage Your logo where they start the day

Every week A report and a campaign manager

One plan, built around your company page: we put it in front of security engineers across daily.dev and report on it every week.

Who are the security 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.

#security
#appsec
#devsecops
#authentication
#cryptography
#devops

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

Where security engineers get their news

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

1 freeCodeCamp
2 bigboxSWE
3 Lobsters
4 Spring
5 InfoQ
6 Node.js

What they also read

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

#ai-agents13%
#quantum-computing10%
#observability7%
#cicd5%
#kubernetes4%
#ai-coding3%

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

How do you reach security 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.

Name the class of vulnerability.

Security readers follow the companies that publish named CVE classes, supply-chain patterns and auth mistakes they have seen. "Protect your apps" gives them nothing to follow.
Write for the buyer and the user separately.

AppSec tools are bought by security teams and adopted by every developer who ships code. Publish research for the first and fix-it guides for the second, from the same company page.
Prove it with the fix, not the fear.

Show the ten lines the tool catches and the time it saves. This audience has learned to distrust fear-based marketing; research they can verify is what earns a follow.
Publish the references they will keep.

A hardening guide or an audit checklist becomes something security teams return to and share. Publish one, and keep it in their feed well after release week.

context.dev

“It wasn’t that it blew up. It was that a certain baseline level of quality was maintained. It feels super reliable as a channel, and it’s something you can do repeatedly.”

Yahia Bakour

Founder

Read the case study →

Why do developers pay attention on daily.dev?

Michael on reaching developers by adding value and showing your culture rather than selling: authenticity cannot be manufactured, and it is what earns attention.

More from the team: the developer marketing series →

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

A few things they read and discuss

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

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.

Supply chain attacks Publish the package, the attack path and the fix; named specifics earn trust where vague "threats" do not
Auth done right Share the ten lines a developer would otherwise write wrong, as code they can copy
Security that developers tolerate Show the speed and the false-positive rate, with how you measured them

How do you target security 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: #security, #appsec, #devsecops, #authentication, #cryptography, #devops, 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 Security and AppSec 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.

Starter Be present. Growth Be seen often. Most brands start here Scale Be the default.

Explore my options →

Prices are quoted per company. See how plans work →

Where else can you reach security engineers?

Where security 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.

Channels for reaching security engineers, compared
Channel	Format	Target by stack	How you buy	Best for
	Your verified company page, your posts in their feed, the newsletter they chose, the homepage	Yes: security tags, seniority, region	Managed monthly plan	Building a brand developers follow, every week, with creative and reporting done for you
Security newsletters (tl;dr sec)	One sponsor slot per issue	By list topic	Per issue	Launch-week spikes
Reddit (r/netsec, r/cybersecurity)	Promoted posts	By subreddit and interest	Self-serve	Discussion and feedback
LinkedIn Ads	Sponsored posts and message ads	By job title, company and self-declared skills	Self-serve	Reaching managers and buyers by title
Black Hat, DEF CON, BSides	Booths and talks	By event	Sponsorship packages	Enterprise relationships
Hacker News	Show HN and Launch HN posts	None; the front page decides	Organic	One-off launches with a technical story
Security podcasts	Host-read sponsorships	By show	Per episode	Brand familiarity

Compare daily.dev with

Security newsletters tl;dr sec

Format: Your verified company page, your posts in their feed, the newsletter they chose, the homepage One sponsor slot per issuePromoted postsSponsored posts and message adsBooths and talksShow HN and Launch HN postsHost-read sponsorships
Target by stack: Yes: security tags, seniority, region By list topicBy subreddit and interestBy job title, company and self-declared skillsBy eventNone; the front page decidesBy show
How you buy: Managed monthly plan Per issueSelf-serveSelf-serveSponsorship packagesOrganicPer episode
Best for: Building a brand developers follow, every week, with creative and reporting done for you Launch-week spikesDiscussion and feedbackReaching managers and buyers by titleEnterprise relationshipsOne-off launches with a technical storyBrand familiarity

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

What do teams build with security engineers on daily.dev?

Build your brand with them

Show up every day in the reading security 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 security 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 security engineers where they already discover tools and ideas.

Brands building with developers on daily.dev

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

Guides on reaching security engineers

All guides: developer marketing resources →

Advertising to security engineers: your questions

daily.dev reaches millions of developers, and security engineers on it read vulnerability write-ups, auth deep dives and supply-chain news. 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.

Usually both. AppSec, secrets and supply-chain tools are bought by security teams and used by every developer who ships code. Your plan can put your research in front of #security and #appsec readers for the buyers and your fix-it guides in front of stack readers (#javascript, #python, #devops) for the users, and the weekly report shows what each group reads.

Your verified company page is where your advisories, research and hardening guides live. Your plan puts those posts in the feed of developers who read #security, #appsec and #devsecops, and in the Security and AppSec newsletter for a disclosure or a release. Lead with an audit checklist developers keep.

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 security engineers who read #security, #appsec, #devsecops. The following stays yours between campaigns.

Yes. Engineering stories, culture and open-source work published on your company page reach security 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
security 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 Web developers Go developers All audiences →

Ad products

In every plan

More ways to reach developers

Resources

Learn

Tools

Compare

Our audience

How to advertise to security engineers