Sirius A product of
Documentation Contact

Get started

Core concepts

A short vocabulary so the rest of the docs stay precise.

Integration

A running flow that receives, transforms, and delivers data. In the console this is what you build, start, and stop as one unit.

Component

A node in that flow. Components are sources (messages in), transforms (messages change), destinations (messages out), plus routers and filters.

Connection

A directed edge. It defines which queue a downstream component consumes.

Message

An immutable envelope: payload, identifiers, causation, and a deadline. The broker moves work. Postgres keeps the record. Replay means re-emitting from that record, not hoping the queue still holds the bytes.

Studio workspace

A transformation project: a runtime pack (language), files, sample payloads, and optional golden tests. The same workbench is embedded on a transform node in the visual builder.

Three APIs

  1. REST — operate the platform: integrations, connectors, messages, identity, alerts.
  2. Studio — /studio/* for workspaces, runs, tests, and milestones.
  3. Host (sirius.*) — what your mapping script calls while a message is in flight.

If the console can do it, these APIs can do it. The in-product agent and MCP server use the same contract.

Task-oriented walkthroughs live under How-to. The contract pages start at the REST API and the Studio API.