Skip to content
AI Publish

Frequently asked questions

The questions that come up before anyone signs anything.

Who owns the content it writes?

You do. It is written for your sites, published to your sites, and stays yours if you stop using the system. Nothing is retained here as a condition of using it.

Does it publish without me looking at it?

No. Unattended runs generate articles and push them as drafts. Taking something live is always a person pressing a button.

If you want a second pair of eyes on top of that, switch on client approval for a site and nothing can go live until somebody signs off, including bulk actions.

What happens if someone edits the published page?

The system notices. It records what it last sent to each site and compares that against what is live, so an edit made on the site is visible rather than silently overwritten on the next push.

You can pull the live wording back into the hub, or push over it on purpose. It will not choose for you.

Which AI models does it use?

Whichever you pick. Text and image models are called through the built-in connectors or through OpenRouter, and you can change the model for a site or a whole client without a redeploy.

Model prices move constantly, which is why the budget is set in dollars rather than in words or credits.

How is the AI billed?

A client plan can carry its own provider key, in which case that client is billed directly by the provider at cost. Where a site runs on the shared key instead, both the plan and the site say so by name, so you always know who is paying for what.

Can my client log in without seeing everyone else's work?

Yes. A plan is the boundary. Staff and read-only viewers see only their own plan's sites, articles, jobs, and costs, and that is enforced on every query rather than by hiding menu items.

Does it work with a static site?

Yes. A Git-backed site such as Astro receives a committed Markdown file and its images, and follows the same lifecycle as a WordPress target. A few minutes after publishing, the system checks that the deployed site actually caught up.

How much of it is really automatic?

Planning, writing, illustrating, and drafting the social copy. Approving and publishing are yours, on purpose. The system is built to remove the retyping, not the judgment.

What happens if we stop?

Your published content is already on your own sites and stays there. Nothing about the pages depends on this system continuing to run.

Where does it run?

On hosting managed by Doorways Into Your Business. You get a login, and there is nothing to install on your own sites beyond the connection.

Still got a question?

Ask it directly and you will get an answer from the person who built the thing.

Request access Ask a question first