A Knotwrx product

Connect any system. Trust every message.

Sirius is an industry-agnostic integration engine. Build flows visually, transform data in the language you already write, and keep a durable record of what moved — with a native path off the engine you use today. A truly native AI agent sits on those same APIs, so standing up an integration is a short conversation instead of a week of wiring.

Studio · JavaScript sirius.*
const body = sirius.json.decode(msg.raw);
body.processed_at = sirius.now();
body.site = sirius.table.lookup("sites", body.site_id, "UNKNOWN");

sirius.route.push(body);
result = { message: body };

Built for the people who live in the interface.

Drawing boxes is the easy part. The work is knowing what happened to a message, why it failed, who changed the flow, and whether it is safe to replay.

Visual builder

Source, transform, destination. Save makes an integration runnable. History and portable export without copying secrets.

One API, every language

JavaScript, Python, Go, and eight other packs share the same sirius.* surface, with Studio autocomplete.

Durable by default

Postgres is the product record. The broker moves work. Search, replay, and audit are first-class — not a hope the queue still has the payload.

Native AI agent

Not a chatbot taped onto the sidebar. The in-product agent builds, tests, and operates integrations through the same RBAC and audit trail as the console — which is why a first flow takes minutes, not a project plan.

Three surfaces. One contract.

If you can do it in the console, you can automate it. Agents use the same APIs you do.

REST

Operate integrations, connectors, messages, identity, and alerts over HTTP. Discover the live contract at GET /openapi.json.

REST API →

Studio

Workspaces, samples, tests, and milestones under /studio/*. The workbench your mappings actually run in.

Studio API →

sirius.*

JSON, HTTP, databases, parsers, crypto, and routing — identical across every language pack.

Host API →

Connectors for the systems you already have.

HTTP and files sit next to Kafka, FHIR, X12, MQTT, and databases — inbound and outbound, with a probe before you wire the flow.

Leave the old engine. Keep the logic.

Sirius ships a migration tool that reads workloads from the engine you run today and emits native Sirius integrations in seconds — not a compatibility layer that still speaks someone else’s dialect.

How migration works
11 language packs
30+ connector families
3 API surfaces
1 Enterprise license

Runtimes: JavaScript · TypeScript · Python · Lua · Go · Tcl · Java · Rust · C · C++ · WASM

Talk to us