OpenVibe.Events

OpenVibe.Events is the durable event backbone of the OpenVibe network, at openvibe.events. Its README describes it as "Durable events, subscriptions, delivery, retry, dead letters and replay for the network."

What it does

Every authoritative service writes domain mutations and outbox events in one transaction, a relay publishes them to Events, consumers use inbox and idempotency receipts, and browsers get resumable projections through the Realtime delivery plane. It stores events, subscriptions, deliveries and checkpoints in PostgreSQL (ov_events), signs webhook deliveries with signature v2, retries with backoff, keeps a dead-letter queue and supports replay. It also serves developer apps with sandbox separation, per-project quotas and SSRF-guarded webhooks. Retention is tiered: hot, a replay tier (events_archive) and an operator-run monthly NDJSON archive.

What it does not do yet

It does not own media bytes, game or media transport packets, or product business rules. WebSocket and presence are "not built yet". Carrier options such as NATS Core, JetStream and a cloud SQS-compatible queue are optional and off unless configured.

How it fits the network

Live, Media, Chat, Games, Network and OpenRestream publish to it in production, and every consumer webhook requires signature v2. It is consumed by OpenVibe.Search and other services, and depends on OpenVibe.Network for token signing keys and subject ids. The README records that it "Replaces the best-effort internal POSTs/webhooks between Live, Media, Network and Community."

Runtime and status

It runs on Node 22 and Express, listening on 127.0.0.1:4300 behind nginx. STATUS.json records the stage as "alpha" and the service deployed with sudo ovhost deploy events. License: AGPL-3.0.