Trust & methodology

Publish the test conditions, not a hero number.

Infrastructure claims are only useful if you can see what was measured. This page records the acceptance benchmark we ran, the limits of that test, and the live endpoints you can inspect yourself.

Measured benchmark

API acceptance latency

14 November 2026 · direct API · suppressed recipient

RunRequestsp50p95p99Errors
Concurrency 810088 ms251 ms282 ms0
Concurrency 16200186 ms1,697 ms2,267 ms0

Acceptance latency is load-dependent. At higher concurrency, the usage-ledger row becomes a contention point and p95 rises sharply. That is a known scaling limit, not something we hide behind a single number. The target is to remove that contention before claiming higher sustained capacity.

Method

  • • 100 or 200 authenticated POST /v1/emails requests.
  • • Unique idempotency key per request.
  • • Recipient added to the suppression list, so no SMTP delivery was attempted.
  • • Direct loopback to the API, excluding Cloudflare and Caddy latency.
  • • 6 vCPU, 11 GiB RAM, PostgreSQL and Redis on the same host.
  • • Measured from request start to the 202 response.

What this does not prove

  • • Inbox placement or receiver filtering.
  • • Sustained throughput or multi-node capacity.
  • • SMTP delivery time after acceptance.
  • • Performance under a specific customer’s traffic mix.
  • • Third-party validation. This is our benchmark, with our method.

Inspect the live service

The public status page and metrics endpoints expose component health, queue depth, webhook backlog, outbox lag and worker heartbeat. They are aggregate-only and contain no tenant content.

Customer evidence

Transmitly is early. We do not publish customer names, logos or quotes without permission, and we do not invent proof. References can be discussed during a serious evaluation with the customer’s consent.

Security and operations

Signed webhooks, TLS on inbound SMTP, DKIM signing, SPF/DKIM report checks, scoped API keys, audit logging and automatic content retention are summarized in the security & trust center. Procurement documents, DPA, SCC addendum and subprocessors are available from there. Report issues through contact.

Test it against your own workload.

Bring a verified domain and a real sending profile. We will show the acceptance and delivery evidence before you move volume.