8
Aug
PagibleAI CMS
A Laravel CMS your whole team can work with
Give editors a clear publishing system and developers a compact, API-first foundation that fits the Laravel application you already run.
One system, clear responsibilities
Editors shape and publish
Build pages from defined content elements, keep drafts separate from the live site, schedule releases, and restore earlier versions.
Developers keep Laravel
Use Blade, Eloquent, queues, storage, cache, authentication, and the deployment practices already understood by your team.
Clients use published content
Serve the website from a theme or deliver the same approved records through JSON:API and purpose-built integrations.
Let editors work without touching the live version
Every change becomes an immutable version. Editors see the latest draft while public routes and delivery APIs continue to read the published snapshot. A publisher can review, schedule, restore, or approve the exact revision that should go online.
Shared elements keep recurring content in one place, and the page tree gives complex sites a navigation structure that remains understandable in the admin.
One content base, several ways to use it
Surface
What it provides
Typical reader
Theme renderer
Cached HTML from Blade views
Website visitors
JSON:API
Read-only published records
Web and mobile clients
GraphQL
Queries and CMS mutations
Admin applications and integrations
MCP server
33 content and media tools
Authorized assistants and automations
Search engine
Database-native full-text search
Visitors and editors
Put AI beside the editorial controls
Editors can draft and refine text, translate content, describe media, transcribe audio, and perform focused image operations without moving work through unrelated tools. Each task can use its own configured provider and model.
Assisted work enters the page as a draft. Your permissions, review process, and published version remain the authority.
Built for the work around publishing
Multiple sites and languages
Run separate page trees by domain, keep tenant data scoped in one shared database, and publish localized content from the same model.
Search on your database
Use SQLite FTS5, MySQL full text, PostgreSQL tsvector, or SQL Server CONTAINSTABLE through one Scout engine.
Security in the normal path
Sanitize submitted HTML, enforce CSP headers, validate URLs, throttle endpoints, and apply tenant-aware permissions.
Made for teams that share ownership of the site
Our editors can prepare a release without wondering what is already public. The version boundary is obvious, and the page tree feels familiar on the first day.
We kept Laravel in charge of the application and added the CMS where it belonged. There was no second platform to operate or work around.
Translation and media descriptions now happen inside the draft. Review still belongs to our team, which made the rollout easy to explain.
From the journal
Before you install
Can PagibleAI be added to an existing Laravel application?
Yes. PagibleAI is installed as Composer packages and uses the application's existing database, storage, cache, queue, and authentication services.
Does AI-generated content publish automatically?
No. Generated and translated content remains part of the editable draft. Publishing still requires the permissions and action defined by your workflow.
Can one installation serve several sites?
Yes. Multi-domain routing can select separate page trees, and single-database tenant scopes keep records separated when you run more than one tenant.
Which databases support full-text search?
The search package supports SQLite, MySQL, PostgreSQL, and SQL Server using the native full-text features of each database.
Is PagibleAI open source?
Yes. PagibleAI CMS is released under the MIT license.