Direct and group messaging, an operations console, realtime delivery, and durable history in one package. Built for teams that need their own account model, moderation trails, and a predictable scaling path.
vvs-im ships the coordination between user clients, admin tools, REST APIs, realtime subscriptions, and the database model. Treat it as a self-hostable messaging subsystem: ship core chat and operations first, then layer media, search, or automation when the product needs them.
Sign-in, conversation list, history, realtime delivery, image and file attachments, drafts, and multi-device read sync.
Group creation, invites and removals, admin roles, mute, profile edits, and channel-aware authorization.
Admin login, user ban/unban, system broadcasts, moderation events, and admin-driven message deletion.
API writes durable rows, Outbox captures side effects, Worker publishes to Centrifugo, clients recover per channel.
Roll out by traffic, media, and deployment shape; capacity, security baselines, and SLAs are aligned with your team during delivery planning. Ops and planning docs in the repo help you reason about growth.
Design docs, data model, APIs, and operations notes live in the repo so evaluation, delivery, and customization stay grounded.
Permissions, moderation, replay, and admin workflows hurt the most when they arrive after v1. vvs-im separates user surfaces, operator surfaces, persistence, and realtime delivery from the start so you can launch one correct path, then add storage, media, or async integrations on top.
Community DMs, internal collaboration, support and ops messaging, and vertical products with embedded chat all map well when you need control over accounts, permissions, moderation, and cost—without surrendering the stack to a black-box vendor.
Product capabilities → use cases. For capacity and observability baselines, use the operations and planning docs in the repository.
