How it works

Four things the platform handles, end to end.

01

Run every transfer from one dashboard

Define an exchange, connect the source and destination endpoints you own, and set a cadence. General Folders schedules each run and reports live status.

Duff Beer › Pipelines
Vance RefrigerationRequesting weekly inventory status
2h ago
Sterling CooperSending monthly billing log
Yesterday
Dunder Mifflin3 pipelines · Active
Sterling Cooper2 pipelines · Active
Vance Refrigeration1 pipeline · Pending setup
ops_daily_exportPostgres · Source
transfers_prodS3 · Destination
vendor_feedsSnowflake · Source
Daily operational feedops_daily_export
Partner update exporttransfers_prod
Reference data syncvendor_feeds
PartnerSterling Cooper
DirectionInbound
CadenceDaily, 06:00
Last runSuccess
Records12,840
Checksummatched ✓
Retries0
Dashboard
Host app
Integration service
Control plane · intent, policy, visibility
Public API
Metadata DB
Secret store
Queue
Enqueue job
Data plane · execution
Isolated workers
Source endpoints
Destination endpoints
02

Owned connections, isolated execution

Each organization connects only the endpoints it owns, with credentials held as secret references. Transfers execute in isolated workers, so payloads move through the run instead of pooling in storage.

  • The control plane stores policy, approvals, schedule, status, and audit.
  • The data plane runs isolated workers with scoped endpoint credentials.
  • Data moves through the workflow rather than into a long-term file pool.
03

Proof every transfer worked

Every run records counts, checksums, retries, and failure detail behind a permission-scoped audit trail, so you can confirm delivery and troubleshoot without exposing raw data.

  • Each run returns status, events, failure details, and webhooks.
  • Record counts, checksums, and retries confirm each transfer.
Daily operational feed Success
DirectionInbound
CadenceDaily, 06:00
Last runSuccess
Records12,840
Checksummatched ✓
Retries0
POST /v1/exchanges
{
  "partner_org_id": "org_partner",
  "source_endpoint_id": "ep_source_db",
  "source_dataset": "operations.view_daily_export",
  "schema_id": "schema_operational_feed_v1",
  "cadence": "daily",
  "timezone": "America/Los_Angeles",
  "retry_policy": { "max_attempts": 3 }
}

→ 201 Created
{
  "exchange_id": "ex_7d91",
  "status": "pending_partner_approval",
  "partner_inbox_item_id": "in_42c1",
  "audit_event_id": "evt_9f8e7d"
}
04

API-first, built to embed

Every exchange is an API object with status webhooks. Create and track transfers from the API, or embed the setup flow so your customers never leave your product.

  1. Create an exchange with partner, endpoint, dataset, schema, and cadence.
  2. Record the partner approval state.
  3. Execute each run through isolated workers.
  4. Return status, failure details, audit events, and webhooks.
  5. Monitor API usage and exchange activity in the dashboard.
Get started

A governed way to exchange
operational data

Skip the SFTP folders, email handoffs, and one-off scripts.