Plum
Why Plum
Managed content should feel like a native capability of a Rails application.
Rails is excellent at building applications, but content management is still commonly assembled from bespoke admin screens or delegated to a remote service. Both choices create work that does not improve the final site.
Keep the application whole
Plum uses the host application's database, users, authorization, jobs, mail, storage, and deployment. Developers retain ordinary Ruby extension points while editors receive a focused place to work.
Start small without choosing a dead end
A content site can begin with Rails and SQLite on one VM. The same content model can live inside a larger PostgreSQL application when the project calls for it.
Own the result
Plum is open source and self-hosted. A site should remain portable as code, structured content, assets, and a documented backup—not as an account on somebody else's platform.