Developers
The builder track. Architecture, code conventions, and the contribution workflow for working on or self-hosting Concierto.
This is the developer track of the docs: the technically-biased material for people building on, extending, or self-hosting Concierto. If you're here to use the product, start with the user manual instead.
In this section
- Architecture: how the platform fits together: Go backend, monorepo frontend, shared packages, and the runtime that executes agents.
- Conventions: the single source of truth for code naming, the i18n translation glossary, and the Chinese voice guide.
- Contributing: the local development workflow: shared Postgres, worktrees, daily commands, and checks.
Related reference
The rest of the technical surface lives alongside this section:
- Daemon and runtimes: the local-daemon model and bring-your-own runtimes
- AI coding tools: the providers a runtime can drive
- Tasks: the execution task lifecycle
- Self-host quickstart and Environment variables
- Sign-in & SSO and Authentication & tokens
- CLI reference