Weave Code
Vaahcms Laravel Package
webreinvent/vaahcms
VaahCMS is an open-source modular CMS built on Laravel. It provides a ready-made admin panel, CRUD generator, module and theme management, role-based permissions, APIs, and media tools to help teams launch and manage web applications faster.
VaahCMS is a laravel based open-source web application development platform shipped with a headless content management system (CMS).
Frequently asked questions about Vaahcms
- How do I install VaahCMS with Composer?
- VaahCMS is installed via Composer into a Laravel application, either a fresh install or an existing one. In practice it works best when you treat it as the application base rather than dropping it into an arbitrary Laravel codebase. After installing, run the setup and migrations, then verify that Vaah's route prefixes and config keys do not collide with your existing namespaces. A short spike that models two or three real content types and exposes them over the API is the cheapest way to confirm fit.
- Which Laravel and PHP versions does VaahCMS support?
- VaahCMS is Laravel-native and targets PHP 8.x on a Laravel-centric stack, typically MySQL or MariaDB and optionally Redis. Read the exact Laravel minor-version pin and PHP version matrix from the package's composer.json and CI configuration before you commit, since Vaah follows its own release cadence. Cross-check the supported Laravel versions against your upgrade plans, because running on an unsupported framework minor is the fastest way to inherit security debt.
- Can I add VaahCMS to an existing Laravel application?
- Yes, it is installable via Composer into an existing Laravel app, but the realistic integration path is to make Vaah the application skeleton and layer your domain code as Vaah modules or adjacent Laravel packages. Because it ships opinionated module, theme, and extension conventions, integration is closer to adoption than composition. Budget time for route, service-provider, and namespace collisions, and draw a clear boundary between Vaah-managed content and application-owned domain logic.
- Is VaahCMS a headless CMS or a traditional CMS?
- VaahCMS is a Laravel-based platform shipped with a headless CMS, so content is delivered through APIs to decoupled consumers such as SPAs, mobile apps, and edge-rendered frontends. Content operations run in a separate Vue-based admin SPA, which keeps editorial tooling apart from presentation concerns. That makes it a good fit when your delivery tier is Next.js, Nuxt, SvelteKit, or a mobile client rather than Blade templates.
- How does authentication work for headless VaahCMS API consumers?
- VaahCMS ships role-based permissions and an API layer, but its auth model and RBAC granularity are Vaah conventions rather than Laravel defaults. Before designing your frontend, confirm in the docs whether headless consumers authenticate via Sanctum, Passport, or API keys, and how scopes map to roles. Also check pagination, filtering, and API versioning conventions, since these are package-defined rather than inherited automatically.
- Does VaahCMS support multi-tenancy, localization, and content versioning?
- Treat these capabilities as open questions rather than guaranteed core features. Multi-tenancy, localization, content versioning, and editorial workflow may be core, bolt-ons, or module-level work depending on the release you pin. Verify each one in the documentation and prototype the ones that matter during your spike before assuming they ship out of the box.
- Does VaahCMS lock me into its module and theme system?
- Yes, to a meaningful degree. Custom modules and content schemas are Vaah-defined, which means they are portable in principle but costly in practice if you later move to plain Laravel or another CMS. Price that exit cost into the decision up front, and confirm backward-compatibility guarantees for custom modules across releases with the maintainers before building heavily on them.
- How does VaahCMS compare to Strapi, Directus, or Statamic?
- VaahCMS is strongest when your host stack is already Laravel and PHP-centric and your delivery tier is decoupled, because it avoids standing up a second runtime. If your platform is Node, .NET, or Go and content is the only reason to run PHP, evaluate Directus, Strapi, or a managed headless CMS first. Statamic is the closer comparison for Laravel teams that want a more conventional, file-and-Eloquent-driven CMS experience.
- Is VaahCMS actively maintained and safe to use in production?
- VaahCMS has a recent release and a stable codebase, but the ecosystem is small at roughly 573 GitHub stars and stewardship is single-vendor through WebReinvent. That combination signals a stable but not high-momentum project, which is reasonable for an infrastructure bet and weaker for a grow-with-the-ecosystem bet. Before production, review CVE history and the disclosure process, admin auth hardening, upload handling, and the real test coverage and release cadence behind the current release.
- How should I migrate existing content into VaahCMS?
- Model content before you migrate it: inventory existing types, taxonomies, media, redirects, and URL structure, then map them to Vaah content types and modules. Export from the incumbent CMS into a staging Vaah instance and validate with API fixtures and golden-file comparisons rather than visual QA alone. Plan a parallel-run window where legacy and Vaah both serve read traffic behind an edge router or feature flag, so rollback is a routing change instead of a data restore.
Weaver
How can I help you explore Laravel packages today?