Event-driven backbone
Built on a backbone that moves at the speed of your business.
Behind every search, every agent action and every audit record sits the same event-driven spine. A NATS event mesh reaches from edge devices to the data centre; Apache Pulsar handles the durable streams. New services snap into the same flow without rewiring the ones already there.
How it flows
From edge device to insight, with one consistent event surface.
Capabilities
Engineering choices we made on purpose.
NATS event mesh
A lightweight messaging mesh that reaches from edge agents in the field to the central platform. JetStream gives every message durability; per-device credentials give every endpoint its own identity.
Apache Pulsar streams
For workloads that need multi-tenant streams, geo-replication and long retention windows, Pulsar provides the durable spine. Consumers replay from offset zero whenever they need to.
A bridge between the two
A native NATS-to-Pulsar bridge moves events both directions, with Prometheus metrics and an end-to-end integration suite. Use NATS at the edge, Pulsar in the data centre — without dual-publishing.
Replayable by default
Every change is an event. New consumers — analytics, audit, downstream agents — replay from any offset. No need to "backfill" the new system.
Backpressure-aware consumers
Workers slow down when downstream systems do. No silent queue blow-ups; no log-spam when a tenant gets noisy.
W3C trace-context end-to-end
Every message carries trace headers from edge agent to LLM call. Traces, metrics and logs land in the format your SOC already speaks.
Where it shows up
One backbone. Every product surface.
Edge agents
IndentiaLocal, IoT gateways and OT bridges publish over NATS with per-device .creds — no inbound ports.
Workflow engine
Indentia Workflow consumes Pulsar topics directly. Email-to-capture mailboxes route into the same event surface.
Agent runtime
Autonomous Agents subscribe to topics scoped to their tenancy. New skills attach to existing events without service changes.
Lineage & audit
Every event flows through OpenLineage and the immutable audit store. Replay any moment in time.
Scale & integration
Add a service. Don't rewire the rest.
New analytics, a new agent, a new compliance check — each one subscribes to the events it cares about. The producers don't change; the existing consumers don't change. Capacity scales horizontally per topic, with backpressure preventing one slow consumer from blocking another.