Steward answers your members' questions from
your own forum's discussions, and reads new posts before they land so the genuinely ambiguous ones get queued for a human.
There's no AI account to create, no API key to paste, and no model to choose. You buy capacity; everything else is handled.
Answers that cite their sources
A member asks a question and gets an answer assembled from posts already on your site — with
every source cited, so it can be checked rather than trusted.
When nothing on your forum answers the question, it says so. It doesn't reach out to the wider internet, and it doesn't invent something plausible to fill the gap. An answer you can't trace back to a real post is worse than no answer.
Moderation that flags, never deletes
Every new post is read first. Most are cleared instantly and for free — only genuinely ambiguous ones are looked at more closely.
Nothing is ever removed automatically. The strongest thing Steward can do is put a post in front of a human. Software that reads a post decides what a moderator
looks at, never what disappears.
Established members are skipped entirely after a configurable number of posts, so your regulars are never screened.
Usage where you'll actually look
Your consumption and what's left of it appear in
Steward's own settings page — not on a billing portal you have to remember to visit. It shows the daily trend, not just a total, because "60% used" doesn't tell you whether you're about to run out.
Pricing
All plans are per month, one forum per subscription, cancel any time.
| Starter | Standard | Pro |
|---|
| Price | $9/mo | $19/mo | $39/mo |
| Questions answered | 600 | 1,500 | 3,000 |
| Posts screened | 6,000 | 15,000 | 30,000 |
| Retrieval | Forum search | Forum search | Semantic, hosted |
Screening allowances are deliberately ten times the answer allowance — moderation touches every post, while answers only happen when somebody asks.
Pro adds hosted semantic retrieval: your posts are indexed on our own search cluster with embeddings, so answers are drawn by meaning rather than keyword overlap. In our own benchmarking this beat keyword matching on every question where the two disagreed.
Getting started
<code>composer require ernestdefoe/steward</code>
Your key is bound to one domain and checked on every request, so it can't be used anywhere else.
On your data
Only
public content is ever sent. Posts in private or hidden discussions are never indexed, and a post that stops being public is withdrawn from the index rather than left behind.
On hosted retrieval, your index is yours alone and is
deleted when you cancel — on the same call that ends the service, not in a cleanup job somebody remembers to run.
Links
Requires Flarum 2.0. Questions and bug reports welcome — I read all of them.
