Replace WordPress
Usually bolted onto a product as a second application, a second stack and a second set of security updates.
Why teams move off WordPress
WordPress bolted onto a Rails app is a second stack, a second host and a second security surface — for the ability to edit a paragraph.
What you give up
The plugin ecosystem, which is both the reason to use it and the reason not to.
This directory says so when an engine only covers part of the job. A replacement that needs a caveat is still worth knowing about — it just should not surprise you in week three.
3 Rails engines that replace WordPress
-
ActiveCanvas
Drop-in replacement ContentThe 'marketing needs to edit pages' job, without a second application to host and patch.
WordPress → active_canvas
No ratings yet → -
Spina CMS
Drop-in replacement ContentPage editing for marketing, without a second stack.
WordPress → spina
No ratings yet → -
Alchemy CMS
Drop-in replacement ContentA full editorial CMS for a Rails site.
WordPress → alchemy_cms
No ratings yet →
Questions
- Is there an open-source alternative to WordPress for Rails?
- Yes — ActiveCanvas, Spina CMS, and Alchemy CMS. They all mount into an application you already run, so there is no second deployment and no second database.
- What do I give up by replacing WordPress?
- The plugin ecosystem, which is both the reason to use it and the reason not to.
- How do I replace WordPress in a Rails app?
- Add active_canvas to your Gemfile, mount it in config/routes.rb at /canvas, and run its migrations. The whole integration is two lines and a migration.
- How much does replacing WordPress save?
- WordPress is priced free; managed hosting from $25/mo. The engines here are open source, so the cost becomes the time to mount one and the resources it uses inside your existing application.
Same category