Skip to content

How Pollora relates to Roots Acorn, Sage, Radicle and to Corcel: architecture, routing, templating, hooks, ORM and license, to pick the right tool.

Short answer: pick Sage for a modern theme on an ordinary WordPress site, Acorn to bring Laravel components into an existing WordPress install, Radicle for the Roots stack prepackaged as a ready-made project, and Corcel when a Laravel app only needs to read WordPress data. Pick Pollora for the opposite arrangement: a Laravel application that boots first and runs WordPress inside it, with hooks, post types and REST routes declared as PHP attributes.

Roots has shaped modern WordPress development for over a decade, and it is a real source of inspiration for Pollora. Bedrock showed that WordPress belongs in a Composer-managed project, Sage brought Blade and a modern build to themes, and Acorn proved that Laravel and WordPress can share a codebase. Pollora builds on that work directly:

  • themes, blocks and plugins are built with @roots/vite-plugin (WordPress dependency extraction and theme.json generation);
  • the framework uses roots/bedrock-autoloader, and the project follows a Bedrock-style layout;
  • the Blade layer ships Sage Directives (@posts, @title, @content, from log1x/sage-directives).

Pollora’s own WordPress models are built on pollora/colt, a fork of Corcel. The projects on this page are not rivals so much as different answers to the same question. This page says where each one fits.

PolloraAcornSageRadicle
What it isA framework: a Laravel application that runs WordPressA package that brings Laravel components into WordPressA WordPress starter themeA WordPress starter combining the Roots stack (Acorn, Bedrock, Sage, optional Trellis)
ArchitectureLaravel boots first; WordPress (admin, database, plugins, REST API) runs inside the Laravel appWordPress boots first; Acorn is booted from a theme’s functions.php or a pluginA theme loaded by WordPress, using AcornWordPress first, with Acorn, in a Bedrock layout
RoutingLaravel routes, Route::wp() on WordPress conditional tags, then the template hierarchy as fallbackLaravel routes alongside WordPressWordPress template hierarchy, rendered with BladeLaravel routes, through Acorn
TemplatingBlade themes with Sage Directives, Vite and Tailwind CSS; block themes also supportedBladeBlade, Tailwind CSS, ViteBlade, through Sage
Post types and hooksPHP 8 attributes (#[PostType], #[Taxonomy], #[Action], #[Filter], #[WpRestRoute], #[Schedule]…), auto-discoveredYour theme or plugin codeYour theme codePost types and taxonomies in config/post-types.php
Blockspollora:make:block, rendered with BladeYour buildYour buildmake:block, server-side rendering
Media and image sizesAny Laravel disk (S3, R2, MinIO…) with two settings; sizes declared in PHP with ImageSize, made on demandWordPress’s own uploads and image sizesWordPress’s own uploads and image sizesWordPress’s own uploads and image sizes
TestingLaravel’s testing toolsLaravel’s testing toolsYour setupPest, Playwright, linting in GitHub Actions
AI toolingNectar: guidelines, 12 agent skills and 11 MCP tools, on Laravel Boost
License and priceMIT, freeMIT, freeMIT, freeOne-time purchase: $80 for one site, $240 for unlimited sites
Maturity (November 2026)v13.40.2 stable, a young projectv6.3.0, about 2.8M Packagist installsv11.2.1, about 13.3k GitHub starsCommercial product from Roots

Sources: each project’s GitHub repository, Packagist and product page (roots.io/acorn, roots.io/radicle), checked on 6 November 2026.

Corcel is not in this table: it is a library of database models, not a way to build a WordPress site, so most rows would not apply. It has its own section below.

Choose Acorn if you already have a WordPress site, theme or plugin and want Laravel’s container, Blade, Eloquent, queues, migrations and commands without changing how the site is structured. Acorn is installed with composer require roots/acorn and booted from your theme or plugin, so WordPress stays in charge of the request. It is mature, maintained by the Roots team, widely used, and its WP-CLI integration (wp acorn) fits existing WordPress workflows.

Pollora takes the inverse route. The project is a Laravel application: public/index.php is Laravel’s front controller, routes/web.php is checked first, and WordPress is loaded inside it to serve the admin, the database and the plugins. Registration code becomes attributes that are discovered automatically: a class with #[PostType] becomes a post type, a method with #[Action('init')] becomes an action. Route::wp() lets a Laravel route match a WordPress conditional tag such as is_singular (see WordPress Routes).

Acorn slots into any WordPress site; Pollora is a project layout you start from. The full Pollora and Acorn comparison goes further: the same task written both ways, adoption figures and when Acorn is the better choice.

Choose Sage if you are building a theme for a standard WordPress install and want Blade, Tailwind CSS and a Vite build with hot reloading. Sage is the most popular project on this page and the reference for modern WordPress themes.

Pollora is an application framework rather than a theme. Pollora themes use the same ingredients, Blade, Vite, Tailwind CSS and Sage Directives (see Theme Structure), but they sit inside a Laravel app that also owns routing, controllers, middleware, queues, and the post types, hooks and REST routes declared as attributes.

If you only need a theme, Sage is the simpler choice.

Radicle is the closest project to Pollora: a complete, Laravel-powered WordPress starter from the Roots team.

Choose Radicle if you want the Roots stack prepackaged, with Bedrock’s structure, Acorn, Sage, optional Trellis for servers, and the tooling already wired: Pest, Playwright end-to-end tests, linting in GitHub Actions, and block scaffolding with make:block. It is a one-off purchase that also supports the Roots team’s work.

Pollora covers the same ground and goes further in a few places:

  • Laravel first. WordPress runs inside the Laravel application instead of Laravel running inside WordPress, so routing, middleware and the request lifecycle are Laravel’s.
  • Attributes and auto-discovery for post types, taxonomies, hooks, REST routes, WP-CLI commands, schedules, AJAX handlers and abilities, where Radicle registers post types and taxonomies in a configuration file.
  • Media on any disk, image sizes in PHP. The media library moves to S3, R2 or any Laravel disk with MEDIA_DISK and MEDIA_URL, and ImageSize declares the sizes your design uses, instead of the sizes WordPress registers for every image.
  • Route::wp(): Laravel routes matched on WordPress conditional tags, with the template hierarchy as a fallback.
  • AI tooling: Nectar gives coding agents guidelines, skills and MCP tools for the project.
  • Free and MIT-licensed.

The full Pollora and Radicle comparison sets them side by side, including where Radicle is ahead.

Both use a Bedrock-style layout (in Pollora, WordPress core in public/cms and wp-content in public/content; see Server Configuration) and install WordPress core and plugins with Composer.

Corcel is not a framework and does not build WordPress sites. It is a set of Eloquent models over the WordPress tables, for a Laravel (or other PHP) application that needs to read WordPress data. WordPress itself is never booted: no hooks, no plugins, no theme.

Choose Corcel if your main application is a Laravel app and WordPress is only a back office where editors write content. Your app reads posts, pages, terms, users and meta through Corcel and renders them its own way. It is MIT-licensed, at v9.0.0, with about 4.8k GitHub stars (October 2026).

Choose Pollora if the site itself is WordPress: you want its admin, its plugins and its editors, with Laravel routes, controllers and Blade on the front end. Hooks fire, plugins load, and the REST API and the template hierarchy keep working.

The two are related rather than rivals. Pollora’s WordPress models (Pollora\Models\Post, Page, Attachment, Term, User, Menu…) are built on pollora/colt, a fork of Corcel, so Corcel-style queries remain available inside a Pollora app.

There is no dedicated migration guide yet. What carries over directly:

  • Blade templates, including Sage Directives such as @posts, @title and @content.
  • Tailwind CSS and Vite, with @roots/vite-plugin generating theme.json from your @theme design tokens (see Theme Structure).
  • A Bedrock-style, Composer-managed project: WordPress core and plugins are Composer dependencies.
  • ACF-style inner blocks: Pollora’s <InnerBlocks /> tag follows ACF’s, only the default wrapper class differs (see Gutenberg Blocks).

What changes: hooks and post types move from function calls or configuration to attribute classes, and the project becomes a Laravel application with WordPress inside it.