Self-hosting

Everything on this page is about running the framework on hardware you control — a clone, pnpm install, docker compose up — rather than the managed service Botseon operates for teams who would rather not run their own infrastructure.

The framework itself is Apache-2.0 (LICENSE), free to self-host, and multi-tenant from its first migration — the same code the managed service runs on, with the model providers, the computer and the mail transport pointed at accounts you hold rather than Botseon's. Running it does not make your processing lawful on its own; it gives you the levers (README.md).

Run it yourself

• Quickstart — clone, install, generate credentials, sign in and make a first bot.
• Write your first module — a package with a manifest, one tool and a declared data flow, built from an empty directory.
• Architecture — the seven packages, the four database roles, the shape of a run, and how a data subject is erased.

Reference

• Module manifest — every field of a module manifest, quoted from source.
• Permission tags — the eleven tags a tool can declare and what each one gates for review.
• The privacy CLI — export or erase one member's data from the command line.
• Provider seams — the six seams a deployment can swap, each quoted from source.

Connectors

• Connectors — bring your own OAuth app for each connector you use.
• Gmail — set up the Gmail connector.
• Todoist — set up the Todoist connector.

The home edition

• Model and voice providers — which keys to bring, and where they go.
• The computer at home — what your own machine needs to run a bot's computer.

Operations

• The command line — every command the CLI offers, and what each one does to your install.
• Status and health — the checks to run, and what a failing one means for your install.
• Sending mail — the provider settings a self-hosted install needs to send mail.