--- title: PagibleAI: The Laravel Headless CMS | daily.dev description: PagibleAI is a self-hosted headless CMS that installs directly into Laravel via Composer, sharing the application's database, users, and infrastructure. It... canonical: https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: PagibleAI: The Laravel Headless CMS | daily.dev og:description: PagibleAI is a self-hosted headless CMS that installs directly into Laravel via Composer, sharing the application's database, users, and infrastructure. It... og:url: https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi og:image: https://api.daily.dev/og/posts/FQlNTuqpi.png og:image:alt: PagibleAI: The Laravel Headless CMS og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # PagibleAI: The Laravel Headless CMS **[Medium](https://daily.dev/sources/medium_js)** · 6 min read · 0 upvotes · 0 comments ## Summary PagibleAI is a self-hosted headless CMS that installs directly into Laravel via Composer, sharing the application's database, users, and infrastructure. It provides a complete editorial and publishing workflow out of the box, exposing approved content through a read-only JSON:API while using GraphQL for administration. Key features include full-text search across SQLite/MySQL/PostgreSQL/SQL Server, multi-domain and multi-language support, tenant-scoped content, versioning, and optional AI-assisted editing. The post also compares PagibleAI against Statamic, Twill, and Filament, positioning it as the option that ships a finished CMS with public delivery API under an open-source model, avoiding both commercial licensing costs and the engineering overhead of building a delivery layer from scratch. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How is PagibleAI different from Statamic and Twill for a Laravel project? PagibleAI installs directly into an existing Laravel app via Composer and Artisan, sharing its database, auth and storage, and ships a complete editorial and publishing system with a read-only JSON:API for delivery. Statamic offers headless delivery and multi-user publishing only under paid Statamic Pro. Twill provides strong editorial components but leaves frontend routes and API endpoints for developers to build themselves. _Compare Laravel CMS options like this on daily.dev before committing to one architecture._ ### Does PagibleAI support a public GraphQL API for content delivery? No, public content delivery in PagibleAI is centered on a read-only JSON:API, while GraphQL is reserved for the administration interface and custom management tools. A project that specifically needs a public GraphQL content API would need to add that layer itself, since it falls outside PagibleAI's intended delivery model. _Track API design trade-offs for headless CMS choices like this one on daily.dev._ ### What databases does PagibleAI's full-text search support? Full-text search in PagibleAI works across SQLite, MySQL, PostgreSQL and SQL Server. The package also supports multiple domains and languages sharing one installation, plus tenant-scoped content for several sites within a single Laravel deployment, though multi-tenancy relies on a shared database rather than separate databases per tenant. _Developers weighing self-hosted CMS features against database support follow details like this on daily.dev._ ## Similar posts on daily.dev - [Building AI Agents with Laravel: No Python Required](https://daily.dev/posts/building-ai-agents-with-laravel-no-python-required-5lpqru3o0) · Laravel · 7 upvotes · 0 comments - [AI Generative Engine Optimization for Laravel](https://daily.dev/posts/ai-generative-engine-optimization-for-laravel-ldr3vzkqb) · Laravel News · 18 upvotes · 0 comments - [Meet Fimo.ai, the AI-Native CMS from Strapi](https://daily.dev/posts/meet-fimo-ai-the-ai-native-cms-from-strapi-f5ihxeeo5) · Neon · 0 upvotes · 0 comments --- Tags: [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel), [#cms](https://daily.dev/tags/cms) [View this post on daily.dev](https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"PagibleAI: The Laravel Headless CMS","url":"https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi"},"datePublished":"2026-07-19T20:55:56.263Z","dateModified":"2026-09-14T06:38:25.822Z","description":"PagibleAI is a self-hosted headless CMS that installs directly into Laravel via Composer, sharing the application's database, users, and infrastructure. It...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bc1f5a55ae4637543fce393752fb3fd6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bc1f5a55ae4637543fce393752fb3fd6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"php,laravel,cms","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"PagibleAI: The Laravel Headless CMS"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/pagibleai-the-laravel-headless-cms-fqlntuqpi#faq","mainEntity":[{"@type":"Question","name":"How is PagibleAI different from Statamic and Twill for a Laravel project?","acceptedAnswer":{"@type":"Answer","text":"PagibleAI installs directly into an existing Laravel app via Composer and Artisan, sharing its database, auth and storage, and ships a complete editorial and publishing system with a read-only JSON:API for delivery. Statamic offers headless delivery and multi-user publishing only under paid Statamic Pro. Twill provides strong editorial components but leaves frontend routes and API endpoints for developers to build themselves. Compare Laravel CMS options like this on daily.dev before committing to one architecture."}},{"@type":"Question","name":"Does PagibleAI support a public GraphQL API for content delivery?","acceptedAnswer":{"@type":"Answer","text":"No, public content delivery in PagibleAI is centered on a read-only JSON:API, while GraphQL is reserved for the administration interface and custom management tools. A project that specifically needs a public GraphQL content API would need to add that layer itself, since it falls outside PagibleAI's intended delivery model. Track API design trade-offs for headless CMS choices like this one on daily.dev."}},{"@type":"Question","name":"What databases does PagibleAI's full-text search support?","acceptedAnswer":{"@type":"Answer","text":"Full-text search in PagibleAI works across SQLite, MySQL, PostgreSQL and SQL Server. The package also supports multiple domains and languages sharing one installation, plus tenant-scoped content for several sites within a single Laravel deployment, though multi-tenancy relies on a shared database rather than separate databases per tenant. Developers weighing self-hosted CMS features against database support follow details like this on daily.dev."}}]} ```