PagibleAI adds content management to a Laravel application you already run. Install it with Composer, build the front end in Blade, and read content over GraphQL or a JSON:API. The AI tools are there when you want them and out of the way when you don't.
PagibleAI is a normal Composer package that runs on Laravel 11, 12 and 13. Add it, run the migrations, and that is the whole install. There are no extra services to host and nothing external to set up.
composer require aimeos/pagible
php artisan cms:install
php artisan migrate
A Lighthouse-based admin API. Read and write pages, elements, files, users and permissions straight from your own code.
A read-only REST endpoint for the front end. One request returns a full page together with its related elements and files.
The front end is plain Blade. Override any view, drop in your own components, and lay pages out the way you want.
Every model is a normal Eloquent model with UUIDs, soft deletes and the usual relationships, so you query and extend them like the rest of your app.
Package auto-discovery handles registration, so there is no service provider to wire up by hand.
It uses Laravel's own routing and authentication. The catch-all route and middleware are configurable when you need to change them.
GraphQL admin API. The admin API runs on Lighthouse and covers pages, elements, files, versions and user permissions. It is what the Vue admin panel talks to, and you can point your own tools at it to build a custom editor or to script content changes.
Every mutation goes through the same role checks as the panel, and each query returns only the fields you ask for. That makes it practical to feed content into a dashboard, a CI job or an AI agent without pulling back more than you need.
JSON:API for the front end. A read-only endpoint that follows the JSON:API spec. A single request gives you a page with its nested elements and file references, which suits SPAs, mobile apps and static site generators.
Because it sticks to the standard, the JSON:API client libraries you already know work against it in most languages. Responses are cached per page, so heavy traffic lands on the cache instead of the database.
Blade templates and themes. Pages render through Laravel's Blade engine. Publish the views and edit them, write a theme of your own, or assign a different theme per page. You keep full control of the markup.
There are themes to start from, including Clean, Paper, Glass and Premium, and you can package your own with templates for each content element. Switching a site's theme is one setting, with no build step and no front-end framework to run.
PagibleAI
OctoberCMS
Statamic
Draft, rewrite, retone or expand text with an LLM, right from the admin panel.
Generate images from a prompt, then remove backgrounds, inpaint, repaint, upscale or extend them without leaving the CMS.
Turn audio and video into text you can search and edit, using speech-to-text.
Translate pages and elements into any of 35+ languages in a single step.
An MCP server with 33 tools, so an assistant like Claude can run the CMS for you.
Suggested titles, meta descriptions and keywords for each page, written by the model.
PagibleAI works for a small blog and for a busy production site:
Each save writes an immutable snapshot, so you have a record of who changed what and when, and you can roll back to any of them.
Editors work on a draft while visitors keep seeing the last published version, so edits never touch the live site until you publish.
Give a page a date and time and it goes live on its own.
Edits broadcast over WebSockets with Laravel Reverb, so teammates see changes as they happen.
A three-way merge and an unsaved-changes guard combine simultaneous edits so nobody's work gets lost.
Put any two versions side by side and restore individual changes from one of them.
Several common protections are set up for you:
Define your own content element types, each with its own fields and Blade template, without touching core code.
Build a content block once and reference it on many pages. Edit it in one place and every page picks up the change.
Move a site over from WordPress with an Artisan command that brings across posts, pages, media and metadata.
Translations for 35+ languages, with the language versions of a page linked together.
Serve a different page tree per domain and run several sites from one Laravel application.
Licensed under LGPL-3.0, so you can use it in commercial work with no per-site fees and no lock-in.
Yes. It is a standard Composer package with auto-discovery. Run composer require, publish the config and migrate. Your existing routes, models and middleware stay as they are.
Laravel 11, 12 and 13. It tracks Laravel's release cycle and is tested against each supported version.
SQLite, MariaDB, MySQL, PostgreSQL and SQL Server. Full-text search works on each one using that database's own features.
Yes. Static state is handled so it stays correct under Octane's long-running workers, and there is nothing extra to configure.
Yes. With the JSON:API and GraphQL endpoints you can run it headless and deliver content to React, Vue, a mobile app or anything else.
Every model is scoped by a tenant_id through a global Eloquent scope. You set up the tenant resolver once and queries are isolated from then on.
Yes, under the LGPL-3.0 license, which covers both open-source and commercial use.
PagibleAI installs with Composer and a couple of Artisan commands, on top of the Laravel app you already run. The install guide walks through the steps.