Hanakai

Hanami 3.0: In full bloom

2026-06-30T23:30:00+00:00

From the very beginning we set out to make Hanami a different kind of Ruby framework: clear, modular, and built to grow. Today it comes into full bloom. We’re thrilled to share Hanami 3.0 with you!

This release rounds out the framework with three big new features: mailers, internationalization, and Minitest. On top of that, your apps are now faster by default, and your developer experience is sharper, from your logs all the way to your assets.

First-class mailers

Our long lost gem is back! Hanami apps now come with integrated mailers, which feel right at home next to your actions, views, and operations.

Mailer classes describe everything you need to deliver an email:

module Bookshelf
  module Mailers
    class Welcome < Bookshelf::Mailer
      from "welcome@bookshelf.test"
      to { |user:| user.email }
      subject { |user:| "Welcome to Bookshelf, #{user.name}!" }

      expose :user
    end
  end
end

As standalone objects, mailers are injectable via the Deps mixin and accessible wherever you need them. Call .deliver and the mailer will use your input to prepare headers and render mail body templates, which work as a fully featured extension of your view layer.

Mailers support multiple delivery methods. SMTP delivery works out of the box: populate some env vars for your SMTP host and you’re good to go. In test, your emails are accumulated in memory for you to inspect.

If you need something more, you can also write your own delivery methods. In addition to a clean interface for these, Hanami Mailer provides hooks for threading delivery options all the way through your mailers, allowing new delivery methods to make the most of special features offered by email delivery providers.

Like all our gems, Hanami Mailer is also designed for standalone use. Check out the comprehensive README for everything you need to know about using it in your Ruby app.

Hanami Mailer leans on the venerable mail gem to handle all its low-level mail wrangling. Thank you to the mail maintainers for all their work over the years!

Built-in internationalization

Taking your apps to the world just got easier: i18n is now built right into Hanami. Bundle the i18n gem and Hanami sets up a self-contained translation backend in your app and every slice, with translate and localize helpers ready to use across your actions and views.

Your translations live in config/i18n/ in your app or slice:

# config/i18n/en.yml
en:
  posts:
    index:
      title: "Latest posts"
    create:
      created: "Your post is live!"
  greetings:
    welcome: "Welcome, %{name}!"

From there, i18n helpers are everywhere you’d expect them! Like in your views:

<%# app/templates/posts/index.html.erb %>
<h1><%= t(".title") %></h1>

And your actions:

# app/actions/posts/create.rb
def handle(request, response)
  response.flash[:notice] = t(".created")
  # ...
end

And for everywhere else, the "i18n" component is just one Deps mixin away:

class Greeter
  include Deps["i18n"]

  def call(name)
    i18n.t("greetings.welcome", name:)
  end
end

We’ve got localization too. localize formats your dates and times for the current locale, and ships with sensible defaults for English:

localize(Date.new(2026, 5, 22))
# => "Fri, 22 May 2026"

localize(Time.new(2026, 5, 22, 9, 5), format: :short)
# => "22 May 9:05 am"

Like every aspect of Hanami, i18n is designed to work out of the box with minimal setup, but there are plenty of settings if you need something custom. Check out the i18n guide for the full picture.

You can’t spell internationalization without the i18n gem, which does all the heavy lifting for this new feature. So a big en-AU “cheers, mates” to the i18n maintainers — thank you for helping Rubyists the world over!

Now with Minitest

Hanami has always shipped with a ready-to-go RSpec setup. We’re delighted we can finally make the other half of you happy, thanks to our brand new Minitest support!

Pick your testing framework when you generate an app:

$ hanami new my_app --test=minitest

RSpec stays our default, but reach for Minitest and you’ll now get an equally complete setup, rather than having to build something yourself.

A big thank you to Ryan Davis and all the contributors for their work on Minitest. Minitest ships with Ruby itself, and we’re glad to make it part of the Hanami story going forward.

Faster by default

Hanami 3.0 is significantly faster, and you can enjoy the benefits right from the get-go. In a test app, the same request runs around 3.7x faster over HTTP while allocating a fraction of the memory.

Hanami now memoizes your components by default. This means that each component in your app’s containers is resolved just once and then reused, rather than built fresh every time it’s needed.

This is the change you’ll really feel. We took an app whose action resolves a graph of nine components and renders a view, then measured the same request on 2.3 and 3.0. In 3.0, there were 14x fewer allocations per request and around 3.7x the throughput over HTTP (and closer to 9x throughput when measured in-process, where the server isn’t the bottleneck). Tail latency dropped too: p99 reduced from 20ms to 4ms as the per-request allocation churn and GC pauses went away.

We also focused on improving performance across the hottest parts of the framework:

Hanami Action snapshots each action’s config up front rather than recomputing it per-request, and overall allocates far less per request. A minimal action drops from 88 allocations to 14 — that’s 84% fewer — and runs around 4.5x faster in isolation.
Hanami View gets the same config snapshot treatment, and also no longer decorates exposures by default. A minimal render drops from 88 allocations to 39 and runs around 2.9x faster.

The best part of all this? It’s a free lunch! Upgrade to 3.0 and your apps simply run faster, on less memory, all without any changes to your code.

A special thank you to Sean Collins for driving much of our performance work for 3.0. We love you 3.7x more than before!

Clearer, more useful logs

We’ve given logs some love for 3.0, across both day-to-day development and production.

In development, logs are now colorized by default. SQL statements are formatted to match your request logs, and they’re also syntax highlighted when the rouge gem is bundled.

SQL statements now log at the :debug level rather than :info, for quieter production logs, and you can tune this with config.db.log_level.

You can also conveniently set the log level from the env with HANAMI_LOG_LEVEL, which takes precedence over any config in your app class.

Underneath, Hanami now guarantees a consistent interface for its logger (even if you configure a third-party replacement), so you can always count on:

Structured logging, via keyword args passed to the standard log methods.
Tagged logging, via #tagged blocks.

Read our revamped logger guide to learn more.

Smoother asset watching

hanami assets watch now keeps pace with more of your work: it picks up newly added and removed entry points, and reacts to changes in static assets like images and fonts. In earlier versions, each of these meant restarting the watcher. Now it just keeps up, so you can stay in the flow!

We also published a spec covering how any asset bundler can plug cleanly into Hanami. Our own bundler is based on esbuild, but we don’t want you to feel locked in! We’d love to see you bring your favorite bundler to Hanami.

Body parsing comes to Hanami Action

Hanami’s request body parsing has moved out of middleware and into Hanami Action, where it’s now driven by your formats config. Your actions parse exactly the formats you accept, and you can configure this right alongside the rest of your content negotiation.

Parsers for multipart form bodies and JSON work out of the box. And if you need something else, you can register your own:

formats.register(:custom, "application/custom", parser: ->(body, env) { ... })

Learn more in our formats and media types guide.

Simpler views with undecorated exposures

View exposures are now undecorated by default. Your templates receive exactly what you expose, with no decoration unless you ask for it. This is a more predictable default, and avoids extra work when decoration isn’t strictly required.

When you do want to decorate, the new .decorate method makes those exposures stand out in your code. You can also bring back the old behaviour across a view with config.decorate_exposures = true.

A cleaner foundation

A major new version is a chance to put the house in order:

hanami-controller is now hanami-action. The gem name finally matches the classes we’ve been using for years. Require it as hanami-action or hanami/action.
hanami-validations has been retired. Hanami Action now reaches for dry-validation directly for your action’s params and contracts, with one fewer gem in between.

Hanami 3.0 also requires Ruby 3.3 or newer.

The result is fewer moving parts, clearer names for the gems we use, and a more approachable Hanami overall.

And much more!

We’ve landed plenty of smaller refinements in 3.0 too:

New hanami generate provider and hanami generate mailer generators.
A --force option across all generators, to overwrite existing files instead of stopping.
A --name option for hanami new, to set the app namespace separately from the directory path: hanami new my_bookshelf --name=bookshelf.
--gem-source=gem.coop for hanami new installs gems from our gem.coop namespaces.
Generated apps require Puma 7.1 and drop app preloading boilerplate from config/puma.rb.
A --template-engine option for hanami new and hanami generate creates templates for the given engine (erb, haml, or slim). Set a project-wide default with config.default_template_engine in your app class.
Explicit redirect helpers in the router: permanent_redirect (301) and temporary_redirect (302), with plain redirect now requiring an explicit code: argument for clarity.
Hanami::Settings::CompositeStore for chaining settings lookups across multiple stores.
Hanami::Slice.with_slices returns a slice together with all its nested slices.
Hanami View exposes the currently-rendering template name as Hanami::View::Scope#template_name and Hanami::View::Context#current_template_name (this supports our relative i18n key lookups).
Raise a helpful error when a slice is called as a Rack app with no routes available.
Various fixes: multipart uploads to the router, URL generation with array variables, duplicate routes on generate action, and more.
A beautiful new welcome screen, matching our Hanakai visuals. (Thank you Max!)

Try it out

You’re only a few commands away from a new Hanami 3.0 app:

$ gem install hanami
$ hanami new my_app
$ cd my_app
$ bin/hanami dev
$ open http://localhost:2300

We’d love to hear how you go! Come say hi in our forum or our chat. Our community is super friendly and always willing to help you on your Hanami journey.

Upgrading from 2.3

Already on 2.3? Our 3.0 upgrade notes walk you through every step.

Thank you to our contributors!

Thank you to everyone who contributed to this release:

Thank you to our sponsors!

This release is another huge step forward for Hanami, and there’s no way we could have done this without the support of our sponsors. Thank you, from the bottom of my heart!

Thank you to our business sponsors:

Sidekiq, our Platinum sponsor.
Brandon Weaver, our Gold sponsor.
Honeybadger, FastRuby.io, AppSignal and SerpApi, our Silver sponsors.

And thank you to all the individuals supporting Hanakai through GitHub Sponsors and Open Collective. Your encouragement means the world!

Hanami is in full bloom today, but a garden is never finished, and there’s plenty more we want to grow. Your support is what makes that possible. We’d love for you to become a sponsor.

Help us test the Hanami 3.0 release candidate

2026-06-16T13:00:00+00:00

Today we’re sharing the release candidate for Hanami 3.0, feature-complete and ready for testing. We’d love your help to give it a good workout before our final release—which, all going well, will be in just a couple of weeks!

What’s coming in 3.0

There’s a lot I’m excited for in 3.0, but I’ll save the full announcement for when it ships. For now, here’s where we’d love your help with testing.

Built-in i18n

Internationalization is now a built-in feature. Bundle the i18n gem and Hanami loads your translations and makes translation and localization helpers available across your views and actions. See Previewing i18n integration in Hanami 3.0 for details.

First-class mailers

We’ve rebuilt Hanami Mailer and integrated it into the framework, with generators, templates, and SMTP delivery. See Previewing mailers in Hanami 3.0 for more.

Minitest support

We’ve created a new Hanami Minitest gem to give you a fully integrated Minitest setup. Activate it with hanami new --test=minitest. See all the details in Feedback on Hanami Minitest.

Memoized components

Container components are now memoized by default: each is resolved once and reused, instead of being built fresh each time. This is one of several performance improvements landing in 3.0, and a good one to test. If you have a component that cannot safely be memoized, you can opt it out.

Improved logging

Web and SQL logs are colorized by default in development. SQL queries are now logged as consistently structured entries, syntax highlighted when the rouge gem is bundled. SQL logs are now emitted at the :debug level for cleaner production logs, which you can adjust with config.db.log_level.

Hanami ensures that structured and tagged logging is available even if you configure your own alternative logger. Emit structured logs via keyword args on the main log methods, and tagged logs via tagged blocks. You can also now control the overall app log level via a HANAMI_LOG_LEVEL env var.

Smoother asset watching

hanami assets watch now keeps up with more of your changes: it picks up newly added or removed entry points, and reacts to edits to static assets like images and fonts. Previously, both meant restarting the watcher.

Other changes

Here are a few more changes worth flagging, especially if you’re upgrading an existing app:

The actions gem is renamed from hanami-controller to hanami-action.
The hanami-validations gem is retired. Hanami Action now checks for dry-validation directly.
Views default to undecorated exposures.
Request body parsing has moved into Hanami Action, driven by your formats config.
Hanami now requires Ruby 3.3 or newer.

Upgrading an existing app

Already on 2.3? Our 3.0 upgrade notes walk you through every step, from the required changes through to the optional new features above.

Try it out

You can step into the 3.0 future with just a few commands:

$ gem install hanami --pre
$ hanami new my_app
$ cd my_app
$ bin/hanami dev
$ open http://localhost:2300

Tell us how you go!

This is the moment your feedback makes the biggest difference. If you hit a snag or just want to share how it went, come talk to us on our forum or chat. We’d love to hear from you!

Thank you to everyone who’s helped on the road to 3.0, and thanks in advance to everyone about to help us test it.

Welcome, SerpApi!

2026-05-29T04:00:00+00:00

We’re thrilled to welcome SerpApi as a new silver-tier Hanakai sponsor!

SerpApi is the world’s leading provider of search data, pioneering APIs that turn search engine results into structured, developer-ready information. Founded in 2017, the company enables developers and organizations around the world to integrate live search insights from sources like Google, Bing, and YouTube.

SerpApi comes on board as we near the first anniversary of our sponsorship program. Support like this has been instrumental in everything we’ve achieved this past year: shipping Hanami 2.3, launching Hanakai, and cooking up a very special Hanami 3.0 release—more on that one soon!

SerpApi is proud to sponsor open source community initiatives and support the continued development of the Hanakai projects. At SerpApi, we are Rubyists at heart and want to see our ecosystem grow.

— Josef Strzibny, Ruby Developer Advocate, SerpApi

Thank you to Josef and the SerpApi team for reaching out to us and making this happen! Your support brings life to Hanakai and our vision for Ruby.

If you or your business would like to join SerpApi in supporting our work, check out our sponsorship options. We have something for everyone, and we’d love to welcome you to the family!

Welcome to Hanakai

2026-05-01T02:00:00+00:00

If you’ve followed Hanami for a while, you’ll know we’re rather fond of flowers. Today our garden has grown: Hanami, Dry, and Rom — three projects that have lived alongside each other across a decade and billions of downloads — are finally coming together as one. Welcome to Hanakai!

With Hanakai, we’re building a single shared community around the gems you know and love. The gems will carry on, now cared for by a bigger, unified team. And with our beautiful new website, now you can discover our vision for Ruby more easily than ever.

Loosely translated from the Japanese 花会, Hanakai means “flower fellowship”, sharing its first character 花 with Hanami, “flower viewing”. With this name, we carry forward Hanami’s spirit of nature and community. From today, our blossoms bloom together, and we invite you to join us!

A new look for our family

To go with our new name, we’re unveiling our new look. This is a brand that truly reflects who we are as a community: friendly, humane, and a little bit fun!

Our logos share a common spirit, while letting each project preserve its own identity. That’s how we want Hanakai to feel — for everyone.

A huge thank you to Aaron Moodie for bringing this vision to life. Aaron first joined us to design the welcome screen for new Hanami apps, and now he’s extended this welcome to the whole world. Thank you, Aaron, this is everything I could have hoped for!

A new home on the web

You’re reading this on our brand new website, now at hanakai.org. Here we’ve brought everything together: project and community info, our blog posts, and guides for every aspect of using our gems. Our refined typography and rebuilt search function make finding what you need a pleasure.

Fittingly, this site is a Hanami app! It’s fully open source, so you can check it out to see how we build Hanakai with Hanakai. All our guides now live together as Markdown files inside this repo, ready for your contributions!

Another huge thank you goes to Max Wheeler — every pixel of this site is Max’s work. He designed and built the entire frontend, and has been a thoughtful, generous collaborator the whole way through. It brings me so much joy just to click around and see everything fitting so well together. Thank you, Max, we couldn’t have done it without you.

Getting this site together has been a big effort, so I have many more thanks to share. For starters, thank you to Josephine Hall for taking over work on this while I focused on shipping a Hanami release; I needed that help! And thank you to Paweł Świątkowski, Philip Arndt, Mathew Button, Marco Roth, Adam Lassek, Jane Sandberg and Paul Oguda for their contributions along the way!

What’s next

Bringing Hanakai to you is a momentous shift for our corner of the Ruby world, and one we’ll certainly celebrate!

But we haven’t stopped moving — there’s plenty to look forward to:

A new release of Dry Operation with a slew of niceties.
A feature-packed Hanami release. Keep an eye out for a release candidate soon!
New “Hanami for Rails developers” guides.
Our sponsorship drive for 2026. Your support has brought us this far — help us take the next steps!

Join us

Our new garden is open, and we’d love for you to join us:

Chat with us on Discord.
Start a thread on our forum.
Subscribe to our newsletter to stay up to date with our announcements.
Follow along on Mastodon or Bluesky.

Of all our projects, our community is by far our most important. With Hanakai, it’s stronger than ever, and ready to welcome you in. Here’s to many seasons ahead!

State of Hanami, December 2025

2025-12-22T12:30:00+00:00

I’m very pleased to share our State of Hanami update for 2025! We’re back for our second time. If you want to get caught up, check out our update from last year.

This has been a pivotal year for Hanami, our first steps into a new era: we made a substantial new release, began unifying our ecosystem, expanded our team, launched our sponsorship program, and saw a real uptick in community activity.

I’ll go into all these highlights below, before leaving you with some plans for 2026.

Our biggest release yet

In November we released Hanami 2.3. This was our first major release in a year, and it turned out to be our biggest release yet, with 32 different contributors choosing to make Hanami better. Hanami 2.3 introduced Rack 3 support, resource routing, improved media type handling, along with a wide range of DX improvements. We’d love for you to give it a try!

Our ecosystem came together

Our maintainers this year have been taking care of Dry and Rom in addition to Hanami. We’ve been working towards bringing these projects together under a single banner. As part of this, we’ve chosen a new overall project name, and have been developing a new website and unified branding. Together, these will reintroduce us to the Ruby world and give our users an easier time learning our tools. We plan to launch these in February, but in the meantime, you can check out the source code and the in-progress live site (our guides are already looking particularly fine).

Our team grew again

This year we welcomed nine new people to our maintainers team:

These joined our existing team members, who have continued to work over the last year:

Thank you to all these beautiful people for giving their time to Hanami and for improving our part of the Ruby world!

All up, our maintainers team is now 17 strong. This feels like a good foundation for us to step up and do even better work next year. If you’d like to get involved, we recommend helping to triage issues and evaluate pull requests.

Our community shone through

Our community took things to a new level this year:

We launched our Discord and saw it bring more community activity than ever before.
We saw the launch of several new open source Hanami apps, including Princeton University Library’s orcid_princeton_hanami, which is also running in production! Huge props to Carolyn Cole for driving that project and sharing her thoughts on the process. We also saw the release of Pat Allan’s Playsmith, Ryan Bigg’s Twist v3, and our very own upcoming website. Meanwhile, Paweł continues to keep Palaver up to date as one of the most complete example apps out there.
Edouard launched the new (commercial) Catalogue Studio, after leaving us a brilliant trail of “Tips and notes about [his] journey” from Hanami 1.3 to 2.2.
Andrea Fomera arrived on the scene with a meteorological level of energy. She contributed some key pieces to Hanami 2.3, and also created hanami-omakase as a proving ground for Rails-alike features.
Ryan Bigg pointed his big blogging brain our way and penned his “Hanami for Rails developers” series. With Ryan now on the team, we’re looking forward to creating our very own “for Rails devs” guides in the future!
Andrew Nesbitt shipped hanami-sprockets, an alternative asset bundler and proving ground for the pluggable bundlers we’d like to ship next year.
Andrew also helped us get our new awesome-hanakai repo off the ground. There’s still a bit of tidying to do, but it exists, and that’s the important thing. If you have something awesome, now you know where to put it!
Did I mention our Hanami 2.3 release saw input from 32 different contributors? This is amazing! Thanks in particular to Wout and Armin for multiple helpful contributions across the year.
Starting in August, I’ve also been sharing my weeknotes covering Hanami development. I hope you find them helpful!

Our community is the most important thing to us. To reflect this, this year we made our community values clearer than ever, and placed them front and centre on our website:

We want the Hanami community to be a welcoming place for people who bring kindness, curiosity, and care. A place where people of all backgrounds and experience levels can feel respected, and can share and grow. A place for people to be proud of, and feel safe within.

We do not tolerate nazis, transphobes, racists, or any kind of bigotry. See our code of conduct for more.

We also adopted the Contributor Covenant 3.0, which brings a more approachable text for our worldwide community, and places a helpful emphasis on restorative justice.

I believe our values have played a big part in the health and growth of our community this year. Thank you to everyone for building a space we can all enjoy!

We went out into the world

Once again, we took ourselves to some conferences!

Tim visited beautiful Riga, Latvia for Baltic Ruby, where he presented a new Murakami-themed introduction to Hanami, and thoughts on the importance of a diverse Ruby ecosystem. He also ran a hack session, where Ismael Celis used his sourced toolkit to create the world’s first event-sourced calculator built on Hanami, and Krzysztof worked on the db rollback command for Hanami 2.3. Thank you to Baltic Ruby for the invitation!
Sean attended Rocky Mountain Ruby in Boulder, Colorado, and spoke on Slicing and Dicing through Complexity with Hanami. He also got to spend some quality time with some #HanamiFriends new and old!
Tim was lucky enough to reprise his talk at both XO Ruby San Diego and thoughtbot Open Summit. Thanks to XO organiser Jim Remsik, the San Diego talk was streamed to the internet, and the Open Summit was a native online event. We saw a good-sized group come together for each one, and I’m really glad I could share Hanami in such an open way. Thank you to Jim and thoughtbot for making these happen!

We launched our sponsorship program

This year we launched our first ever sponsorship program for Hanami, Dry and Rom. These are big and ambitious projects, and they need consistent attention for them to grow. Thanks to the support of the Ruby community, we made this happen! Since February this year, I’ve been able to commit a full business day every week towards the stewardship of our projects.

This could not have happened without our founding patrons. Thank you to Sidekiq, Brandon Weaver, Honeybadger, FastRuby, and AppSignal for your support! Your courage and belief is what got this thing off the ground in the first place.

Thank you also to all the individuals who are supporting us through GitHub sponsors. There are 20 of you right now! There’s real power in numbers, and your support takes us further than we could go alone.

We’ll run another sponsorship drive toward the middle of next year, but we are ready to accept your support at any time! See our sponsorship site to learn more. A few more businesses, or growing from 20 to 40 individual supporters, would make a huge difference to our project. And as you can see from everything in this post, your support goes a long way.

We have also ceased our relationship with Ruby Central as a fiscal host, following their removal of the Bundler and RubyGems.org maintainer teams from those projects, and their conduct thereafter. We stand with every maintainer.

Looking forward to next year

Just like last year, we have some goals we want to pursue across 2026:

Establish a twice-a-year release cycle for Hanami. Right now we’re aiming for May and November.
Finish unifying our ecosystem. We’ll launch our new site, finish rolling out our repo sync and release automation, then look at merging our forums.
Prepare the future for Dry and Rom. We want to reinvigorate these gems and make things easier for new contributors. This means triaging issues, bringing on focused maintainers, and developing roadmaps for the next phase of these projects.
Enter a successful second year of funded maintenance. Year one proved we could do this. Year two will show us whether we can sustain it. We’re looking forward to your support!

We’ll share more on each of these as we work through the year.

In the meantime, that’s it from us for 2025. Thank you to everyone who contributed to a wonderful year of improvements. We’re looking forward to continuing the work!

Hanami 2.3: Racked and Ready

2025-11-12T13:00:00+00:00

Today we are excited to announce Hanami 2.3! With this release, we unlock Rack 3, introduce resource routes, and deliver dozens of quality-of-life improvements that make building with Hanami smoother than ever.

Built for Rack 3

We are excited to bring Rack 3 support to Hanami! We now support both versions 2 and 3, so you can use whichever version of Rack suits your situation. We encourage you to upgrade Rack when you can, and we’re happy that Hanami can help you on this path.

When you upgrade to Rack 3, check out the Rack 3 upgrade guide. Hanami already handles the essential changes for you, but you may need to update your app code if you’re working with Rack request/response details.

Streamlined from route to response

More than just Rack, we’ve refined all aspects of our routing and request handling layer. The biggest change is the return of resource-based routing.

To set up RESTful routes, you’d previously add the following lines:

# Previously...
get "/books", to: "books.index", as: :books
get "/books/:id", to: "books.show", as: :book
get "/books/new", to: "books.new", as: :new_book
post "/books", to: "books.create"
get "/books/:id/edit", to: "books.edit", as: :edit_book
patch "/books/:id", to: "books.update"
delete "/books/:id", to: "books.destroy"

Now, all you need is one:

# Now! 🥰
resources :books

Resource routing is integrated with every aspect of routing. Resources can be customized, nested, and combined with scopes and ordinary routes. Learn more here.

The improvements don’t stop there! With this release:

Route scopes can be given custom name prefixes.
Routes can be named with a prefix that precedes scope prefixes.
Router runtime performance is considerably improved for large numbers of routes.
Multipart form and JSON request bodies are parsed by default.
Action format and media type config is clearer and more flexible.
You can access your subdomains via Request#subdomains, and configure your TLD length.
When you add 'nonce' to your content security policy, nonces are automatically added to script and stylesheet tags.
CSRF tokens are loaded from the X-CSRF-Token header in addition to request params.

DX in the details

We’ve also improved many more of your day-to-day interactions with Hanami:

hanami new now initializes a Git repository for new apps. You can also provide --skip-view to skip the view layer, as well as --gem-source, so you can use gem.coop from the get-go.
New apps get a helpful bin/setup script, as well as an improved README with a handy list of first steps.
New apps also receive a bin/hanami binstub, so you can invoke bin/hanami without requiring a bundle exec.
Run hanami db rollback to easily rollback a database migration.
Add your own methods to hanami console via your own modules: add config.console.include MyModule in your app class.
Prefer Pry to IRB? Make it the default with config.console.engine = :pry.
The console now prints a one-time warning when you access the keys for an un-booted app or slice. You can also chose to boot your app preemptively with hanami console --boot.
The default Rakefile will automatically load custom tasks from lib/tasks/.
View context classes are generated by default, so you can more easily see where to put custom view logic.
Run hanami generate command within a slice directory and the generated file will target that slice automatically.

We’ve made dozens more small improvements and fixes. Check out the changelogs to learn more.

Try Hanami 2.3

There’s never been a better time to try Hanami. For this release we’ve made our getting started guide more concise and easier to follow. Now you can get up and running faster than ever!

Why don’t you give it a try? Your first Hanami app is just a few commands away:

$ gem install hanami
$ hanami new my_app
$ cd my_app
$ bin/hanami dev
$ open http://localhost:2300

We’d love to hear how you go! Come join our Discord or forum and share your experience with our lovely community.

And if you’re a certified legend already rocking a Hanami app, make sure to check out the upgrade notes for 2.3.

Thank you to our contributors!

Hanami 2.3 is a significant release: it comes courtesy of our biggest contributors group yet. Thank you to all these wonderful humans!

There’s always room for more. Our community is inclusive and welcoming, and we’d love to have you join us.

Thank you to our patrons!

This is also our first major release since launching our sponsorship program. I’d like to extend my deepest thanks to our founding patrons: Sidekiq, Brandon Weaver, Honeybadger, FastRuby.io and AppSignal. Without you, this release wouldn’t have been possible.

Thank you also to the individuals supporting Hanami through our GitHub Sponsors. There are now 21 of you!

We’d love for you to become a patron too. Learn more here.

Announcing Hanami 2.3 beta2

2025-10-17T09:30:00+00:00

Two weeks after beta1, it’s time for 2.3 beta2!

This will be our last beta, and we’re aiming for the full 2.3 release in two weeks. Read on to see what’s new.

`hanami run` command

You can now can run your own scripts and code snippets with the hanami run command!

$ bundle exec hanami run my_script.rb
$ bundle exec hanami run 'Hanami.app["repos.commit_repo"].all.count'

Improved action formats config

Our previous approach to action formats config (config.formats in action classes or config.actions.formats in app or slice classes) made it too hard to configure and use your own custom formats. We’ve now overhauled this config and made it much more flexible.

This is an important change and we’d love your help with testing. If you configure formats for your actions, please pull down this beta and give this a go!

Use config.formats.register to register a new format and its media types.

This replaces config.formats.add. Unlike .add, it does not activate the format as “accepted” at the same time. This makes it easier to register your custom formats in app config or a base action class, while maintaining control over where you apply your format restrictions.

A simple registration looks like this:

config.formats.register(:json, "application/json")

.register also allows you to register one or more media types for the different stages of request processing:

Provide accept_types: to accept requests based on specific Accept types in request headers.
Provide content_types: to accept requests based on specific Content-Type request headers.
Both the above are are optional. If you do not provide these, then the format’s default media type (the required second argument) is used for each.
This default media type is also set as the default Content-Type response header when requests match that format.

Together, these allow you to register a format like this:

config.formats.register(
  :jsonapi,
  "application/vnd.api+json",
  accept_types: ["application/vnd.api+json", "application/json"],
  content_types: ["application/vnd.api+json", "application/json"],
)

Use config.formats.accept to accept specific formats from an action.

formats.accept replaces Action.format and config.format. You can access your accepted formats via formats.accepted, which replaces config.formats.values.

To accept a format:

config.formats.accept :html, :json
config.formats.accepted # => [:html, :json]

config.formats.accept :csv # Accepted formats are additive
config.formats.accepted # => [:html, :json, :csv]

The first format you give to accept will also become the default format for responses from your action, but only if you haven’t already configured a default using the approach below.

Use config.formats.default=` to set an action’s default format.

This is a new capability. Assign an action’s default format using config.formats.default=.

The default format is used to set the response Content-Type header when the request does not specify a format via Accept.

config.formats.accept :html, :json

# When no default is already set, the first accepted format becomes default
config.formats.default # => :html

# But you can now configure this directly
config.formats.default = :json

Previous format config methods are deprecated.

The previous format config methods (Action.format, config.format, config.formats.add, config.formats.values, and config.formats.values=) continue to work, but are now deprecated and will be removed in Hanami 2.4.

Switching to the methods above should be straightforward, and they give you significantly more flexibility. We hope you give them a go!

Thank you to our patrons

Thank you to our Hanami patrons who made this release possible! That’s Sidekiq, Brandon Weaver, Honeybadger, FastRuby.io and AppSignal.

Thank you also to all the community members supporting Hanami through our GitHub Sponsors. There are now more than 20 of you!

We’d love for you to become a patron too. Learn more here.

Improvements & fixes

We’ve got even more improvements and fixes in this release:

The router sees a big runtime performance boost for large numbers of routes, addressing a performance regression that was introduced as part of some fixes in Hanami 2.2.
hanami generate action now accepts a --skip-tests flag.
hanami generate action will add routes to slice-specific config/routes.rb files, if present.
hanami generate commands now graceully handle names given with mixed cases.
In new apps, the Types module now uses Dry.Types(default: :strict).
In new apps, the generated Guardfile now passes the environment from ENV["HANAMI_ENV"].
The view context no longer includes "settings" as a default dependency. You can include this yourself if you need it.
Errors for missing actions in routes now show friendlier, relative file paths.

With this release, we’ve also dropped support for Ruby 3.1. Hanami 2.3 will require Ruby 3.2 or later.

We need your help!

We need your help with testing! In addition to the new action formats config, we’re still keen for feedback from people navigating the upgrade to Rack 3, which we enabled as part of beta1.

If you have a Hanami app, please try upgrading to 2.3.0.beta2, adopting Rack 3, and improving your action formats. We’d love to hear how you go!

How can I try it?

> gem install hanami --pre
> hanami new my_app
> cd my_app
> bundle exec hanami dev

What’s included?

Today we’re releasing the following:

hanami v2.3.0.beta2
hanami-assets v2.3.0-beta.2 (npm package)
hanami-assets v2.3.0.beta2
hanami-cli v2.3.0.beta2
hanami-controller v2.3.0.beta2
hanami-db v2.3.0.beta2
hanami-reloader v2.3.0.beta2
hanami-router v2.3.0.beta2
hanami-rspec v2.3.0.beta2
hanami-utils v2.3.0.beta2
hanami-validations v2.3.0.beta2
hanami-view v2.3.0.beta2
hanami-webconsole v2.3.0.beta2

For the full list of changes, please see each package’s own CHANGELOG.

What’s next?

We have a short list of remaining fixes and improvements to make before our proper 2.3 release. See this GitHub project for details.

We expect to be back with 2.3 in a couple of weeks.

Thank you to our contributors!

Thank you to all these amazing people who contributed to this release!

And thank you again for giving this beta a try! We’re looking forward to hearing your feedback.

Announcing Hanami 2.3 beta1

2025-10-03T08:20:00+00:00

After getting set up for sponsorship (we still want to hear from you!), we’re back with a new Hanami release. Today we’re pleased to announce the first beta of Hanami 2.3.

Rack 3 support

This one goes up to ~~eleven~~ three.

With this release, we introduce Rack 3 support to Hanami!

We now support Rack versions 2 and 3, so you can use whichever version suits your situation. We still encourage you to upgrade Rack when you can, and we’re happy that Hanami is no longer a blocker on this path.

To upgrade your app to Rack 3, update your Hanami gems to this beta release, then bundle update rack. You should also check out the Rack 3 upgrade guide. Most changes will be handled for you by the Hanami gems, but you may need to update some of your app code if you’re dealing with lower-level request/response details.

Thank you to our patrons

This is a our first release since launching our sponsorship program. I’d like to extend a very warm thank you to the patrons who made this possible: Sidekiq, Brandon Weaver, Honeybadger, FastRuby.io and AppSignal.

Thank you also to all the community members supporting Hanami through our GitHub Sponsors. There are now 20 of you!

Improvements

This beta also brings a range of nice improvements to your Hanami experience:

Add your own methods to hanami console via own modules. Add config.console.include MyModule, AnotherModule to your app class.
Prefer Pry to IRB? Make it the default with config.console.engine = :pry.
When you specify 'nonce' in your content security policy, a nonce is automatically added to javascript_tag and stylesheet_tag.
Access subdomains using Request#subdomains, and configure your default TLD length with config.actions.default_tld_length.
Redirect to absolute URLs in route definitions: redirect '/example', to: https://example.com, code: 302
You can now use single-character slice names.
Run any hanami generate command inside a slice directory and the slice will automatically be used as the target for the new files.
Run hanami db rollback to easily rollback a database migration.
Running hanami new will now initialize a Git repository in your new app.
Run hanami new with --skip-view to skip generating the view layer.
The default Rakefile will automatically load custom tasks from the conventional lib/tasks/ location.
The README.md in newly generated apps now includes some helpful instructions for next steps.

Fixes

We’ve also fixed a bunch of bugs:

Allow access to autoloaded constants in config/routes.rb.
Support include Deps in repo classes.
Avoid false negatives for content type matches in actions.
Properly show database errors arising from hanami db commands.
Skip ENV var processing by Foreman (run via hanami dev by default) to ensure consistent ENV loading across environemnts.
Respect app inflections when running hanami generate commands.
Prevent generate commands from overwriting files.
Convert special characters to underscores in route helper names.
Include all necessary gems when running hanami new with the --head option.

We need your help!

Our Rack 3 upgrade is one of the more intricate changes we’ve made, especially considering the broad ecosystem that depends on Rack. We need your help to make sure this goes smoothly!

If you have a Hanami app, please try upgrading to 2.3.0.beta1 and Rack 3, and let us know how you go!

How can I try it?

> gem install hanami --pre
> hanami new my_app
> cd my_app
> bundle exec hanami dev

What’s included?

Today we’re releasing the following:

hanami v2.3.0.beta1
hanami-assets v2.3.0-beta.1 (npm package)
hanami-assets v2.3.0.beta1
hanami-cli v2.3.0.beta1
hanami-controller v2.3.0.beta1
hanami-db v2.3.0.beta1
hanami-reloader v2.3.0.beta1
hanami-router v2.3.0.beta1
hanami-rspec v2.3.0.beta1
hanami-utils v2.3.0.beta1
hanami-validations v2.3.0.beta1
hanami-view v2.3.0.beta1
hanami-webconsole v2.3.0.beta1

For the full list of changes, please see each package’s own CHANGELOG.

What’s next?

We have a short list of remaining fixes and improvements to make before a proper 2.3 release. See this GitHub project for details.

I anticipate we’ll do one more beta release, followed by the final 2.3 release.

Thank you to our contributors!

Thank you to all these amazing people who contributed to this release!

And thank you again for giving this beta a try! We’re looking forward to hearing your feedback.

Hanami adopts Contributor Covenant 3.0

2025-09-02T08:30:00+00:00

Our community is the most precious part of Hanami. When you pick up Hanami, we want to make sure you have a great time. This is why we place our community values front and centre on our home page:

We want the Hanami community to be a welcoming place for people who bring kindness, curiosity, and care. A place where people of all backgrounds and experience levels can feel respected, and can share and grow. A place for people to be proud of, and feel safe within.

It’s also why we govern our community spaces under the Contributor Covenant code of conduct. This is the gold standard for community codes of conduct, and it’s served us well for over ten years.

Today we’re delighted to adopt the new Contributor Covenant 3.0, released just last month. This new version brings a number of improvements:

Contributor Covenant 3.0 is designed to be more adaptable to different kinds of communities, both online and offline. It is written with clearer, less US-centric language, intended to be easier to understand and translate. The enforcement guidelines section has been reimagined as “Addressing and Repairing Harm,” reflecting an alignment with principles of restorative justice, including finding ways to safely reintegrate someone back into a community after an incident occurs.

We’re pleased that this new version is more approachable for our worldwide community. We also welcome the focus on restorative justice. The examples of how people can make genuine amends to grow and rejoin a community are clear and well explained.

These changes won’t affect how we interact day-to-day in our already lovely community, but do give us better tools for the rare times when conflicts need thoughtful resolution.

Thank you to the Organization for Ethical Source for their work on this new version!

You can find our instance of the Contributor Covenant on our community page.

Wrapping up our sponsorship drive

2025-08-27T11:45:00+00:00

After six posts (the announcement, our founding patrons, a field report, meeting Tim and Sean, the Rails elephant in the room, and a cuteness preview), it’s time to wrap up our sponsorship drive for 2025.

How’d we go?

Thanks to your support, we’ve entered a whole new era for Hanami, Dry and Rom. For the first time ever, Ruby has a second framework backed by funding!

Granted, we’re at only 0.2 of a full-time role, but a start is a start! We’re here for the long haul, and going from 0 to something is one of the most important jumps we will make.

We have you—the Ruby community—to thank for this.

Thank you especially to Mike Perham and Sidekiq, Brandon Weaver, Joshua Wood and Honeybadger, Ernesto Tagwerker and FastRuby, and Roy Tomeij and AppSignal.

These are our founding patrons, and without their support, this whole thing would never have got off the ground. They’ve committed $26k towards our first year of paid maintenance.

These people are visionaries, going out of their way to support a brighter, better Ruby. Just look at how Brandon describes it:

In Ruby diversity is our greatest strength, whether that be the people, the ideas, or the technologies we use. Ruby is not just one framework, nor is it just one person, it is a community of passionate people pushing the boundaries of what’s possible not just as individuals, but as a collective. I am happy to continue to fund efforts building upon that vision of the future.

Who wouldn’t want this for Ruby? We’re doing everything we can to make this real.

We’ve also been buoyed by new support from fellow community members. We’ve been delighted to welcome 15 new community patrons via our GitHub Sponsors. These are individuals who’re putting their own money towards Hanami, and together they’re contributing $260/month. Thank you!

We’ve also established a partnership with Ruby Central as our fiscal host. Ruby Central gives us a very attractive fee structure (5% vs the 10% that Open Collective charges) and they have already handled the funds for most of our business patrons. This means more of your money goes directly to our work on tools for Rubyists.

Ruby Central went out of their way to set this up for us, and I couldn’t think of a better partner for this. We share the same vision for Ruby’s future, and I’m excited to collaborate with them for many years to come!

After all of this, how did we go? We’ve raised $29k (so far!). This is short of our initial $40k target, but fortunately, it’s still enough to support me at 1 day/week for this first year of paid maintenance.

We’re ready. Are you?

While our sponsorship drive may be coming to an end, we’re ready to bring in new supporters at any time.

Does your business already depend on our gear? (I’m sure there are a lot of you out there, with our billion gem downloads and counting across Hanami, Dry and Rom). Or do you want to step up and count yourself among the brave few willing to forge a healthier, kinder future for Ruby? If so, then come talk to us!

What’s next?

Establishing our sponsorship was one of our most important goals for 2025, and I’m very happy we’ve managed to get that done. While it did take a lot of time and brain space, we’ve still managed several other initiatives:

Upcoming release:

Moving towards a Hanami 2.3 release. Rack 3 support will be the centrepiece here, but this will bring in a range of small improvements and fixes too.

Brand and community:

Preparing new branding for our projects, along with a way to bring them together as a unified family. You’ve seen a preview of this already!
Building our brand new website, which will provide a one-stop shop for everything Hanami, Dry and Rom. Guides, docs, news, community info and more.

Project maintenance:

Catching up on housekeeping. First order of business is rolling out a tool to keep our 50+ GitHub repos in sync.
Working on new contributor guidelines that will make it clear how you can become a maintainer, and empower our existing maintainers to take our gems to the next level.

One more thing:

Personally, I’ve (finally!) found some time to work on my open source Hanami example app, Decaf Sucks. My current focus is adding streamlined Rodauth integration, something that feels completely “Hanami-native” and can serve as the foundation for an eventual rodauth-hanami gem.

With sponsorships in place, I can’t wait to bring you all of the above!

Exciting stuff is on the way. If you want to help out or follow along, come say hi in chat or our forum!

Hanakai

Hanami 3.0: In full bloom

First-class mailers

Built-in internationalization

Now with Minitest

Faster by default

Clearer, more useful logs

Smoother asset watching

Body parsing comes to Hanami Action

Simpler views with undecorated exposures

A cleaner foundation

And much more!

Try it out

Upgrading from 2.3

Thank you to our contributors!

Thank you to our sponsors!

Help us test the Hanami 3.0 release candidate

What’s coming in 3.0

Built-in i18n

First-class mailers

Minitest support

Memoized components

Improved logging

Smoother asset watching

Other changes

Upgrading an existing app

Try it out

Tell us how you go!

Welcome, SerpApi!

Welcome to Hanakai

A new look for our family

A new home on the web

What’s next

Join us

State of Hanami, December 2025

Our biggest release yet

Our ecosystem came together

Our team grew again

Our community shone through

We went out into the world

We launched our sponsorship program

Looking forward to next year

Hanami 2.3: Racked and Ready

Built for Rack 3

Streamlined from route to response

DX in the details

Try Hanami 2.3

Thank you to our contributors!

Thank you to our patrons!

Announcing Hanami 2.3 beta2

hanami run command

Improved action formats config

Thank you to our patrons

Improvements & fixes

We need your help!

How can I try it?

What’s included?

What’s next?

Thank you to our contributors!

Announcing Hanami 2.3 beta1

Rack 3 support

Thank you to our patrons

Improvements

Fixes

We need your help!

How can I try it?

What’s included?

What’s next?

Thank you to our contributors!

Hanami adopts Contributor Covenant 3.0

Wrapping up our sponsorship drive

How’d we go?

We’re ready. Are you?

What’s next?

`hanami run` command