See whether it fits
Start with what the product is and the vocabulary the rest of the docs use, then read the module you care about most.
Introduction 27 pages, 6 sections
Everything you need to run BottleCRM.
Feature guides, API reference, integration samples, and self-hosting playbooks, written for people who want to ship, not wade through 200 pages of marketing.
Written against the code that ships. Where something is built but not reachable yet, the page says so rather than describing the screen it does not have.
Start here
Three ways in, depending on why you came.
Most people arrive doing one of these three things, and the shortest route differs for each.
Get it up on your own box
The Docker Compose stack brings up Postgres, Redis, the API, a Celery worker and the web app. Then read the environment variables and the row-level security setup.
Docker guideTalk to the API
JWT auth, an OpenAPI schema, and Swagger and Redoc served by the backend. The mobile app is a client of the same API, which is the only guarantee that matters.
AuthenticationThe whole portal
Every page, grouped.
Six sections, 27 pages. Counts come from the navigation manifest, so this list cannot drift from the sidebar.
Getting Started
What BottleCRM is, how to get it running, and the words the rest of the docs use.
Features
What each module actually does, module by module, including the parts that are not built yet.
Self-hosting
Docker Compose, the Postgres row-level security setup, and every environment variable the app reads.
API reference
Authenticating, the endpoints per resource, and what the error bodies look like when a call is refused.
Integrations
CSV import, the AI agent guide, and a worked JavaScript sample against the live API.
Mobile app
Building and installing the Flutter client for Android and iOS from source.
Something missing, or something wrong?
The docs live in the same public repository as the product, so a correction is a pull request rather than a support ticket. Every page here was rewritten against the code.