Get started
Introduction
Sirius is an integration engine from Knotwrx. It moves data between the systems you already run — applications, files, queues, databases, devices, and partners — and gives you a place to transform that data, watch it, and recover it when something fails.
It is not built for a single industry. The same product runs clinical feeds, payment instructions, factory telemetry, and ordinary HTTP APIs. Protocols change. The operating model does not.
What you get
- A visual builder for sources, transforms, and destinations.
- A Studio where you write mappings in the language your team already uses.
- A runtime that keeps a durable record of every message so you can search, replay, and explain what happened.
- APIs for the same work the console does — REST, Studio, and the in-transform
sirius.*host library. - A native AI agent on that same contract, so building and operating a flow is minutes of conversation instead of a week of wiring.
- A migration tool that turns workloads from another engine into native Sirius integrations in seconds.
Who it is for
Integration engineers design and test flows. Operators deploy, scale, and recover them. Security teams govern access, secrets, and audit. Platform teams automate the whole surface from CI or an agent.
How the pieces fit
An integration is a graph: messages arrive at a source, pass through transforms and routers, and leave through destinations. Sirius stores the graph, the message history, and the operational state in Postgres. A message broker wakes workers. The console and the APIs are two views of the same control plane.
When you are ready to try it, start with the quick start or install the stack on your machine.