The AI-powered CMS

PagibleAI: The Headless CMS

Deliver content to any frontend over JSON:API and GraphQL. PagibleAI works as a headless CMS and adds AI tools for creating content.

Isometric 3D illustration of a central glowing content hub delivering structured content over thin cyan connections to a laptop, smartphone and tablet, in a blue and teal palette on a transparent background

What is a headless CMS?

A headless CMS keeps the content backend separate from the frontend. Rather than rendering pages itself, it serves structured content over APIs, so you can build the frontend with whatever technology you like, such as ReactJS or VueJS.

PagibleAI provides a standard compliant JSON:API REST endpoint for reading content and a GraphQL API for managing it, so you can wire it into any stack you build.

composer require aimeos/pagible
php artisan cms:install
php artisan migrate

Content delivery

api.svg

JSON:API

A read-only, JSON:API-compliant REST endpoint for content delivery. Fetch a full page with its nested elements and file references in a single request.

graphql.svg

GraphQL API

An admin API powered by Lighthouse. Read and write pages, elements, files, users and permissions from your own code, or build a custom editor on top.

laravel.svg

Structured Content

Content is stored as structured JSON elements rather than fixed HTML, so you can query it, transform it and render it however each channel needs it.

media.svg

Media & Files

Images, video, audio and documents are stored with ready-made preview sizes and served fast over a CDN, ready to drop into any frontend, app or channel.

structured.svg

Multi-Channel

Deliver the same structured content to websites, mobile apps, digital signage, IoT devices and print, all served from one CMS and one source of truth.

languages.svg

Multi-Language

Deliver content in 35+ languages, with each language version of a page linked to the original, so any frontend can request the locale its visitor needs.

Two APIs for your content

JSON:API content delivery: a glowing JSON document with curly-brace code delivering data to a laptop, phone and tablet, blue and teal

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.

Illustration of a GraphQL admin API as a connected graph of data nodes with an admin control panel, in blue and teal

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.

PagibleAI vs Contentful vs Strapi

Features
PagibleAI PagibleAI
Contentful Contentful
Strapi Strapi
AI-powered content
good
commercial
bad
AI image editing
good
bad
bad
Audio transcription
good
bad
bad
MCP / AI tools
good
bad
bad
WYSIWYG
good
complex
bad
GraphQL API
good
good
good
JSON:API
good
proprietary
proprietary
Structured content
good
good
good
Full-text search
good
good
bad
Multi-channel
good
good
good
Multi-language
good
good
good
Multi-domain
good
good
bad
Multi-tenancy
good
good
bad
Roles & permissions
good
good
good
Version control
good
good
commercial
Real-time collaboration
good
bad
bad
Scalability
good
enterprise only
bad
Costs
good
bad
good
No Vendor lock-in
good
bad
good
Open Source
good
bad
good

Create once, deliver everywhere with AI

Content Generation

Draft new text from a prompt, rewrite or retone a passage, or expand a few bullet points into full copy, all with an LLM inside the admin panel.

Image Manipulation

Generate, resize, crop, retouch and clean up images with AI right inside the CMS, so you never have to open a separate image editor to get them ready.

Audio Transcription

Turn audio and video into accurate, editable text with speech-to-text, so recordings become content you can search, reuse and translate later.

AI Translation

Translate a whole page or a single element into any of 35+ languages in one action through Prism PHP, with each version linked back to the original.

SEO Optimization

Get titles, meta descriptions and keyword suggestions written for each page from its own content, giving search engines what they need to rank it.

MCP Server

An MCP server with 33 tools lets an assistant like Claude create, edit and publish content for you, so the routine CMS work can run almost hands-free.

Scaling up

Scaling up: a single server rack multiplying into a rising cluster of servers with database cylinders and an upward growth arrow, blue and teal

Headless delivery puts the traffic on your APIs, and PagibleAI scales to handle it, from a small blog to a busy production site:

  • Cloud and clusters: deploy on AWS, Google Cloud, Azure or Kubernetes and scale horizontally across several servers.
  • Databases: runs on SQLite, MariaDB, MySQL, PostgreSQL and SQL Server, each with optimized full-text search.
  • Multi-tenancy: run several sites from one install, with each tenant's data kept apart.
  • Page trees: the hierarchy is stored so even deep navigation loads quickly.
  • Octane-ready: run on Laravel Octane with long-running workers to handle more concurrent API traffic.

Your frontends only see what you publish

Immutable Versions

Every save writes an immutable snapshot, so you keep a full record of who changed what and when, and can compare versions or roll back at any time.

Draft/Published

Editors work on a draft while your APIs and visitors keep serving the last published version, so nothing changes for consumers until you publish.

Scheduled Publishing

Set a page to go live at the date and time you choose and it publishes itself, so you can prepare launches ahead instead of publishing them by hand.

Security

A glowing 3D security shield with a padlock emblem, connected by cyan lines to a protected system, blue and teal

Going headless means your content backend is reached over public APIs, so the protections that matter most are the ones guarding those endpoints:

  • API permissions: every GraphQL admin call runs through the same role checks as the panel, so each consumer reads and writes only what its role allows.
  • Read-only delivery: the public JSON:API endpoint can only read content, so the channel your frontends depend on can never change it.
  • Input sanitisation: content is cleaned before it is stored and served, so no frontend ever receives unsafe data.
  • Tenant isolation: each tenant's data stays separate, so one tenant's API access never reaches another's content.

For developers

Custom Elements

Define your own content element types with their own fields and validation, then deliver them through the same APIs, all without touching core code.

Multi-Domain Routing

Serve a different page tree depending on the request domain, so you can run several separate sites or brands from a single Laravel application install.

CMS Importer

Move a site over from WordPress with a single Artisan command that brings across posts, pages, media and metadata while keeping the structure intact.

Eloquent Models

Every page, element and file is a normal Eloquent model with UUIDs, soft deletes and relationships, so you query and extend them like any Laravel model.

Full-Text Search

A custom Laravel Scout engine indexes pages, elements and files for full-text search, running on each database's native engine, so there is no separate search service to host.

LGPL-3.0 License

Released under the LGPL-3.0 license, so you can use it freely in open-source and commercial projects alike, with no per-site fees and no vendor lock-in.

Frequently Asked Questions

Is PagibleAI a headless CMS?

Yes. It has both a JSON:API REST endpoint and a GraphQL API, so you can deliver structured content to any frontend you build.

How does PagibleAI compare to Contentful?

Contentful is a proprietary SaaS headless CMS with per-seat pricing and lock-in. PagibleAI offers the same structured content and API-first approach, and adds AI content creation, a visual preview, multi-tenancy and multi-domain support. It is open source, with no usage fees.

How does PagibleAI compare to Strapi?

Strapi is a Node.js headless CMS that takes real effort to self-host and does not scale on its own. PagibleAI adds built-in AI features, multi-tenancy, JSON:API delivery and visual editing, all on top of Laravel.

Can I use PagibleAI with React, Vue, or Next.js?

Yes. The JSON:API and GraphQL endpoints deliver structured content to any frontend, including React, Vue, Svelte, Next.js, Nuxt and mobile apps. You consume the API like any other headless CMS.

Does PagibleAI support multi-channel content delivery?

Yes. Content is stored as structured JSON elements rather than HTML, so the same content can go to websites, mobile apps, digital signage, IoT devices or print from a single CMS.

Which databases are supported?

SQLite, MariaDB, MySQL, PostgreSQL and SQL Server. Full-text search works on each one using that database's own features.

Is PagibleAI open source?

Yes, under the LGPL-3.0 license, which covers both open-source and commercial use. There are no per-site fees and no lock-in.

Add a headless CMS to your stack

PagibleAI delivers structured content over JSON:API and GraphQL to any frontend. The install guide walks through the steps.