Skip to content
AI Publish

Features

Everything below is in the product today. It was built on our own sites first, and most of it exists because something went wrong once.

Writing

Per-site voice and brand
Tone, audience, brand colours, and image direction per site. Global defaults flow down, and a new site can be seeded from a sister site.
Long-form that finishes
Articles over 600 words are written section by section as background jobs, with word budgets held to target and each section told what the ones before it already covered.
Your choice of model
Models are called through the built-in connectors or through OpenRouter, with a curated shortlist in every selector and a per-site or per-plan key deciding who is billed.
Search research built in
Pull competitor terms and suggested headings for a focus keyword into the brief, then score the finished draft against those same competitors.
Cross-site linking
Finds real topic overlap between sister sites on a plan and proposes contextual links, inserted only when you approve them.

Pictures

Hero images with alt text
Generated to the site's brand, imported as WebP featured images, and given alt text automatically.
Grounded in-body images
Each in-body picture is prompted from the opening of the section it illustrates, so it depicts what the text actually says.
Image Studio
Test image models against a site's brand, generate variations side by side, compare them full size, and accept one as the article's hero.
Bring your own photography
Turn generated heroes off for a site that supplies its own. Articles that already have one keep it.

Publishing

WordPress and static sites
A WordPress target gets a real post through a secure connection. A Git-backed site gets a committed Markdown file and its images. Same lifecycle, same buttons.
The right byline
Set a default author per site, chosen by name from that site's own users, and override it per article, so content does not publish under whichever account happens to hold the connection.
Deploy verification
A few minutes after a static site goes live, the plugin checks that the site itself caught up rather than trusting the commit, and flags a stalled build.
Remote edit protection
It records what it last sent to each site and refuses to overwrite a page edited there since, offering to bring that version back instead.
Out of Sync
Reads every published article back and groups them by what is actually different, offering only the repair that fits each group.

Social

6 networks, native shapes
Facebook, Instagram, LinkedIn, X, Threads, and Pinterest, each with its own copy and a live character count you can edit against.
Written at go-live
Publishing an article writes its social posts and leaves them as a draft. Sites that do not do social are left alone, and anything you wrote yourself is never overwritten.
Honest delivery records
A post is recorded as sent only to the accounts that actually received it, and a failure names each account that needs reconnecting.

Running it as a business

Plans, roles, and scoping
A plan owns its sites, its people, and its budget. Staff and read-only viewers see only their plan, enforced on every query and every write.
Per-client AI billing
A plan carries its own key and default model, so its sites bill the client rather than you.
Spend ceilings
Checked before each request, not after. Budgets and costs in Canadian dollars, with unpriced models counted separately.
Client approval
Per site. Covers every action that would rewrite a live page, not just the first publication, including bulk actions and unattended runs.
No-login review links
Each approval email carries a personal, single-article link. It expires after 2 weeks, can be revoked, and a fresh one retires the last.
Today's Work
One screen answering what needs a person today, in work order, with the buttons that do the job and a live progress view while they run.
Usage and audit
Every action logged as a business transaction, charted by month and filterable by user.
Problems Found
A read-only screen that checks whether the system's own records are true rather than reporting what they say. Every finding names the screen that fixes it.
Help on every screen
A Help button on each page and step-by-step procedures written for staff who have never seen the system before.

Which of these matter for your sites?

Tell us what you publish and we will show you the parts that apply.

Request access Ask a question first