AppBoard
Documentation menu

Docs

Self-hosting & open source

AppBoard is open source and self-hostable. Which repository is which, how to run the stack yourself with Docker, and the license terms.

AppBoard is open source and self-hostable — and it will stay that way. The entire platform is public, so you can read the code, run it on your own infrastructure, and keep full control of your data and store credentials.

The repositories

AppBoard is split into three repositories:

  • appboard_backend — the API (Bun + Elysia + Drizzle + PostgreSQL): store connections, listings, publishing, research, keyword rank tracking, and the encrypted vault.
  • appboard_web — the admin panel (Next.js + React): dashboard, listing editor, screenshot studio, research, and automation.
  • appboard_website — this marketing site, docs, and blog.

To self-host the product you need the backend and the admin panel. The website is optional and only serves the public marketing pages.

Running it yourself

Each repository ships a README.md and CONTRIBUTING.md with the exact setup. In short:

  1. Backend — provision PostgreSQL, copy .env.example to .env, generate an ENCRYPTION_KEY (openssl rand -hex 32), set your SMTP and public URLs, then bun install and bun run dev (port 6680). Database migrations run automatically on start.
  2. Admin panelbun install, point BACKEND_URL at your backend, and bun dev (port 6600). The panel proxies /api/* to the backend.

Bring your own OpenRouter key for the AI features and your own SMTP for transactional email. Store credentials are protected by an end-to-end encrypted vault — self-hosting means those keys never leave your servers.

License

AppBoard is source-available under the PolyForm Noncommercial License 1.0.0: free to use, run, and modify for personal and non-commercial purposes. Commercial use and resale are not permitted. (This is not an OSI-approved open-source license, because it restricts commercial use.)

Get involved

Found a bug or want a feature? Open an issue on the relevant repository, or join the community on Discord. Contributions are welcome — see each repo's CONTRIBUTING.md for the branch model (work off develop) and PR process.