The AI-powered CMS

PagibleAI: The Cloud-Native CMS

Deploy on AWS, Google Cloud, Azure, or Kubernetes. PagibleAI scales from a simple blog on shared hosting to enterprise platforms handling billions of requests — with zero architecture changes.

Low-poly 3D crystalline cloud wired to distributed server nodes by a glowing cyan network, with lavender accent lines

Built for the Cloud from Day One

PagibleAI is architected as a truly cloud-native application. Built on Laravel, it leverages cloud services like load balancers, auto-scaling groups, and managed databases out of the box. No external dependencies, no separate services — just install with Composer and deploy anywhere.

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

Cloud-Native Infrastructure

cloud-check-variant.svg

Deploy Anywhere

Run on AWS, Google Cloud, Azure, or any Kubernetes cluster. The same install runs on the infrastructure you already have, with no rewrite.

scale.svg

Auto-Scaling Ready

Scale horizontally across as many instances as you need, and the site stays fast and responsive as traffic rises and falls during the day.

Object storage and CDN icon

CDN/Object Storage

Keep media off local disk. Store uploads on S3, Google Cloud Storage or any S3-compatible object store and serve them straight from a CDN.

label-multiple.svg

Multi-Tenancy

Run many isolated sites from one installation, with each tenant's data separated automatically. Useful for SaaS platforms and agencies.

laravel.svg

Any Database

Works with SQLite, MariaDB, MySQL, PostgreSQL and SQL Server, each with built-in full-text search using the database's own features.

Read/write database splitting icon

Read/Write Splitting

Send writes to the primary database and reads to replicas using Laravel's connection splitting, so read traffic no longer hits the primary.

api.svg

Smart Caching

Per-page cache with a duration you set, backed by any store. Point it at shared Redis or Memcached so every instance stays consistent.

Queue workers icon

Queue Workers

Offload AI generation, image processing and search indexing to background queue workers that scale independently from the web tier.

open-source-initiative.svg

Octane Compatible

Stays correct in long-running Laravel Octane workers, so you can keep workers warm for speed with nothing special to configure.

Flexible Content Delivery

cms-jsonapi.webp

JSON:API for the front end. A read-only endpoint that follows the JSON:API spec, so a single request returns a page together with its nested elements and file references. There is no second round trip to assemble a view, which keeps things fast for SPAs, mobile apps and static site generators that pull content at build time.

Because it sticks to the standard, the JSON:API client libraries you already use work against it without custom glue code. Responses are cached per page for a duration you set, so a traffic spike lands on the cache instead of the database, and the same endpoint serves every instance behind your load balancer.

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. Powered by Lighthouse, the admin API gives you full read and write access to pages, elements, files, versions and user permissions. It is the same API the Vue admin panel runs on, so anything you can do in the interface you can also do from your own code.

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 wire content into a CI job, a custom editor or an AI agent, and to run those integrations at scale without pulling back more data than the task needs.

Blade templates and themes: a 3D webpage assembled from layout blocks with double-curly-brace template tags and theme color swatches, blue and teal

Blade templates and themes. Pages render server-side through Laravel's Blade engine, so the front end stays plain Laravel. Publish the views and edit them, write a theme of your own, or assign a different theme per page when one site needs to look unlike the next.

Start from the bundled Clean, Paper, Glass and Premium themes, or package your own with a template for each content element. Switching a site's whole look is one setting with no build step and no front-end framework to run, so deployments stay on the same Composer-and-migrate flow as the rest of the app.

PagibleAI vs Contentful vs Contentstack

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

AI-Powered Content Workflow

Content Generation

Create drafts, rewrite text, adjust tone, and expand outlines using LLMs — directly from the admin panel.

Image Manipulation

Resize, crop, and optimize images with AI-assisted processing. No external image editing tools needed.

Audio Transcription

Convert audio and video files into searchable text content automatically using speech-to-text AI.

AI Translation

Translate pages and content elements across 35+ languages with a single action via Prism PHP.

MCP Server

33 ready-to-use tools that let AI assistants like Claude manage your entire CMS programmatically.

SEO Optimization

AI-generated meta descriptions, titles, and keyword suggestions to improve search engine visibility for every page.

Scales with Your Project

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

PagibleAI grows with your application, from a personal blog on shared hosting to a high-traffic enterprise platform:

  • Databases: runs on SQLite, MariaDB, MySQL, PostgreSQL and SQL Server, each with built-in full-text search
  • Caching: per-page cache backed by a shared Redis or Memcached store, so every instance stays consistent as you scale out
  • Multi-tenancy: run several sites from one install, with each tenant's data kept apart
  • Cloud and clusters: deploy on AWS, Google Cloud, Azure or Kubernetes and run across several servers
  • Octane: static state is safe under Octane for long-running workers
  • Page trees: the hierarchy is stored so even deep navigation loads quickly
  • Rate limiting: every endpoint is throttled by default

Version Control & Publishing

Immutable Versions

Every change creates an immutable snapshot. Full audit trail of who changed what and when, with complete rollback.

Draft/Published

Editors work on drafts while the public sees the last published version. Edit freely without affecting the live site.

Scheduled Publishing

Set pages to go live at a specific date and time. Plan content launches ahead without manual intervention.

Secure for Multi-Tenant Cloud

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

PagibleAI sets up several common protections for you:

  • Input sanitization: user input is cleaned before it reaches a visitor's browser
  • CSP headers: a Content Security Policy is sent so unapproved scripts will not run
  • SSRF protection: server-side URL fetches are checked against SSRF and DNS-rebinding
  • Bot protection: hCaptcha guards forms against automated spam
  • Database constraints: foreign keys keep content consistent when related records are deleted
  • Tenant isolation: each tenant's data stays separate from the rest

Developer Features

Custom Elements

Define new content element types with your own fields and Blade templates. Extend the CMS without modifying core code.

Shared Elements

Create reusable content blocks once and reference them across multiple pages. Update once, reflect everywhere.

CMS Importer

Migrate from WordPress with a built-in Artisan command. Import posts, pages, media, and metadata seamlessly.

Multi-Language

Full i18n support with 35+ locales. Manage translations per page with linked language versions.

Multi-Domain Routing

Serve different page trees based on the request domain. Run multiple sites from a single Laravel application.

LGPL-3.0 License

Use freely in commercial projects without licensing restrictions. No per-site fees, no vendor lock-in.

Frequently Asked Questions

What makes PagibleAI cloud-native?

PagibleAI is built on Laravel, which natively supports cloud services like load balancers, auto-scaling groups, managed databases, Redis caching, and queue workers. It scales horizontally across multiple instances and runs on any cloud provider or Kubernetes cluster without architecture changes.

How does PagibleAI compare to Contentful?

Contentful is a proprietary SaaS platform with per-seat pricing and vendor lock-in. PagibleAI offers the same cloud-native scalability and API-first approach, plus AI-powered content creation, WYSIWYG preview, multi-tenancy, and multi-domain support — all as open source with no usage fees.

How does PagibleAI compare to Contentstack?

Contentstack is an enterprise SaaS headless CMS with strong cloud-native capabilities but high costs and vendor lock-in. PagibleAI matches Contentstack on scalability, multi-tenancy, and version control while adding AI-powered content creation, multi-domain support, and full open-source freedom with no per-seat or usage-based pricing.

Which cloud providers are supported?

PagibleAI runs on any cloud provider including AWS, Google Cloud Platform, Microsoft Azure, and any Kubernetes-based infrastructure. It also works on traditional shared hosting and VPS environments.

Does it work with Laravel Octane?

Yes. All static state is designed to be safe in long-running Octane environments. No special configuration is needed for maximum throughput.

How does multi-tenancy work?

Every model is automatically scoped by a tenant_id via a global Eloquent scope. You configure the tenant resolver once, and all queries are isolated automatically — perfect for SaaS platforms and agency setups.

Is PagibleAI open source?

Yes. PagibleAI is released under the LGPL-3.0 license, which allows free use in both open-source and commercial applications. No per-site fees, no vendor lock-in.

Deploy Cloud-Native Content Management Today

Three commands. Any cloud. PagibleAI scales from shared hosting to enterprise clusters — install it now and deploy anywhere.