One event. Many destinations.
Define customer contracts once and deliver to HTTP, Kafka, RabbitMQ, NATS or SQS without embedding routing in your application.
Publish business events once. Let Nuntivus handle customer-specific routing, payloads and delivery—on infrastructure you control.
Alpha release: APIs, configuration and behavior may change before a stable release.
orders.createdThe API accepts events. PostgreSQL keeps the durable record. JetStream distributes work to the Worker, where customer contracts shape every delivery.
A dedicated delivery layer, not another set of integration branches in your application.
Define customer contracts once and deliver to HTTP, Kafka, RabbitMQ, NATS or SQS without embedding routing in your application.
Validate schemas, review compatibility, filter events and transform payloads. Simulate the full contract before sending.
Inspect delivery history, retry failures, replay events and monitor success and latency targets with SLOs and alerts.
Run the API, Worker and dashboard yourself. Keep your data, credentials and delivery policies in your own environment.
Build the API, Worker and administration dashboard from source with Docker Compose.
Read the quick start →Local evaluation only. Production hosting has separate security requirements.
git clone https://github.com/nuntivus/nuntivus-server.git
cd nuntivus-server
docker compose -f docker-compose.quickstart.yml up -d --waitExplore the architecture, try the project and help shape what comes next.
At-least-once processing: consumers must tolerate duplicate deliveries.