OpenLivery – ajanslar için açık kaynaklı çok kiracılı WhatsApp ajanları

The open-source, white-label platform for agencies to build, run and manage AI agents for their clients.

Documentation · Documentación · Quick start · Self-hosting · Discussions

OpenLivery is a multi-tenant workspace where an agency creates AI agents for its clients, gives each client a branded portal, and talks to end users over WhatsApp or an embeddable web chat widget. Bring your own OpenAI / Anthropic keys and self-host the whole thing with one command.

Full documentation lives in docs/ . Every guide is written twice: English and Spanish , same filename under each.

Three services plus PostgreSQL, orchestrated by Docker Compose:

All data lives in PostgreSQL; provider keys and WhatsApp sessions are encrypted at rest. Every query is scoped by agency_id for tenant isolation, and public endpoints (sign-in and the web widget) are rate-limited per client IP. A Caddy gateway serves the app and API from a single origin ( /api/* → backend).

Then open http://localhost:3000 (API docs at http://localhost:8000/docs ). Ports clashing? API_PORT=8001 WEB_PORT=3001 DB_PORT=5433 make up . Prefer not to build? make pull runs the prebuilt images published to GHCR.

The full walkthrough — first agency, provider keys, agents, knowledge and channels — is in the getting started guide .

Deploying to a public server (reverse proxy, TLS, backups) is covered in self-hosting .

apps/mobile is an optional Expo app: the inbox a business you serve carries in their pocket, with conversations, takeover, replies, photos and voice notes. It is not installed with the platform and the server does not need it — nobody running OpenLivery has to build or deploy it to have everything working.

It deliberately carries no brand : no name, no logo, no bundle identifier, no preset pointing at any hosted service. What ships is a working app and the machinery to make it yours — put your identity in a brand file, build, and publish it under your own name from your own developer account. The whole checklist, including why you publish it rather than us, is in apps/mobile/WHITELABEL.md .

Run the project locally, the test suites and the conventions are documented in the contributing guide . In short: all code, identifiers, comments and docs are in English; end-user UI is localized (English default, Spanish) through the typed i18n system in apps/web/lib/i18n .