Skip to content

Changelog

What’s shipped, and what isn’t.

Mailtruss is in developer preview. This page is the source of truth for what works today.

Developer preview

The first public build: the API, the dashboard and the delivery trace.

  • Send, batch (up to 100), schedule (up to 30 days), reschedule and cancel through /api/v1
  • Idempotency keys, atomic quotas and per-key rate limits
  • Delivery trace and recorded event timeline for every message
  • Plain-language diagnosis for bounces, complaints, rejections, throttling and uncertain outcomes
  • Automatic suppression of hard-bounced and complaining addresses
  • Domains with DKIM, MAIL FROM and SPF records, re-checked automatically while pending
  • API keys (full access or sending only), shown once and stored hashed
  • API request logs with redaction, and an in-dashboard playground
  • Analytics by day and domain
  • Webhooks: signed payloads, retries with backoff, replay and delivery log
  • Templates: block editor or HTML, variables with fallbacks, versions and explicit publish
  • Organizations, projects, invitations and five roles
  • Contacts (add, CSV import), segments, and broadcasts with scheduling; every email carries its own unsubscribe link and a one-click List-Unsubscribe header
  • One sending tenant per organization, so one customer’s bounces and complaints are tracked on their own
  • No open or click tracking: no tracking pixels and no rewritten links in your email
  • Password reset, an account page, and a privacy policy, terms, acceptable use policy and data processing addendum
  • Analytics on public pages only after consent, never inside the dashboard

Status

Being explicit about what has and hasn’t been proven.

Sending pipeline, events, diagnosis
Verified
Checked in production during the developer preview: a message accepted by the API was delivered by the live delivery network, and a hard bounce came back with its reason and added the address to the suppression list by itself. Tested by sending to a handful of verified addresses and to the delivery network’s own test mailboxes.
Sending to any recipient
Partly tested
Enabled on 13 November 2026: the delivery network lifted its test-mode restriction, so mail can go to any address (shared limit: 50,000 messages a day, 14 a second). Not yet exercised with unverified real recipients.
Domain verification
Partly tested
The live check is built and the same records were verified for Mailtruss’s own sending domain. A customer adding a domain through the dashboard has not yet been run in production.
Per-customer sending tenants
Verified
A tenant was created and used for real sends in production. The automated tests do not call the provider.
Webhook delivery
Simulation only
Signing and retries are tested; deliveries have only been tested against test endpoints.
Contacts, segments and broadcasts
Partly tested
Tested end to end in simulation and in a browser, including the unsubscribe page. A broadcast has not yet been sent to real recipients. One send is limited to 5,000 recipients, and topics have no screen yet.
Billing
Not live
Built, but paid plans can’t be bought until payments are connected. Prices are provisional.
Google and GitHub sign-in
Not live
Written, not yet enabled or tested.
Inbound email, automations, SMTP relay
Not built
Not built.