Event Bus
Platform coreEngine 11 of 12 · The spine
Ordered, per-tenant, replayable domain events.
Event Bus
The Event Bus is the architectural spine of Clario360: ordered, partitioned per tenant, schema-registered and replayable. Apps publish facts as domain events and never call each other's databases — which is why suites ship, scale and fail independently.
Inside the Event Bus
Ordered & partitioned
Per-tenant ordered event streams
Schema registry
Versioned, validated event contracts
Replayable
Rebuild state from the log
No coupling
Facts, not commands; no DB calls
The other engines
Every engine is built once and consumed by all four suites. That is the platform-first dividend.
Workflow Engine
Configurable approvals, stage gates and state machines
Forms Engine
Admin-built forms and data capture, no redeploy
Automation Engine
Runbooks, drills and event-triggered actions
Integration Engine
Source and target adapters, gov-platform connectors
IAM
One login, RBAC and tenant isolation across the platform
File Service
Sovereign document storage, legal hold and evidence
Notifications
Email, SMS and in-app alerting, centrally governed
Licensing
Per-tenant entitlement and packaging control
AI Services
Copilots, contract review and detection, RAG-ready
API Gateway
AuthN/Z, rate limits, routing and versioning · Go
Observability
RPO/RTO/latency SLOs and platform-wide audit
See the platform core in a deep-dive
From the gateway to the event bus — a working session on how the engines fit together in your environment.