RunlineRunline
Platform & SDKConnections & Integrations

Connections & Integrations

How Runline reaches external systems, through two very different doors.

Runline talks to two very different kinds of external system, and they go through two very different doors. Keeping them separate is a deliberate trust-boundary decision (ADR-019).

Two doors, on purpose

  • Regulated systems (banking cores) go through The Grid: auth → kill-switch → rate-limit → audit → proxy. Nothing regulated ever routes through a third-party integration broker.
  • Third-party SaaS tools (Linear, GitHub, eventually per-CU tools) go through Connections: a Nango-backed, fully brokered integration layer.

How Connections works

Three parties, one clean split:

  • Nango owns execution. OAuth flows, API-key auth, token refresh, unified calling. Runline builds none of it (it's already SOC 2 Type II / HIPAA / GDPR certified).
  • Identity owns authorization. A Connections plugin on identity holds the grant model: a connection is owned by an organization, team, or user. Org/team-owned connections carry implicit trust for Runners acting for that org; user-owned connections have zero implicit grants, ever.
  • Fully brokered. No Runner or service ever receives a Nango credential or connection id. They call identity; identity checks the grant, calls Nango server-side with the one Nango key it alone holds, and returns the result, not a reference.
execute holds the only Nango key returns the result, not a credential Runner / Service Identity (checks grant) Nango Third-party API

Why brokered? Not because the connection id is secret (it's just a correlator, useless without a credential). Because a directly-usable id makes the grant model advisory. Brokering makes it enforced by construction.

Internal events are a different job

Connections is for reaching out to external tools. Moving events between Runline's own services is Circuit, the org nervous system. External third-party payloads deliberately do not ride Circuit's first-party surface.

Status

Proposed (ADR-019). First real consumer: an internal Linear activity feed for Console. The Cloud vs. self-hosted Nango question gets revisited before any CU-client credential is ever provisioned, not after.

Canonical reference

  • ADR-019 · Connections, the Nango broker architecture
  • Circuit & Integrations · Integrating with Circuit
  • Platform Services · Identity

Logging & Telemetry

What every authenticated action records: telemetry, security alerts, audit.

Banking Cores

Regulated core systems, reached only through the Grid.

On this page

Two doors, on purposeHow Connections worksInternal events are a different jobStatusCanonical reference