Want something like this?
Tell us what yours would need to do differently. We reply with a scope and a price.
Work · 03 · Publishing
Aqilra
A multi-tenant publishing platform where every organisation runs its own publication, with the editorial workflow most blog engines forgot to build.
The problem
Organisations that want to publish face a bad trade. Hosted platforms give writers a beautiful editor and take away ownership. Headless CMSs give admins structure and make writing feel like filling in a database form. Self-hosted blog engines give you everything and make you operate everything. Almost nothing serves the actual shape of organisational publishing: authors write, editors review, the organisation owns the result.
The approach
Aqilra is multi-tenant from the first line. Each organisation gets its own publication, its own roles and its own clean public pages, on shared infrastructure it never has to think about.
- Authors get a writing surface that gets out of the way.
- Admins get a structured review-and-publish layer: drafts, review states, publication control.
- Readers get fast, clean pages with none of the platform chrome.
Review before publish is the same human gate the rest of the lab runs on.
Dogfooding
The lab’s own engineering blog is published through Aqilra. Everything on the field notes page comes from it.
Roadmap
- AI assistance inside the editor: drafting, editing and consistency support.
- A public API and embeddable widgets, so a publication can be syndicated anywhere.
- Custom domains: each tenant’s publication under its own name.