<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/rails-is-done-bxobwivpz" -->

---
title: Rails is done | daily.dev
description: Lucas Dohmen announces Amiko, a community fork of Rails 8.x, motivated by DHH&#x27;s leadership and worldview being incompatible with an inclusive community. The...
canonical: https://daily.dev/posts/rails-is-done-bxobwivpz
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Rails is done | daily.dev
og:description: Lucas Dohmen announces Amiko, a community fork of Rails 8.x, motivated by DHH&#x27;s leadership and worldview being incompatible with an inclusive community. The...
og:url: https://daily.dev/posts/rails-is-done-bxobwivpz
og:image: https://api.daily.dev/og/posts/BxOBwiVPZ.png
og:image:alt: Rails is done
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Rails is done

**[RUBYLAND](https://daily.dev/sources/rubyla)** · 6 min read · 3 upvotes · 0 comments

## Summary

Lucas Dohmen announces Amiko, a community fork of Rails 8.x, motivated by DHH's leadership and worldview being incompatible with an inclusive community. The author argues that Rails core (railties, actionpack, activesupport, activemodel, activerecord, actionview) has been essentially feature-complete since Rails 6.0 in 2019, making a fork maintainable by a small team. Amiko's primary goal is to provide an LTS version of Rails 8.x maintained by a community that explicitly rejects bigotry. The fork aims for near-full compatibility with existing Rails 8.x apps, requiring only gem swaps and minor search-and-replace changes. The post also addresses why Amiko exists alongside Hanakai, positioning both as complementary alternatives in the Ruby ecosystem rather than competitors.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://lucas.dohmen.io/posts/2026/08/09/rails-is-done>

## Questions this post answers

### What is the Amiko project and why is it forking Ruby on Rails?

Amiko is a community-driven hard fork of Ruby on Rails core, started because a group of developers disagree with DHH's leadership and values and an earlier open letter asking the Rails core team to cut ties with him went unanswered. It targets only the core gems (railties, actionpack, activesupport, activemodel, activerecord, actionview), aiming to provide an LTS-style, compatible alternative to Rails 8.x that existing apps can adopt via a gem swap and search-and-replace, without tolerating bigotry within its community.

_Developers weighing whether to stick with Rails or move to a values-driven fork can track this story on daily.dev._

### Which parts of Ruby on Rails have not changed significantly since Rails 6.0?

The core gems generated by rails new --minimal — railties, actionpack, activesupport, activemodel, activerecord, and actionview — have seen no major changes since Rails 6.0 shipped the Zeitwerk autoloader in 2019, aside from ActiveRecord additions like at-work encryption, asynchronous query loading, some authentication methods, and composite primary keys, mostly added in Rails 6.1 in 2020. Everything else added since, like asset pipelines, deployment tools, and a reverse proxy, are optional add-on gems rather than core changes.

_Teams deciding how much churn to expect from a framework upgrade can follow Rails core stability discussions on daily.dev._

### How does the Amiko Rails fork differ from Hanakai (Hanami)?

Amiko is designed to stay compatible with existing Rails 8.x applications, letting developers switch gems and do minor search-and-replace changes to keep their current app running, rather than adopting a different framework design. Hanakai (built around Hanami) offers a fundamentally different architecture for those who want a clean break from Rails' design, so Amiko positions itself as the choice for teams who like Rails but reject its leadership, while Hanakai suits those wanting a different framework entirely.

_Developers comparing Ruby web framework forks before committing an existing codebase can weigh both options via daily.dev._

## Similar posts on daily.dev

- [Amiko: A desperate virtue signalling attempt](https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37) · RUBYLAND · 0 upvotes · 0 comments
- [Issue \#813: A new attempt to fork Rails — Ruby Weekly](https://daily.dev/posts/issue-813-a-new-attempt-to-fork-rails-ruby-weekly-kbcj0j5vw) · Ruby Weekly · 2 upvotes · 0 comments
- [Returning To Rails in 2026](https://daily.dev/posts/returning-to-rails-in-2026-ohsyin4ne) · Lobsters · 1 upvotes · 0 comments
- [Top Ruby Developers and RoR Experts You Should Know \(2026\)](https://daily.dev/posts/top-ruby-developers-and-ror-experts-you-should-know-2026--weup5tfek) · Ruby Flow · 1 upvotes · 0 comments
- [Bringing Rails into the Ractor-age](https://daily.dev/posts/bringing-rails-into-the-ractor-age-ea9pqilyv) · GitHub · 2 upvotes · 0 comments

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#ruby](https://daily.dev/tags/ruby), [#rails](https://daily.dev/tags/rails)

[View this post on daily.dev](https://daily.dev/posts/rails-is-done-bxobwivpz)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Rails is done","url":"https://daily.dev/posts/rails-is-done-bxobwivpz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/rails-is-done-bxobwivpz"},"datePublished":"2026-08-09T06:58:23.670Z","dateModified":"2026-09-14T06:05:25.500Z","description":"Lucas Dohmen announces Amiko, a community fork of Rails 8.x, motivated by DHH's leadership and worldview being incompatible with an inclusive community. The...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"RUBYLAND","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"RUBYLAND","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/rubyla","url":"https://daily.dev/sources/rubyla"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/rails-is-done-bxobwivpz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,ruby,rails","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"RUBYLAND","item":"https://daily.dev/sources/rubyla"},{"@type":"ListItem","position":3,"name":"Rails is done"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/rails-is-done-bxobwivpz#faq","mainEntity":[{"@type":"Question","name":"What is the Amiko project and why is it forking Ruby on Rails?","acceptedAnswer":{"@type":"Answer","text":"Amiko is a community-driven hard fork of Ruby on Rails core, started because a group of developers disagree with DHH's leadership and values and an earlier open letter asking the Rails core team to cut ties with him went unanswered. It targets only the core gems (railties, actionpack, activesupport, activemodel, activerecord, actionview), aiming to provide an LTS-style, compatible alternative to Rails 8.x that existing apps can adopt via a gem swap and search-and-replace, without tolerating bigotry within its community. Developers weighing whether to stick with Rails or move to a values-driven fork can track this story on daily.dev."}},{"@type":"Question","name":"Which parts of Ruby on Rails have not changed significantly since Rails 6.0?","acceptedAnswer":{"@type":"Answer","text":"The core gems generated by rails new --minimal — railties, actionpack, activesupport, activemodel, activerecord, and actionview — have seen no major changes since Rails 6.0 shipped the Zeitwerk autoloader in 2019, aside from ActiveRecord additions like at-work encryption, asynchronous query loading, some authentication methods, and composite primary keys, mostly added in Rails 6.1 in 2020. Everything else added since, like asset pipelines, deployment tools, and a reverse proxy, are optional add-on gems rather than core changes. Teams deciding how much churn to expect from a framework upgrade can follow Rails core stability discussions on daily.dev."}},{"@type":"Question","name":"How does the Amiko Rails fork differ from Hanakai (Hanami)?","acceptedAnswer":{"@type":"Answer","text":"Amiko is designed to stay compatible with existing Rails 8.x applications, letting developers switch gems and do minor search-and-replace changes to keep their current app running, rather than adopting a different framework design. Hanakai (built around Hanami) offers a fundamentally different architecture for those who want a clean break from Rails' design, so Amiko positions itself as the choice for teams who like Rails but reject its leadership, while Hanakai suits those wanting a different framework entirely. Developers comparing Ruby web framework forks before committing an existing codebase can weigh both options via daily.dev."}}]}
```

