Built to protect
every brand's data.
Security is built into the foundation: encrypted credentials, a hardened API boundary, scoped access, and tenant isolation.
Security fundamentals
Encrypted credentials
Provider passwords, tokens, and webhook secrets are submitted only to dedicated endpoints and encrypted server-side. They are never returned by the API or bundled into browser code.
A hardened API boundary
The API can only address an explicit allow-list of tables and fields. Secret, credential, event, and generated-version tables are deliberately unreachable.
Scoped access
Granular roles, per-brand membership scopes, and live/test API keys with per-key scopes and expiry keep access least-privilege by default.
Permission-first by design
Bounce, complaint, and unsubscribe processing can never be turned off — consent enforcement is structural, not a setting.
Tenant isolation
Every record is tenant- and brand-scoped, so data never crosses between the brands or organizations that own it.
Operational visibility
Incidents, risk events, and background jobs are tracked, so problems surface instead of hiding.
Bring your provider.
Keep your brands distinct.
Start today.
Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.