Repository notes / no tagged release

What is here.
What is not.

A changelog should describe shipped work, not fill gaps with invented dates or roadmap promises. This page is a readable snapshot of the implementation in the open-source product repository baseline.

Open-source product repository

Implemented surfaces

The list below names capabilities represented by the web, API, database, workers, configuration, and documentation in the separate open-source product repository. Availability can still depend on permissions, migrations, external services, and deployment choices.

01

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.
  • Connection-scoped worker sessions with durable command and event paths.
02

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.
  • Workspace invitations, audit logging, and access-aware search and exports.
03

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.
04

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.
05

Self-hosting and repository boundaries

The open-source product repository contains the development and single-host production baselines. This public Astro website and its Cloud waitlist are maintained in a separate marketing repository.

  • 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, private data services, secret files, migrations, backups, and monitoring guidance.
  • The marketing repository contains this static website and the separate Cloudflare Worker for the double-opt-in Cloud waitlist; neither creates Cloud product access.

See a feature here that the code no longer supports, or a real release that should be recorded? Open a focused issue with the relevant route, component, or configuration file.