Integrations

Integrations

RunwayCtrl sits at the tool-call boundary and governs write-side effects.

Every governed write produces a receipt (attempt record) and optional trace linkage. Start with one workflow, expand as needed.

Initial Support
Planned
01 / Supported

Initial support

These integrations are available in the design partner preview. Each integration governs specific write actions with policy enforcement and receipts.

02 / Planned

Coming next

Slack

Planned

Govern message and notification writes with stable action identity and bounded retries.

Message sendChannel postUpdate message
03 / Adoption

How you adopt it

RunwayCtrl integrates at the tool-call layer. Wrap your existing tool calls, define policies, and start collecting receipts.

1

Wrap tool calls

Use the preview SDK wrapper around your existing tool calls. The wrapper intercepts the call before execution.

2

Define ActionKeys + policies

Specify how to compute the ActionKey and what policy rules apply (retry budget, lease scope, rate limits).

3

Observe receipts + traces

Attempt records are stored in the ledger. Traces can export to your observability stack when enabled.

04 / Get started

Join design partners

Bring one real workflow (PagerDuty or GitHub). We'll help define ActionKeys + policies. You get early builds, a shared Slack channel, and direct input on priorities.