Open-Source CMS · AlchemyCMS

alchemy_cms

AlchemyCMS is an open-source Rails CMS engine supporting both traditional server-side rendering and headless architectures. It provides component-based content management with an admin interface, multi-language support, versioning, and RESTful API capabilities.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/AlchemyCMS/alchemy_cms

901

GitHub stars

321

Forks

Ruby

Primary language

BSD-3-Clause

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	AlchemyCMS/alchemy_cms
Owner	AlchemyCMS
Primary language	Ruby
License	BSD-3-Clause — OSI-approved
Stars	901
Forks	321
Open issues	12
Latest release	v8.3.2 (2026-06-30)
Last updated	2026-07-07
Source	https://github.com/AlchemyCMS/alchemy_cms

What alchemy_cms is

A Ruby on Rails engine (v8.3.2) built as a content management system with flexible templating, page versioning, user access control, image processing, and extensibility via Rails engines. Requires Rails ≥7.2, Ruby ≥3.1, SQL database, and ImageMagick. Integrates as a gem into existing Rails applications.

Quickstart

Get the alchemy_cms source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/AlchemyCMS/alchemy_cms.git2cd alchemy_cms3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-language, multi-domain Rails sites

Designed natively for managing content across multiple languages and domains with built-in URL handling and content versioning.

Component-based content management

Separates content from markup via flexible templating, ideal for organizations managing reusable content blocks across pages.

Headless CMS for decoupled frontends

RESTful API enables use as a content backend for frontend frameworks, SPAs, or mobile applications separate from Rails.

Implementation considerations

Current version (v8.3.2) requires Rails ≥7.2 and Ruby ≥3.1; multiple stable branches available for older frameworks.
Authentication uses Devise-based model (alchemy-devise gem) by default or integrates custom user models via role-based access control.
ImageMagick dependency required for on-the-fly image cropping and resizing; ensure availability in deployment environment.
Admin interface mounted at `/admin` by default; customizable via initializers for routing and authentication methods.
Development branch carries stability risk; production deployments should use stable branch (8.0-stable) or released gem version.

When to avoid it — and what to weigh

Non-Rails projects or no Ruby expertise — Tight coupling to Rails ecosystem; requires Rails ≥7.2 and Ruby ≥3.1. Not suitable for non-Rails or non-Ruby environments.
Zero server-side infrastructure — Requires a running Rails server, SQL database, and ImageMagick. Not a static site generator or edge-first solution.
Need for production hardening without review — Main branch noted as development branch potentially containing bugs. Stable production use requires 8.0-stable branch or current gem version.
Simple blog or lightweight content site — Full Rails CMS overhead may be unnecessary; lightweight alternatives or static generators might be more cost-effective.

License & commercial use

Licensed under BSD 3-Clause (New/Revised), a permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions. Requires retention of copyright and license notice.

BSD 3-Clause license permits commercial use and derivative works. No explicit commercial support, hosting, or warranty is stated in available data. Requires independent review of licensing implications for your use case and assessment of support options.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

Brakeman security scanning integrated in CI/CD. User access control and role-based permission system built-in. No known vulnerabilities, penetration test results, or security audit details provided. Production deployments should use stable branches. Requires standard Rails security practices (CSRF protection, SQL injection prevention via ORM, etc.). No independent security assessment available in provided data.

Alternatives to consider

Contentful / Strapi

Cloud-hosted or self-hosted headless CMS with broader language support and no Rails dependency; better for decoupled front-end architectures.

Statamic / Craft CMS

PHP-based CMS with comparable features; lighter deployment footprint and different ecosystem; no Rails lock-in.

WordPress with custom plugins

Wider hosting support, larger plugin ecosystem, lower entry barrier; trade-off is less developer control and different architecture philosophy.

Software development agency

Build on alchemy_cms with DEV.co software developers

Review the stable branch for production use, assess Rails ≥7.2 and Ruby ≥3.1 requirements, and test authentication integration with your existing user model before deployment.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

studiocms ujcms tinacms

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMS Web App Development API Development Cloud Deployment Talk to DEV.co

alchemy_cms FAQ

Can I use AlchemyCMS in a non-Rails project?

No. AlchemyCMS is a Rails engine; it requires a Rails application (≥7.2) and Ruby ≥3.1. It cannot be used outside the Rails ecosystem.

Is the main branch production-ready?

No. The main branch is explicitly noted as a development branch that may contain bugs. For production, use the current gem version from rubygems.org or the 8.0-stable branch.

What authentication does AlchemyCMS provide?

By default, it uses alchemy-devise (Devise-based user model). You can also integrate your own user model by defining an alchemy_roles method that returns admin/editor/author/member roles.

Can I use AlchemyCMS as a headless CMS?

Yes. It provides a RESTful API for headless deployments, enabling use as a content backend for front-end frameworks or mobile apps separate from the Rails app.

Software developers & web developers for hire

Need help beyond evaluating alchemy_cms? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source cms integrations — and maintain them long-term.

Evaluate AlchemyCMS for Your Rails Project

Review the stable branch for production use, assess Rails ≥7.2 and Ruby ≥3.1 requirements, and test authentication integration with your existing user model before deployment.

Talk to DEV.co Schedule a Consultation