Integrations

One governed path.
Every connector.

Connector calls run server-side through a governed invocation framework — idempotency keys, retries, SSRF-guarded egress, and capability gates. Slack is the reference connector today; a broader catalog is planned on the same framework.

Start building See the framework
Invocation Console
Worker connected
Invocations server-side · queued
inv_8f24c1 chat.postMessage delivered 12s
inv_8f24c0 chat.postMessage delivered 41s
inv_8f24bf db.read:orders delivered 1m
inv_8f24be chat.postMessage retrying 2m
inv_8f24bd db.read:orders delivered 4m
inv_8f24bc chat.postMessage queued 5m
Invocation Framework

Connectors are governed calls.
Not pasted API keys.

Every connector invocation goes through the same server-side path. Nothing is called from the browser, and no credential ever reaches user code.

01
Queued execution

Invocations run through a queued worker with idempotency keys and retries — duplicate sends are structurally prevented.

02
Guarded egress

Outbound calls pass SSRF-guarded egress validation. Connectors reach what they declare, nothing else.

03
Capability gating

Apps must hold an explicit capability to invoke a connector. No capability, no call — enforced at publish and at runtime.

Invocation Framework
Invocation Pipeline
app.call() governed SDK · server-side
capability check slack.chat.postMessage granted
enqueue idempotency_key dedupe
egress validation SSRF guard · allowlisted host
deliver retry 3x · exponential backoff
audit actor + outcome · append-only
Server-side invocations with idempotency keys and retries
SSRF-guarded egress validation on every outbound call
Connector instances store config and secret references, never browser secrets
Every invocation is audited with actor and outcome
Server-side execution · Idempotent · Capability-gated · Audited
Catalog Available Planned

A small governed set.
Not a marketplace.

PostgreSQL and Slack are live today. Database, API, and custom-source connectors are planned on the same governed framework — quality over count.

Catalog
Connector Registry
PostgreSQL
Available

Dedicated per-org database with server-side SQL execution.

Slack
Available

Reference connector — governed messages with idempotent delivery.

MySQL
Planned

External database connector on the governed framework.

MongoDB
Planned

Document store connector on the governed framework.

REST API
Planned

Generic HTTP connector with declared egress targets.

GraphQL
Planned

Typed API connector with capability-scoped queries.

Slack connector live · Catalog planned · Same framework for every connector
Integrations

Stop pasting API keys.
Start governing calls.

Connector credentials stay server-side. Invocations are queued, idempotent, and audited. Built for teams that treat third-party calls as production traffic.

Start building Explore the platform

Open beta · Slack connector live · Catalog planned

Server-side execution · Secret references · Capability gates · Audited invocations