Aqilra

The problem

Organizations that want to publish face a bad trade. Medium gives writers a beautiful editor but takes away ownership and structure. Headless CMSs give admins structure but make writing feel like filling in a database form. Self-hosted WordPress gives you everything and makes you operate everything. Almost nothing serves the actual shape of organizational publishing: authors write, editors review, the organization owns the result.

The approach

Aqilra is built as true multi-tenancy from the first line: each organization 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 in the spirit of Medium's editor — the page gets out of the way.
• Admins get a structured review-and-publish layer, closer to a Contentful-style admin than a blog dashboard: drafts, review states, and publication control.
• Readers get fast, clean public pages with none of the platform chrome.

The interface sensibility sits somewhere between Medium's editor, a structured admin layer, and a Notion-style UI — familiar surfaces, arranged around an editorial workflow rather than a content database.

Roadmap

• Phase 2 — AI assistance. Drafting, editing, and consistency support inside the editor.
• Phase 3 — Public REST API and embeddable widgets. Publications become distributable: syndicate posts anywhere, embed them in existing sites.
• Phase 4 — Custom domains. Each tenant's publication under its own domain, fully white-labeled.