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

How to advertise to Ruby developers

To advertise to Ruby developers, be where they read every day: daily.dev Ads, Ruby Weekly, Rails World and r/rails. daily.dev gives you a verified company page they follow and puts your posts and releases in the feed of developers who read #ruby and #rails, and in the Web Development newsletter, in one plan we run for you.

Explore my options→ See how plans work

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

  • #ruby
  • #rails
  • #backend
  • #webdev
  • #postgresql
  • #javascript

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

Where Ruby developers get their news

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

  1. 1 Hacker News
  2. 2 RUBYLAND
  3. 3 Ruby Flow
  4. 4 Rails
  5. 5 Ruby Weekly
  6. 6 Fireship

What they also read

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

  • #css8%
  • #database7%
  • #ai-agents6%
  • #security5%
  • #react5%
  • #architecture3%

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

How do you reach Ruby developers?

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. Follow the conventions and the audience follows you.

    Ruby developers judge a gem by how closely it matches the Rails way: a generator, an initializer, sensible defaults. Publish examples that show those, and the tool is understood at a glance.

  2. The readme is the product page.

    This audience reads the gem readme before any marketing site. Link your posts to the repository or a page written like a readme, with the install and the first call at the top.

  3. Write for developers who have shipped Rails for years.

    Many Rails developers run mature production apps. Skip the introduction to the problem and publish how your tool fits a mature app, with the migration and the rollback.

  4. Postgres is the stack, so say what you do with it.

    Postgres sits under a great many Rails apps. A post about how your tool works with the database they already run has an angle of its own; name the integration plainly.

context.dev
“You guys were awesome. I didn’t have to do anything. I basically just said what I wanted and it was running.”

Yahia Bakour

Founder

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 Ruby developers read, and what should your brand say?

A few things they read and discuss

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

  1. Callbacks, Concerns, and Current: Avoiding Hidden Dependencies in Rails Ruby Flow 1 0
  2. Ruby 3.4.11 Released Ruby 2 22
  3. Stop building side projects. Nobody cares — and here's the uncomfortable math. DEV 20 48

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.

  • Rails conventions Publish the generator and the initializer in a working example
  • Deploying Rails Walk through push to live, with the steps counted
  • Postgres as the stack Write about what your product does with the database they already run

How do you target Ruby developers 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
#ruby, #rails, #backend, #webdev, #postgresql, #javascript, 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 Web Development 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 Ruby developers?

Where Ruby developers 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
Ruby newsletters Ruby Weekly, Short Ruby
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: #ruby, #rails and related tags, 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 Ruby developers on daily.dev?

Build your brand with them

Show up every day in the reading Ruby developers 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 Ruby developers follow you, discuss your posts and come back for your next release.

Strengthen your employer brand

Share engineering stories, culture and open roles with Ruby developers 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 Ruby developers

All guides: developer marketing resources →

Advertising to Ruby developers: your questions

Yes. Your posts can reach only developers who read #ruby, or #ruby with #rails, #backend, #postgresql or #webdev, with seniority and region on top. It is built on what developers read, not a self-declared profile.

daily.dev reaches millions of developers, and Ruby developers there read about Rails, Postgres and deploying web apps. 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.

Your verified company page comes first, with Rails examples, release notes and engineering posts. Your plan puts them in the feed of developers who read #ruby and #rails and in the Web Development newsletter. Lead with a quickstart that follows Rails conventions.

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 Ruby developers who read #ruby, #rails, #backend. The following stays yours between campaigns.

Yes. Engineering stories, culture and open-source work published on your company page reach Ruby developers 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
Ruby developers 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: Backend developers PHP developers Full-stack developers All audiences →