Who Are Hanami 2.0 Developers?
Hanami 2.0 is a modern, full-stack Ruby framework built around Dry-rb principles: explicit dependencies, functional architecture, type-safe repositories, and clean layer separation. Developers adopting Hanami 2.0 have deliberately moved beyond the Rails convention-over-configuration model — they are experienced Ruby engineers making a deliberate architectural choice.
This makes Hanami developers a uniquely valuable audience for developer tool companies, infrastructure vendors, and any product serving experienced Ruby engineers. They signal intent through GitHub activity long before reaching your marketing funnel.
GitHub Signal Sources for Hanami Developer Leads
- Stargazers on hanami/hanami — developers evaluating or adopting Hanami 2.0
- Stars on hanami/api, hanami/view, hanami/db, dry-rb ecosystem repos
- Issues mentioning "hanami 2 migration", "hanami rom", "hanami action", "hanami slice"
- Code containing "Hanami::Action", "Hanami::View", "Hanami::Application" in public repos
- Discussions about "Hanami vs Rails", "Hanami with dry-schema", "Hanami monolith"
- PRs adding Hanami to a new service in an existing Ruby monorepo
Signal Context from Hanami Ecosystem Repos
Beyond hanami/hanami itself, GitLeads monitors the full Dry-rb ecosystem that Hanami is built on: dry-monads, dry-schema, dry-validation, dry-struct, rom-rb, sequel. Developers active in these repos are building with the same architectural patterns as Hanami.
// Example Hanami developer lead signal pushed to Pipedrive
{
name: "Lars Eriksson",
github: "larserik",
email: "lars@startup.se",
company: "Nordic SaaS",
location: "Stockholm, Sweden",
followers: 289,
topLanguages: ["Ruby", "TypeScript", "Elixir"],
signal: {
type: "keyword",
source: "github_issues",
repo: "hanami/hanami",
keyword: "Hanami 2 slice architecture",
triggeredAt: "2026-05-14T11:15:00Z",
},
}Integration Stack for Hanami Developer Outreach
- HubSpot: contact created with "Hanami Ruby" tag, enriched with company domain
- Slack: alert to #devrel channel with signal context and GitHub link
- Apollo.io: add to "Ruby Engineers" sequence with Hanami-specific personalization
- Clay: enrich with LinkedIn data to identify company size and tech stack fit
- Smartlead: reference the exact Hanami issue or repo they starred in opening line
ICP Filters for Hanami 2.0 Developer Leads
- Top language: Ruby — primary filter
- Followers 200+: senior engineers, not beginners exploring Ruby
- Company present: professional developer building production apps
- Signal context contains "slice", "action", "repository", "view" — using Hanami internals, not just exploring
- Also active in dry-monads or rom-rb: deep adopter with production intent