Newsroom
Plan coverage, move a story from pitch to approved, keep assets and versions together, and see what every title is working on without asking.
Media operating infrastructure
Run the publication, not the plumbing.
PublicationOS is being built as one system for the work that keeps a publication running: planning what gets written, getting it live across every domain you own, selling and billing the commercial side, and keeping a record of all of it that holds up when someone asks.
We're early and we'd rather say so. Nothing here is for sale yet, and nothing on this page is a commitment to ship a specific feature on a specific date.
Operating ledger
PHASE 0
NewsroomPlanning, drafts, review, approvals
In build
PublishingReleases, domains, delivery checks
In build
CommercialAds, sponsorships, billing workflow
In design
RecordsAudience data, provenance, audit trail
In build
Control planeTitles, domains, people, permissions
In build
Assisted workAI drafting and analysis, gated
In design
States describe internal development only. They are not availability, service levels, or a release schedule.
- Built to run
- Independent publications
- Multi-title media groups
- Local and regional news
- Business and trade publishers
- BLOS-owned properties
The situation
Most publishers don't have a software problem. They have eleven of them.
A three-title publisher typically runs a CMS per site, a separate ad server, a spreadsheet for the editorial calendar, an inbox for approvals, an analytics tab nobody agrees on, and one person who remembers how it all fits together.
Nothing in that stack knows about anything else. Launching a fourth title means rebuilding it. Losing that one person means losing the operating knowledge. And when a client, a regulator, or a court asks what ran, where, and who cleared it, the answer has to be assembled by hand from six systems.
PublicationOS starts from the opposite assumption: that titles, domains, people, permissions, published output, commercial activity, and the record of all of it belong in one system that treats a publisher — not a website — as the unit of work.
The unit of work is a publisher, not a website.
What it covers
Six desks, one system.
Grouped the way a publishing operation is actually staffed, so it's clear who owns what rather than which service it runs on.
Publishing & delivery
Publish to every domain you own from one place, control what goes live and when, and get proof each page is actually reachable.
Commercial operations
Run advertising and sponsored work as a workflow, not a favour: inventory, approvals, what ran, and what to invoice.
Audience & audit
Traffic and search data every title reads the same way, plus a durable record of what was published, edited, or removed, and by whom.
Control plane
Titles, domains, staff, roles, and permissions in one place — so adding a publication is a configuration, not a rebuild.
AI that stays on a leash
Research, drafting, and analysis that operate under the same permissions as staff, leave a trail, and stop at a human approval before anything publishes.
How it's being built
We run our own publications on it first.
PublicationOS is being developed as the operating foundation for BLOS Media Network properties. Every capability has to survive a real publishing week before it counts as done.
Commercial availability, scope, service levels, and pricing will be announced when the platform is ready for them — and not before.
- OperateBLOS titles publish daily and run into the real constraints — deadlines, domains, clients, corrections.
- BuildThose constraints become platform capabilities, with permissions and records designed in rather than bolted on.
- ProveEach capability runs in production against live publications before it's considered finished.
- OpenWhat survives that becomes available to publishers outside the network.
Commitments
Four things we're designing around.
Your titles stay yours
Clear boundaries between publishers, and deliberate ownership of your content, domains, audience data, and accounts. A platform should be a place you keep things, not a place they get stuck.
You can leave
Export and domain handoff are being designed in from the start, not added under pressure. If migrating away is impossible, the product is winning the wrong way.
The record is part of the product
What was published, changed, approved, or taken down — with who and when — is stored as first-class data, because publishers get asked and need to be able to answer.
Automation reports to a person
Automated and AI-assisted work runs inside defined permissions, leaves an auditable trail, and stops at a human decision before anything reaches an audience.
Early partnerships
Tell us how your operation actually works.
We're talking to publishers now — not to sell anything, but to make sure what we're building matches how real newsrooms and media groups run. If you're planning a migration, running several titles on tools that don't talk to each other, or just have opinions about what publishing software gets wrong, we'd like to hear it.
- Independent and regional publishers
- Multi-title media organizations
- Business and trade publications
- Anyone planning a platform migration