Conduit
One neutral connector layer for every external system — banks, calendars, inboxes, SaaS — so provider names never leak into your product.
In the constellation
Conduit highlighted in the live map — hover or tap any node to explore.
Why it exists
Every product that touches the real world has to reach the same kinds of systems — banks, calendars, inboxes, SaaS tools. So every team rebuilds the same plumbing: OAuth flows, polling loops, webhook handlers, and a different payload shape to untangle for each vendor.
Worse, vendor names leak everywhere. Swap a bank or a calendar provider and you’re editing code across the whole app, because the integration was never isolated in the first place.
What Conduit is
Conduit is one neutral connector layer for every external system. It speaks a single connector contract: data comes in and gets normalized into one clean shape, actions go out and get routed to the right provider — and the provider’s name never escapes the config.
It’s the “Zapier layer,” built as real infrastructure instead of a side service. Concrete vendors live behind adapters; your product talks to abstract connectors and stays clean as providers come and go.
What it does
One connector contract
A single uniform shape for every external system — connect once, not once per vendor.
Inbound normalization
Messy third-party payloads mapped into clean, uniform internal records, deterministically.
Outbound dispatch
Uniform actions routed to the right connector and provider, with retry and idempotency built in.
Credential brokerage
Secrets held by reference, never on disk; scopes minimized; webhooks verified on the way in.
The line between judgment and machinery
AccelMars draws one hard line through every product: what an AI decides, and what runs deterministically. Conduit sits on the deterministic side.
Deterministic by design
- ▪ Transport in and out of external systems
- ▪ Payload normalization to a uniform shape
- ▪ Credential brokerage and webhook verification
Conduit moves and shapes data — it never decides what to sync. That judgment lives in the app above it, so the connector layer stays pure mechanism, and provider names stay locked in config.
Planned — designed, not yet built. It will be the connector layer beneath Abacus, Aide, and Megaphone, and the source of clean bank data for Ledger.
Open-core, like Anchor and Booster — the mechanical engine in the open.