About transparency
We build an email product layer. We don't pretend to run the pipes ourselves. We show you all the data that matters—delivery, opens, clicks, bounces—so nothing is hidden. Here's what we do and what we rely on.
What we build
- • Our API — Your sending endpoint, request/response format, and authentication (API keys).
- • Our dashboard — Domains, templates, analytics, settings. The UI you use every day.
- • Our template system — Create, edit, and reference templates when sending.
- • Our analytics layer — Aggregation and display of send/delivery/open/click/bounce/complaint data.
- • Our domain onboarding — Guidance for DNS (SPF, DKIM, DMARC) and verification status.
- • Event tracking and webhooks (when shipped) — So you get events at your endpoints.
What we use for delivery
We use a trusted, large-scale delivery provider for the actual sending. We don't operate our own mail servers or claim to have a "global delivery network" that we built. That provider handles SMTP delivery, reputation, and scaling. We build the product on top—API, dashboard, templates, domain verification, and analytics that show you real events and status.
If we add more providers later (e.g. for redundancy or regional routing), we'll say so. We won't market "AI-powered deliverability" or "inbox guarantee" unless we actually implement and measure it.
What we don't claim
- • We don't claim to run our own global mail infrastructure.
- • We don't guarantee inbox placement (nobody honestly can without context).
- • We don't advertise "AI deliverability" or "smart routing" until we build and ship it.
- • We don't present roadmap items as if they're already live.
Why it matters
We want to be the email layer you trust because we're clear about what we do and what we don't. You get a clean product, control over your domains and templates, and an API you can build on—without the marketing spin. When we add features (warmup, suppression, multi-provider), we'll describe them honestly on the roadmap and in the product.