Durable event streams that don't leave the perimeter.
Limit Platform components talk through durable event streams inside the customer perimeter. No off-premise event bus. No external broker. Audit, integration, and inter-service traffic all flow through the same fabric.
// messaging · don't leave the perimeter
Events are durable. Streams are sovereign.
A regulated AI platform produces a constant stream of events worth retaining: identity changes, authorization decisions, model invocations, integration calls, evidence writes. Routing those events through an external messaging service creates a sovereignty gap precisely where there should not be one.
Limit Bus is the messaging fabric that runs inside the customer perimeter. Inter-service communication, audit topics, integration events, and customer-app traffic all flow through the same durable, replayable, customer-owned event store.
Durable, replayable, schema-versioned.
- 01
Durable event delivery between platform components
Services produce and consume events through a customer-perimeter event store. Delivery is at-least-once with idempotency support; ordering is preserved per topic partition.
- 02
Replay for audit and incident review
Events are retained per topic policy. Audit and incident teams can replay an event stream from a point in time, reconstructing what the platform did and when.
- 03
Schema management with versioning and compatibility checks
Topics carry schemas; schemas are versioned; producer and consumer compatibility is checked. Changes go through normal review and audit.
- 04
Integration topics for customer systems
External customer systems (ERP, MES, SIEM, ticketing) interoperate with Limit Platform through integration topics. The platform exposes structured events; consumers subscribe to what they need.
The bus stays on customer hardware.
The messaging fabric deploys inside the customer perimeter on customer-procured infrastructure. No platform event leaves the perimeter through this layer. Cross-site message replication, where used, is customer-controlled.
For air-gapped deployments, the messaging fabric operates fully without external dependency. Cross-perimeter integration with customer systems uses customer-defined transports.
- Where it runs
- Inside the customer perimeter on customer-procured infrastructure. Sized per event volume.
- Delivery semantics
- At-least-once with idempotency support. Ordering preserved per topic partition.
- Retention
- Per-topic retention policies, configurable for audit, replay, and operational needs.
- Cross-site
- Customer-controlled replication for multi-site deployments. Air-gapped operation supported.
This capability is one layer of the operating system. Every application uses it. Every customer perimeter that runs Limit Platform gets it. See the full architecture →
See it in your environment.
Walk us through the systems already in place. We'll show you how this layer fits.