Conduit View on GitHub
Open source · MIT licensed

Stop reinventing OAuth for every API you integrate.

Conduit is a self-hosted integration gateway for Slack, GitHub, Stripe, and more: the boilerplate every team writes once per API, done right, once.

Try it in 30 seconds View source
No signup·No API keys required to try·Runs on your infra

Built for the integration work everyone re-does

Four situations Conduit is built to remove, straight from the boilerplate you'd otherwise write yourself.

🔐

Customers connect their own Slack/GitHub/Stripe

Point customers at Conduit's install endpoint. It runs the OAuth flow, refreshes tokens automatically, and encrypts credentials at rest, so you never touch a raw token.

⏱

Rate-limited APIs, without hand-rolled backoff

Conduit's client already understands Slack's Retry-After header and GitHub's X-RateLimit-* headers, with exponential backoff and jitter for everything else.

📡

Inbound webhooks, verified correctly

HMAC-SHA256 signature verification, done once in the SDK, instead of once per integration you build.

🩺

Know when a provider's API quietly changes

A background drift detector probes each connector, diffs the response shape against a stored baseline, and flags it before it silently breaks something downstream.

What's actually in the box

Unified connector interface

One Go interface: AuthConfig, Endpoints, HandleWebhook. Slack, GitHub, and Stripe implement it today; add your own the same way.

OAuth2 + API-key auth

Automatic token refresh on expiry or 401. Credentials encrypted at rest with AES-256-GCM.

Provider-aware rate limiting

Exponential backoff with jitter, tuned to each provider's actual rate-limit response format.

Drift detection

Scheduled probes diff live responses against a stored baseline schema, and alert on change.

Observability built in

Prometheus metrics at /metrics; an auto-generated OpenAPI spec and Swagger UI at /docs.

Dashboard UI

A no-build-step dashboard for browsing the catalog, managing instances, and executing endpoints directly.

From clone to executed request, in five steps

  1. 1
    Clone and run. docker run or go run ./cmd/gateway, boots with a built-in mock provider, no API keys needed.
  2. 2
    Open the dashboard. Browse the connector catalog at localhost:8080/ui/.
  3. 3
    Install a connector. API-key connectors (like Stripe) prompt for a key; OAuth2 connectors (like Slack, GitHub) redirect through a consent flow.
  4. 4
    Execute an endpoint. Pick the instance and endpoint, send the request, see the live response.
  5. 5
    Swap in real credentials. Point at real provider OAuth apps and API keys when you're ready to go beyond the mock demo.

Why self-hosted instead of Nango, Merge, or Paragon

Those are good products with far more pre-built connectors than Conduit has today. The tradeoff is control and cost.

Pick a hosted platform if…

You need broad, ready-made connector coverage right now and don't want to run infrastructure yourself.

Pick Conduit if…

You specifically need Slack/GitHub/Stripe (or want to add your own connector against a plain Go interface), and would rather not send customer credentials to a third party or pay per API call.

Try it now

No signup. No API keys. Runs entirely on your machine.

Terminal 
git clone https://github.com/navyabijoy/conduit-go.git
cd conduit-go
docker build -t conduit .
docker run -p 8080:8080 -p 8081:8081 conduit

or without Docker: go run ./cmd/gateway

View on GitHub Read the docs