Pages are layouts, not forms
Most content systems ask editors to fill in fields and imagine the result. Aurora lets them work on the page itself, without giving up structure, permissions or code you own.
Principles
Three things we believe
Edit what visitors see
The editor renders the real templates. When the editing surface is the page, people stop asking developers to "just move that box".
Structure stays structure
Every block is typed, validated and stored as JSON. That is what lets translations, search and AI assistants work with content safely.
Nobody gets more power than they have
Roles decide what people can do, and an assistant acting for someone has exactly their rights. Nobody can grant a permission they do not hold.
The problem
Why not a form-based CMS?
A form is a great way to capture data, and a poor way to make a landing page. Editors think in sections, columns and emphasis, not field names. When every layout change needs a new field, a developer, or both, pages end up looking the same.
Aurora keeps the parts of structured content that matter (types, validation, revisions, translations) and drops the guessing. Blocks are still fields under the hood: the inspector shows them, and the canvas lets people type straight into them.
The platform
Why build on Laravel and Filament?
Your team already knows Laravel. Aurora is a package in it, not a platform beside it: your models, queues, tests and deployments stay the same. Filament gives the admin a consistent, accessible interface that developers can extend with the tools they already use.
Nothing is hidden in a hosted service. The database is yours, the code is in your repository, and the blocks are classes you can read.
The assistant
Why put AI in a CMS?
Because the hard part of AI in content work is not writing, it is trust. Aurora's assistant uses the same tools the editor does, with the same permissions, and every change it makes is a revision with the person's name on it.
The same tools are offered over the Model Context Protocol, so Claude and other apps can draft, translate and tidy pages too, and nothing they do is out of reach of the undo button.
FAQ
Questions people ask
Yes. Blocks are Blade views in your app, styled however you like. The visual editor renders them with your stylesheet, so editors always see your design.
That is what it is for. Install the package, run aurora:install, and register your blocks and settings from your own service provider.
In your database. Pages store their blocks as JSON, media goes to whichever filesystem disk you configure, and nothing is sent anywhere unless you connect an AI provider.
No. The assistant stays switched off until someone adds a provider and an API key under Settings, and MCP access is a separate permission per role.
English and Norwegian out of the box. Every label can be translated from the Translations screen, and new languages can be imported from lang files.
Convinced, or curious?
The quickest way to judge a CMS is to use it. Install Aurora in a fresh Laravel app in a few minutes.
Getting started