The ultimate guide to advertising to developers in 2026

tldr: Most lists of developer newsletters are written for developers to read, not for marketers to buy. This one names who accepts sponsorship, who does not, and who each publication actually reaches. The most valuable entries are the ones nobody lists: two publisher networks worth roughly 775,000 developers between them, and several six-figure newsletters that never appear on these roundups.

Audience figures below are self-reported by each publisher and vary between sources, sometimes by a lot. Treat them as scale, not as precision, and ask for current numbers before you commit budget.

Why developer marketing matters more in the AI era

Three things changed at once, and they all point the same way.

The developer became the buyer. AI tooling is adopted from the bottom up. An engineer tries a coding agent on a personal card, the team copies them, and procurement arrives months later to formalise something already running in production. The decision that used to sit with a CIO now sits with whoever opened the terminal. That turns developer-facing media from a brand exercise into the actual sales channel.

Search stopped being a reliable way to get found. Nearly every technical query now returns an AI Overview, and a growing share of developers ask an assistant rather than a search engine. Both answer the question without sending anyone a click. The old motion, where you published a good technical post and a developer eventually found it, is thinning out. Newsletters and podcasts are delivered rather than searched, which makes them much harder for an answer engine to sit in front of.

Trust got scarcer as content got cheaper. Generated technical writing flooded the same channels developers used to rely on. When everything reads as plausible and almost none of it is verified, a named curator who has spent years deciding what goes in their issue is worth more, not less. That scarcity is the thing you are actually buying.

There is also simply more competition for the same attention. Nearly every AI startup now ships something developer-facing: agents, model APIs, eval tooling, orchestration, testing. The number of companies chasing developers has multiplied. The number of publications those developers genuinely read has not.

What makes developers different to buy

Developers are the hardest technical audience to buy. They block ads, they distrust marketing language by default, and they will read your documentation before they read your landing page. The lists are also small: a newsletter with 20,000 engaged backend engineers is a serious buy in this category, where a general B2B list of that size would be a rounding error.

That combination is why newsletter advertising works here when display advertising does not, and why general SaaS advertising playbooks transfer badly. Newsletter ads arrive inside something the reader chose to open, from a curator they already trust, next to content they came for. It is closer to a recommendation than an advertisement, which is exactly why the publications that protect that trust are the ones worth buying.

Which developer newsletters accept sponsorship?

Grouped by who they reach, because you should buy on audience fit rather than raw subscriber count. Not ranked. It runs from the largest tech newsletters down to sharply focused engineering newsletters with a few thousand readers, and in this category the small ones often win.

The foreword publication by Hashnode

Audience: developers and engineering leaders working on AI coding, agents, and developer tooling. Coding agents and CLIs, MCP and agent infrastructure, model APIs and what they cost, testing and evals.

Sponsorship: yes. Reach us at theforeword@hashnode.com.

Disclosure: The foreword publication by Hashnode is this publication. It is listed here because a directory that omits its own inventory is less useful, not more, and it is held to the same disclosure standard as anything else we cover.

AI and AI engineering

General developer

Engineering leadership and architecture

Language and framework

Infrastructure, cloud, and reliability

Elsewhere worth knowing

The two networks nobody treats as networks

This is the part every other list misses, and it is the most useful thing on this page if you are buying at any scale.

Cooper Press publishes JavaScript Weekly, Frontend Focus, Node Weekly, React Status, Ruby Weekly, Golang Weekly, Postgres Weekly, JAMstacked, and Deno Weekly. That is roughly 450,000 developers across nine newsletters, from one publisher, in one conversation. Every roundup names these individually. None of them points out that you can plan them as a portfolio and segment by language without negotiating nine times.

Libhunt runs the "Awesome" family: Awesome Java, Awesome Python, Awesome Go, Awesome Rust, Awesome C++, Awesome Kotlin, Awesome Elixir, Awesome PHP, Awesome Node.js, Awesome Swift, Awesome iOS, Awesome .NET, Awesome React, Awesome Scala, and more. Each sits around 21,700 subscribers, all sell sponsorship, and there are more than fifteen of them. Call it 325,000 developers, pre-segmented by language, from a single operator. It appears on no developer newsletter roundup we could find.

Between them that is roughly 775,000 developers reachable through two relationships.

Where the answer is no

The most useful thing a list like this can tell you is where not to spend your time.

The Pragmatic Engineer does not run newsletter sponsorships. With more than a million readers it describes itself as the number one software and AI engineering newsletter on Substack, and its own about page is unambiguous: "The newsletter does not run advertisements or sponsorships", alongside "I don't take sponsorships of any kind, and disclose any affiliation I would have with the companies covered."

There is a door, and it is not the newsletter. The Pragmatic Engineer Podcast does carry limited podcast sponsorship, and it reaches an overlapping audience. If those readers are your target, the podcast is the buy and no amount of emailing about the newsletter will change that.

Latent Space does not sell traditional sponsorships. It is the definitive publication for AI engineering, with an audience of exactly the people most AI startups want, and its own page states it works with PR teams ahead of major product and funding announcements on roughly a month of lead time, while explicitly not accepting cold emails. If you want that audience, the route is an announcement worth covering, planned early. It is not a media buy.

More broadly, treat any publication whose value comes from editorial independence the same way. The reason its recommendation is worth something is that it cannot be bought, and the pitch that works is the one that gives the writer something genuinely worth telling their readers.

How to read a newsletter media kit

Every figure on this page is self-reported, and the spread between sources is wider than you would expect. One widely cited list puts TLDR at 275,000 while another puts it above a million. Both are recent. Neither is lying, they are counting different things: total signups, active subscribers, across all editions or one.

Three questions worth asking before any buy:

Active subscribers, not signups. A list of 100,000 where 30,000 open is a better buy than a list of 300,000 where 25,000 do, and the second number is the one that rarely appears in a media kit.

Click rate, not open rate. Open rates have been unreliable since Apple's Mail Privacy Protection began pre-loading images in 2021. Clicks are the only number that survives it, and any publisher serious about advertising will have them.

Audience composition. "Developers" is not a segment. Twenty thousand backend engineers and twenty thousand bootcamp students are the same number and different products entirely.

What actually converts for developer tools

An argued position rather than a benchmark, and worth what you paid for it: any developer marketing strategy that works starts from one observation, which is that developers do not respond to brand advertising. They respond to a specific technical claim they can verify in a single click.

The sponsorships that work send people to documentation, a benchmark, a changelog, or a repository. The ones that do not send people to a homepage with a headline about transforming their workflow. A developer who clicks your sponsorship is doing so to evaluate you, and if the destination is a marketing page they have learned nothing and they leave.

Two things follow from that.

Relevance to the issue beats reach. A tool that fits what that week's content is about will outperform a bigger list where the fit is generic. This is the argument for the smaller, sharper newsletters in the tables above, and the reason a 3,700-subscriber list can outperform one twenty times its size.

Judge on pipeline, not on clicks. Developer tool consideration cycles run long. Somebody who clicks a sponsorship in March may open an account in June after seeing you three more times. Attribution that only counts the last touch will tell you sponsorships do not work, and it will be wrong.

FAQ

Which developer newsletters accept sponsorship?

Most of the large ones do, including TLDR, TLDR AI, ByteByteGo, The Real Python Newsletter, Baeldung, Bytes, Console.dev, Last Week in AWS, and the full Cooper Press and Libhunt networks. The significant exceptions among major publications are The Pragmatic Engineer, whose newsletter does not run advertisements or sponsorships at all, and Latent Space, which does not run traditional advertising. The Pragmatic Engineer Podcast is a separate matter and does carry limited sponsorship.

How do I reach developers if a publication does not sell ads?

Give it something worth covering. Publications that do not sell advertising still cover launches, benchmarks, and technical work that their readers care about. Latent Space, for example, states it works with PR teams roughly a month ahead of major announcements. That is a longer lead time than a media buy and it is not guaranteed, but the resulting coverage carries more weight than a placement.

What is a good audience size for a developer newsletter sponsorship?

Fit matters more than size in this category. A newsletter with 5,000 readers who all work in your exact problem space will usually outperform 200,000 general developers. Start from who you need to reach and work backwards, rather than sorting the list by subscriber count.

Is it better to sponsor one big newsletter or several small ones?

Several small ones, if they are well matched, and the two networks above make that practical to administer. Frequency matters in a category with long consideration cycles, and appearing in three publications a developer reads is worth more than appearing once in a larger one they skim.

What is the best way to advertise to developers?

There is no single best way to advertise to developers, but the channels that work share one property: the developer opted into them. Newsletters, podcasts, and curated sites are read by choice, which is why they outperform display. The best way to advertise to developers is to appear in something they already read, with a claim they can verify in one click.

How do you market to engineers?

Marketing to engineers works when it stops looking like marketing. The short answer to how to market to engineers, and how to market to developers generally, is that you lead with the technical claim, the benchmark, or the documentation rather than the value proposition. Engineers evaluate before they buy, so digital marketing for engineers has to survive that evaluation. Anything that reads as a pitch gets discounted immediately, and anything that reads as useful information gets forwarded.

What are the main developer marketing channels?

Newsletter sponsorship, podcast sponsorship, sponsored content on developer sites, conference and community sponsorship, open-source sponsorship, and search. Framed the other way, how to reach developers comes down to whichever of those they already opted into. The tables above cover the first three, which are the ones most devtool and AI startups start with because they are measurable and do not require a headcount to run.

What is a newsletter CPM?

CPM is the cost per thousand impressions, the way most newsletter ad rates are quoted. Developer newsletters run higher than general B2B because the audiences are smaller and harder to reach, and newsletter sponsorship rates vary enough between publications that any figure quoted here would mislead you. Ask each publisher for current rates, and ask for click numbers alongside them, because CPM without a click rate tells you what you paid rather than what you got.

How do I sponsor The foreword publication by Hashnode?

Email theforeword@hashnode.com with what you are launching, who you want to reach, and your timeline. Sponsorship is separate from editorial: placements are labelled, and buying one does not buy coverage, a review, or a place in a comparison.

---

Figures gathered on 26 July 2026 from publishers' own sponsorship pages and public directories. This page is updated as publications change their terms, so if something here is out of date, tell us at theforeword@hashnode.com and we will correct it.