<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Omar Soliman</title>
    <description>The latest articles on DEV Community by Omar Soliman (@omarcodes).</description>
    <link>https://dev.to/omarcodes</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4123307%2Fa047154b-fa9e-40f4-96c8-7786f146ec60.png</url>
      <title>DEV Community: Omar Soliman</title>
      <link>https://dev.to/omarcodes</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/omarcodes"/>
    <language>en</language>
    <item>
      <title>Who sponsors developer creators, September 2026</title>
      <dc:creator>Omar Soliman</dc:creator>
      <pubDate>Thu, 24 Sep 2026 12:09:37 +0000</pubDate>
      <link>https://dev.to/omarcodes/who-sponsors-developer-creators-september-2026-1lao</link>
      <guid>https://dev.to/omarcodes/who-sponsors-developer-creators-september-2026-1lao</guid>
      <description>&lt;p&gt;If you sell to developers, you have probably wondered which brands actually pay creators, and whether the ones you compete with are among them. Sponsorship marketplaces will sell you a guess. The creators themselves tell you for free, one "this issue is brought to you by" at a time, if you read enough of their posts.&lt;/p&gt;

&lt;p&gt;I run &lt;a href="https://devsponsors.com/" rel="noopener noreferrer"&gt;devsponsors&lt;/a&gt;, a directory of developer creators, and that is what it does: it reads the creators' own posts and issues, and when a creator names a sponsor in their own words, the brand goes on record with the sentence and the post it came from. No brand is listed from a guess, a media kit or a marketplace. Here is what the record says as of September 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  The numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;68 brands&lt;/strong&gt; are named as sponsors across &lt;strong&gt;81 disclosures&lt;/strong&gt; in the posts of 500 developer creators on YouTube, GitHub, Dev.to, newsletters and social platforms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;10 brands&lt;/strong&gt; are named by two or more creators: &lt;a href="https://devsponsors.com/sponsors/brilliant" rel="noopener noreferrer"&gt;Brilliant&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/coderabbit" rel="noopener noreferrer"&gt;CodeRabbit&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/unblocked" rel="noopener noreferrer"&gt;Unblocked&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/aws" rel="noopener noreferrer"&gt;AWS&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/endor-labs" rel="noopener noreferrer"&gt;Endor Labs&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/hubspot" rel="noopener noreferrer"&gt;HubSpot&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/mongodb" rel="noopener noreferrer"&gt;MongoDB&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/serpapi" rel="noopener noreferrer"&gt;SerpApi&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/viktor" rel="noopener noreferrer"&gt;Viktor&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/zapier" rel="noopener noreferrer"&gt;Zapier&lt;/a&gt; (2).&lt;/li&gt;
&lt;li&gt;Everyone else shows up once. A single disclosure is still a real buy, but it is not a program.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every brand links to a page that lists the creators who named it, with the quote: &lt;a href="https://devsponsors.com/sponsors" rel="noopener noreferrer"&gt;every brand seen sponsoring a developer creator&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faapdqe6gwx2lefkmjv6b.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faapdqe6gwx2lefkmjv6b.png" alt="Bar chart of the brands named by two or more developer creators, with the number of creators for each" width="800" height="384"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Newsletters are where the repeat buyers are
&lt;/h2&gt;

&lt;p&gt;Of the 29 developer and AI newsletters in the directory, 9 name their sponsors in the body of their issues, and between them they name 34 brands. The most disclosed newsletters: &lt;a href="https://devsponsors.com/o/product-growth" rel="noopener noreferrer"&gt;Product Growth&lt;/a&gt; (10), &lt;a href="https://devsponsors.com/o/the-system-design-newsletter" rel="noopener noreferrer"&gt;The System Design Newsletter&lt;/a&gt; (9), &lt;a href="https://devsponsors.com/o/ai-agents-simplified" rel="noopener noreferrer"&gt;AI Agents Simplified&lt;/a&gt; (6), &lt;a href="https://devsponsors.com/o/engineering-leadership" rel="noopener noreferrer"&gt;Engineering Leadership&lt;/a&gt; (5), &lt;a href="https://devsponsors.com/o/ben-s-bites" rel="noopener noreferrer"&gt;Ben's Bites&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/o/algomaster-newsletter" rel="noopener noreferrer"&gt;AlgoMaster Newsletter&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/bytebytego-newsletter" rel="noopener noreferrer"&gt;ByteByteGo Newsletter&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/jam-with-ai" rel="noopener noreferrer"&gt;Jam with AI&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/seattledataguy-s-newsletter" rel="noopener noreferrer"&gt;SeattleDataGuy’s Newsletter&lt;/a&gt; (1).&lt;/p&gt;

&lt;p&gt;That is not because newsletters sell more sponsorships than YouTube channels. It is because a newsletter writes the disclosure into every issue as text ("This issue is brought to you by HubSpot", "Thanks to AWS for partnering on this post"), where a YouTube channel says it out loud in the video and leaves the description bare. A text-based record will always see newsletters more clearly, and I say so on the page rather than pretending the video side is quiet.&lt;/p&gt;

&lt;h2&gt;
  
  
  The creators with the most named sponsors
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://devsponsors.com/o/product-growth" rel="noopener noreferrer"&gt;Product Growth&lt;/a&gt; (10), &lt;a href="https://devsponsors.com/o/the-system-design-newsletter" rel="noopener noreferrer"&gt;The System Design Newsletter&lt;/a&gt; (9), &lt;a href="https://devsponsors.com/o/ai-agents-simplified" rel="noopener noreferrer"&gt;AI Agents Simplified&lt;/a&gt; (6), &lt;a href="https://devsponsors.com/o/engineering-leadership" rel="noopener noreferrer"&gt;Engineering Leadership&lt;/a&gt; (5), &lt;a href="https://devsponsors.com/o/ben-s-bites" rel="noopener noreferrer"&gt;Ben's Bites&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/o/commonluke" rel="noopener noreferrer"&gt;commonLuke&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/o/hardware-haven" rel="noopener noreferrer"&gt;Hardware Haven&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/o/the-cherno" rel="noopener noreferrer"&gt;The Cherno&lt;/a&gt; (3).&lt;/p&gt;

&lt;p&gt;Most of these are newsletters, for the reason above. The count is sponsors on record, not sponsors ever; it grows as issues are read.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this says about developer marketing budgets
&lt;/h2&gt;

&lt;p&gt;Three things stand out.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Repeat programs are rare.&lt;/strong&gt; Ten brands with more than one creator, out of 68. Most devtool companies try creator sponsorship once. Whether that means it did not work or they never measured it, the record cannot say.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The same audience gets bought by rivals.&lt;/strong&gt; The System Design Newsletter alone names nine brands. A brand that sponsors one issue is buying the same readers as the eight others did. If you are one of those brands, the list of who else bought that audience is a market map you did not have to pay for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Most creators have said nothing in public.&lt;/strong&gt; 50 of 500 creators have a sponsorship confirmed on record (a named sponsor, a rate card or a sponsorship page), 41 run posts the platform flags as paid without naming the brand, 30 invite sponsorship in a bio or link, and 378 have nothing on record either way. Nothing on record is not a no.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How the record is built
&lt;/h2&gt;

&lt;p&gt;A brand enters only from a disclosure sentence in the creator's own post or issue. The sentence and the URL sit beside the name on every page and in the &lt;a href="https://github.com/devmarketing-co/developer-creators-sponsors" rel="noopener noreferrer"&gt;open dataset&lt;/a&gt; (CC BY 4.0). Audience figures come from the platforms' own APIs; a few independent newsletters carry the count printed on their own page and are labelled self-reported wherever it shows. Nothing is estimated. The full method is at &lt;a href="https://devsponsors.com/method" rel="noopener noreferrer"&gt;devsponsors.com/method&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you want the list for one question, the topic pages answer it: &lt;a href="https://devsponsors.com/topics/brands-that-sponsor-developer-creators" rel="noopener noreferrer"&gt;which companies sponsor developer creators&lt;/a&gt;, &lt;a href="https://devsponsors.com/topics/developer-ai-newsletters" rel="noopener noreferrer"&gt;which developer and AI newsletters take sponsorships&lt;/a&gt;, and &lt;a href="https://devsponsors.com/topics/ai-developer-youtubers" rel="noopener noreferrer"&gt;which AI YouTubers a devtool brand can sponsor&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>marketing</category>
      <category>devrel</category>
      <category>newsletter</category>
      <category>youtube</category>
    </item>
    <item>
      <title>The developer and AI newsletters you can sponsor, with their real subscriber counts</title>
      <dc:creator>Omar Soliman</dc:creator>
      <pubDate>Mon, 14 Sep 2026 20:22:11 +0000</pubDate>
      <link>https://dev.to/omarcodes/the-developer-and-ai-newsletters-you-can-sponsor-with-their-real-subscriber-counts-4npf</link>
      <guid>https://dev.to/omarcodes/the-developer-and-ai-newsletters-you-can-sponsor-with-their-real-subscriber-counts-4npf</guid>
      <description>&lt;p&gt;Newsletter sponsorship is the one channel where a devtool marketer can see the audience number before writing the email. Substack prints each publication's free subscriber count. Independent newsletters print theirs on an advertise page. Neither is an open rate, and I will come back to that, but both are real numbers a buyer can plan around.&lt;/p&gt;

&lt;p&gt;I keep &lt;a href="https://devsponsors.com/" rel="noopener noreferrer"&gt;devsponsors&lt;/a&gt;, a directory of developer creators. This is the newsletter slice of it as of September 2026: 29 newsletters, 25 on Substack and 4 on their own domain.&lt;/p&gt;

&lt;h2&gt;
  
  
  The largest, by the number their platform or page prints
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://devsponsors.com/o/the-rundown-ai" rel="noopener noreferrer"&gt;The Rundown AI&lt;/a&gt;, 1,700,000 self-reported subscribers; &lt;a href="https://devsponsors.com/o/superhuman-ai" rel="noopener noreferrer"&gt;Superhuman AI&lt;/a&gt;, 1,500,000 self-reported subscribers; &lt;a href="https://devsponsors.com/o/tldr-ai" rel="noopener noreferrer"&gt;TLDR AI&lt;/a&gt;, 1,100,000 self-reported subscribers; &lt;a href="https://devsponsors.com/o/semianalysis" rel="noopener noreferrer"&gt;SemiAnalysis&lt;/a&gt;, 315,000 free subscribers; &lt;a href="https://devsponsors.com/o/the-system-design-newsletter" rel="noopener noreferrer"&gt;The System Design Newsletter&lt;/a&gt;, 251,000 free subscribers; &lt;a href="https://devsponsors.com/o/product-growth" rel="noopener noreferrer"&gt;Product Growth&lt;/a&gt;, 240,000 free subscribers; &lt;a href="https://devsponsors.com/o/deep-learning-weekly" rel="noopener noreferrer"&gt;Deep Learning Weekly&lt;/a&gt;, 224,000 free subscribers; &lt;a href="https://devsponsors.com/o/latent-space" rel="noopener noreferrer"&gt;Latent.Space&lt;/a&gt;, 198,000 free subscribers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp1b7yqhrsr0oiag7wqmr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp1b7yqhrsr0oiag7wqmr.png" alt="Bar chart of the largest developer and AI newsletters by subscriber count, with self-reported counts marked" width="800" height="405"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Two kinds of number are mixed in that list, and the directory keeps them apart. A Substack count is stated by Substack, not by the author. A count on a newsletter's own advertise page is the publication's own claim, so it is labelled self-reported on every row, it never ranks against a platform count, and the page links the exact place it was read from. The full list, with the label on each, is at &lt;a href="https://devsponsors.com/topics/developer-ai-newsletters" rel="noopener noreferrer"&gt;developer and AI newsletters you can sponsor&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who already sponsors them
&lt;/h2&gt;

&lt;p&gt;9 of the 29 name their sponsors in the body of their issues, and between them they name 34 brands. The most disclosed: &lt;a href="https://devsponsors.com/o/product-growth" rel="noopener noreferrer"&gt;Product Growth&lt;/a&gt; (10), &lt;a href="https://devsponsors.com/o/the-system-design-newsletter" rel="noopener noreferrer"&gt;The System Design Newsletter&lt;/a&gt; (9), &lt;a href="https://devsponsors.com/o/ai-agents-simplified" rel="noopener noreferrer"&gt;AI Agents Simplified&lt;/a&gt; (6), &lt;a href="https://devsponsors.com/o/engineering-leadership" rel="noopener noreferrer"&gt;Engineering Leadership&lt;/a&gt; (5), &lt;a href="https://devsponsors.com/o/ben-s-bites" rel="noopener noreferrer"&gt;Ben's Bites&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/o/algomaster-newsletter" rel="noopener noreferrer"&gt;AlgoMaster Newsletter&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/bytebytego-newsletter" rel="noopener noreferrer"&gt;ByteByteGo Newsletter&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/jam-with-ai" rel="noopener noreferrer"&gt;Jam with AI&lt;/a&gt; (1), &lt;a href="https://devsponsors.com/o/seattledataguy-s-newsletter" rel="noopener noreferrer"&gt;SeattleDataGuy’s Newsletter&lt;/a&gt; (1).&lt;/p&gt;

&lt;p&gt;The disclosures come in a few shapes, and I read them as they are written: "This issue is brought to you by HubSpot", "This newsletter is sponsored by Unblocked", "(Thanks to AWS for partnering on this post.)", or a "Brought to you by:" header followed by one brand per line. Each brand links to the creators who named it, with the sentence, so a buyer can see which rivals already bought a given list before asking for the rate.&lt;/p&gt;

&lt;p&gt;Across all developer creators, 10 brands sponsor two or more, and most of those repeat buys are in newsletters: &lt;a href="https://devsponsors.com/sponsors/brilliant" rel="noopener noreferrer"&gt;Brilliant&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/coderabbit" rel="noopener noreferrer"&gt;CodeRabbit&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/unblocked" rel="noopener noreferrer"&gt;Unblocked&lt;/a&gt; (3), &lt;a href="https://devsponsors.com/sponsors/aws" rel="noopener noreferrer"&gt;AWS&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/endor-labs" rel="noopener noreferrer"&gt;Endor Labs&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/hubspot" rel="noopener noreferrer"&gt;HubSpot&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/mongodb" rel="noopener noreferrer"&gt;MongoDB&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/serpapi" rel="noopener noreferrer"&gt;SerpApi&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/viktor" rel="noopener noreferrer"&gt;Viktor&lt;/a&gt; (2), &lt;a href="https://devsponsors.com/sponsors/zapier" rel="noopener noreferrer"&gt;Zapier&lt;/a&gt; (2).&lt;/p&gt;

&lt;h2&gt;
  
  
  What nobody can tell you
&lt;/h2&gt;

&lt;p&gt;An open rate. Substack does not publish one, and an advertise page's open rate is the publication's own claim. The subscriber count is the size of the list, not the size of the audience that reads a given issue. Some newsletters also send some issues only to paying subscribers; the directory notes the share of recent issues that went to the whole list, because a sponsored slot in a paid-only issue reaches far fewer people than the count suggests.&lt;/p&gt;

&lt;p&gt;Prices are the other gap. In the whole directory, only a handful of creators print a rate. Advertise pages mostly take an enquiry. The directory never estimates an audience figure, and where it shows a price estimate for a placement it is labelled as arithmetic on a public benchmark, with the arithmetic shown.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I would use this
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Start from the topic page and sort by the figure you trust: Substack counts for the platform-stated list, then the self-reported ones as a separate conversation.&lt;/li&gt;
&lt;li&gt;Open the brands column before you email. If three rivals sponsored a newsletter last month, you have your answer about whether that audience buys.&lt;/li&gt;
&lt;li&gt;Ask for the recent send count and the free-list share, not the open rate. A publisher who answers with a screenshot is the one to work with.&lt;/li&gt;
&lt;li&gt;Give every placement its own link so you can compare newsletters against each other, not against a benchmark.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The method behind every figure is at &lt;a href="https://devsponsors.com/method" rel="noopener noreferrer"&gt;devsponsors.com/method&lt;/a&gt;, and the brands seen sponsoring developer creators, newsletter or not, are at &lt;a href="https://devsponsors.com/sponsors" rel="noopener noreferrer"&gt;devsponsors.com/sponsors&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>newsletter</category>
      <category>ai</category>
      <category>marketing</category>
      <category>devrel</category>
    </item>
  </channel>
</rss>
