What ships in the integration engine.

Builder, runtime, governance, and APIs share one authorizer and one audit trail. Nothing here is a bolt-on suite.

Visual integration builder

Sources, transforms, routers, and destinations on one canvas. Save makes a flow runnable. History, restore, and portable packages with secret references only.

Polyglot Studio

Author mappings in JavaScript, TypeScript, Python, Lua, Go, Tcl, Java, Rust, C, C++, or WASM. One sirius.* catalog drives autocomplete in every pack.

Native parsers and codecs

JSON, XML, HL7, FHIR, X12, EDIFACT, and financial message families on the same host API — not a different product per standard.

Inline I/O from a transform

HTTP, databases, and files from inside the script, through a wired connector. No extra hop just to look something up.

Safe replay and dead-letter

Replay never mutates the original record. Failures can be retried, resolved, or closed. Deadlines and causation ride the envelope.

Alerting that reaches people

Rules over logs, failures, integration status, and cluster events. Email, Slack, Teams, or a webhook.

Migration in seconds

A built-in tool that reads workloads from any engine and emits native Sirius integrations — your logic, our API.

Native AI agent and MCP

A truly native agent — not a wrapper around someone else’s chat. It builds and operates integrations through the same APIs you do, so a first flow is minutes of conversation. External agents connect through MCP with the same permissions and audit trail.

HA, backup, upgrades

Clustered runtimes, checksummed backups, and one-click rollback of both the application and the data layer.

Enterprise license

The full platform under one offering. Offline verification. No feature maze, no per-message meter.

Durable processes

Long-running workflows that wait on messages and timers, and streaming topologies with time windows — on the same runtime.

Runs where you run

Laptop Compose, Kubernetes, or an air-gapped rack. Same image, same APIs.