For: admins of a self-hosted instance. The “Documentation” link in your sidebar points at this help centre, which is written for the hosted product — so this article exists to say which parts of it are about a product you are not running.
What is exactly the same
The product itself. Playbooks and their two kinds, personas and their routes, workspaces, the three roles, the access rules including “Only me”, workspace files, the browser extension and the MCP server. Everything in this help centre about how those work applies to you unchanged, because it is one codebase.
What does not exist on your instance
Plans, seats and AI credits. There is no subscription and nothing metered. Skip the billing articles entirely — they are not a preview of something you could switch on.
The starter-playbook step in the setup wizard. Generating a first set of playbooks from a company description is a hosted feature; your wizard goes straight from the welcome screen to the channel choice.
Groups in the access dialog. You restrict a playbook to named people; naming a group is hosted-only. The underlying tables ship with your instance but have no interface, so a group could not grant anything anyway.
In-product feedback and this help centre's messenger. Your build ships no key for it, so none of it loads. That is the point: your users never report into our workspace. Set your own key if you want the feature, pointed at your own project.
A provider key is not optional for you
Self-hosting is bring-your-own-key by design. With no credits to fall back on, nothing AI-powered runs until a key is connected under Settings → Integrations — which is why the wizard keeps asking for one whatever channels you picked.
The upside is the one most operators came for: prompts go to a provider you chose, under a contract you signed, from infrastructure you run.
One thing that looks broken and is not
In the extension step of the setup wizard, the automatic “installed” detection never ticks on your instance. The extension itself works — only the detection does not, because a browser extension can answer that question for one named origin and ours names the hosted address.
There is no setting for this and no configuration you have missed. Install the extension and carry on; the unticked step is cosmetic.
Updates and licence
Releases are published on GitHub and your instance tells you when a newer one exists. Updating is pulling the new version, not a migration you have to plan around.
The licence is the Sustainable Use License — fair-code, not open source. You may run it, read it, modify it and self-host it for your own purposes; what it does not permit is reselling it as a hosted service. If that distinction matters to your legal review, read the licence itself rather than this summary.
The operator-facing documentation — installation, upgrades, environment variables, running the stack — lives with the code in the repository, not here. This help centre is about using the product; that documentation is about running it.
Updated 27 September 2026 · Article version 1