VaahCMS is an MIT-licensed, Laravel-based open-source web application development platform shipped with a headless content management system, built for teams that want to develop applications and manage content inside one codebase rather than stitching a CMS and a Laravel project together.

What it is

VaahCMS is an open-source web application development platform that ships with a headless CMS. It is built with Laravel, Vue, Pinia, and PrimeVue, and it follows the Hierarchical Model View Controller (HMVC) architectural pattern. That pattern is the organising idea of the project: the platform supports multiple Modules and Themes, and each module or theme can be structured on its own, with its own frontend code, instead of being flattened into a single application tree. Its stated purpose is to develop enterprise-level software applications that remain manageable, extendable, flexible, upgradable, and maintainable over the long run.

The concrete problem it solves is the split developers hit on nearly every project: a CMS is used to build the website and Laravel is used for application development, and the two have to be reconciled. VaahCMS places the content management capability inside the Laravel application itself, so the CMS does not sit in the way of the application code. The project describes its CMS Module as inspired by the simplicity of WordPress, while the surrounding platform remains an application development framework rather than a publishing tool. It lives in the PHP and Laravel ecosystem.

Key capabilities

• Hierarchical Model View Controller (HMVC) architecture with structured, co-existing Modules and Themes.
• Each module and theme can be isolated as its own Vue or React application.
• Modules and themes can also be set up with blade file support alone, without a separate frontend JavaScript library.
• A headless CMS with a built-in API, so any frontend framework such as Nuxt or Next can be attached to it.
• A CMS Module modelled on the simplicity of WordPress.
• A frontend stack of Laravel, Vue, Pinia, and PrimeVue, with Bulma and Buefy listed among the project topics.
• Installation driven by the npx command cms:install.

Who uses it and how

• Teams building enterprise-level applications that also need content management, where the platform's Module and Theme structure carries the application across a long maintenance life.
• Developers who currently reach for a CMS for the website and Laravel for the application on the same project, and want one platform instead of two.
• Frontend developers working headless: the built-in API is designed to plug into a Nuxt or Next frontend while the CMS stays in Laravel.
• Content-heavy applications and single-page or JavaScript-driven applications, since each module and theme can carry its own isolated Vue or React app.
• Contributors and integrators around the project, including documentation work on the vaah-docs repository and discussion in the project's Slack community.

Getting started

Run the quick start command npx vaah cms:install. Documentation for the current line lives at docs.vaah.dev/vaahcms-2/.

How it compares

The facts do not provide a list of paid products VaahCMS replaces, so the honest placement is among the tools it names. Its CMS Module is explicitly inspired by the simplicity of WordPress, while the platform around it is an application development framework in the Laravel ecosystem, and its headless API is meant to pair with frontends such as Nuxt or Next. It therefore sits between a conventional CMS and a Laravel application skeleton rather than fully in either camp.

When to use it — and when not to

A self-hoster takes on a Laravel application plus the Node-based npx tooling used for installation, and the README does not spell out the database, storage, or mail services that must be provisioned around that application, so those questions need answering before adoption. The project is small — 573 stars, 25 forks, and 8 open issues — and it is actively seeking contributors for its documentation, which suggests that support and documentation depth should be weighed against the platform's ambition. It is a poor fit for anyone who wants a hosted, content-first CMS with no application framework underneath; the licence is unambiguous, MIT, but the project's centre of gravity is application development, not publishing.

npx vaah cms:install