Open-source product status

What the current
beta includes.

WATeamInbox does not have a tagged public release yet. Until it does, this page summarizes the features implemented on the main branch of the open-source repository.

Open-source product repository

Implemented surfaces

These features are present across the web app, API, database, and workers. Some require additional services, configuration, or the right workspace permissions.

Inbox and WhatsApp connections

The current application can manage multiple WhatsApp connections per workspace, pair devices through QR codes, reconnect or archive sessions, and route each contact through its owning connection.

Message history sync with progress state and on-demand older history.
Text and supported media messages, replies, reactions, delivery state, presence, typing, and groups.
Contact profiles preserve WhatsApp public usernames separately from phone numbers.
Connection-scoped worker sessions with durable command and event paths.

Team workflows and access

Workspace roles and granular permissions define who can see conversations, send, assign, manage connections, export data, or inspect operational history.

Owner, admin, and member roles with owner-managed permission overrides.
Contact assignment, assignment history, shared and private notes, tags, and CSV contact import.
Blocked contacts replace outbound actions until an authorized user unblocks them.
Workspace invitations with automatic join after email verification, audit logging, and access-aware search and exports.

Business inbox tools

The web app and API include the business-facing tools represented in the repository, without implying that every WhatsApp capability is supported.

Quick replies with shortcuts, WhatsApp Business label sync and tag linking.
Catalog and product sync with archive/restore and product visibility controls.
Scheduled messages and permission-gated broadcast jobs with pacing and quota configuration.

Analytics, notifications, and data

Operational views expose activity and response information while keeping PostgreSQL as the durable source of truth.

Dashboard metrics for messages, contacts, teams, engagement, response time, and resolution cases.
Calendar-aware response and resolution SLA policies plus breach views.
In-app and desktop notifications, optional Web Push, Meilisearch with a PostgreSQL fallback, and CSV/JSON/ZIP exports.

Self-hosting and repository boundaries

The open-source product repository contains the development and single-host production baselines. The managed Cloud control plane and this public website remain separate from the MIT-licensed application.

Development Docker Compose for PostgreSQL, NATS, Centrifugo, Meilisearch, and MinIO lives with the open-source product.
The product repository documents a production Compose baseline with Caddy, a readiness-aware API router for 1–10 homogeneous API replicas, private data services, secret files, migrations, backups, and monitoring guidance.
WhatsApp workers use independently tagged artifacts and stop-first, rollback-aware rollout gates; the orchestrator remains a singleton.
The public website links to the managed Cloud application while keeping commercial plans, billing, and entitlements outside the open-source repository.