FEATURES

A clear path from integration to operation.

Connect through SMTP or the Email API. Manage verified domains together and share your account’s active plan allowance.

Two ways in. One foundation.

SMTP

Keep your mail client. Authenticate with TLS and an API Key; public host, port and certificates depend on deployment.

Read integration docs

Email API

One recipient, explicit fields, standard HTTP. HTTP 202 means accepted; query status or receive Webhooks for later outcomes.

Read integration docs

BUILT FOR MULTI-DOMAIN TEAMS

Manage many domains in one place.

Stop setting up a separate email service for every project. Verify each sending domain once, keep keys and templates together, and share the quota of your active plan.

VERIFIED DOMAIN CLUSTER
Multiple verified domains
SPF · DKIM
app.example.com
mail.example.com
notify.example.org
auth.example.net
DOMAIN LIMIT
Set by plan
DNS RECORDS
TXT
DKIM KEY
RSA-2048

Verified domains, one console

Bind the sending domains of your products and client sites. Each domain must pass DNS verification before it can send, and the number of domains is capped by your plan.

Read the domain guide
ACCOUNT QUOTA
300
RESULT
202 + Webhook
Total quota300
Daily limit50 / 24h
Hourly limit10 / 1h
SMTP 465 / 587HTTP 202 Accepted + Webhook

One quota, three safeguards

All verified domains draw on the quota of your account's active plan, with total, daily and hourly limits enforced by the server. Acceptance is not inbox delivery — track the final status through the API or signed webhooks.

Read the SMTP guide

Multiple domains. One place.

Your domains, together

Manage sending domains for different products together. Each domain needs verification; the actual plan defines the domain limit.

Choose by sending allowance

Domains share the active plan allowance, with total, daily and hourly limits. Prices and entitlements come from the actual plan configuration.

Two protocols. Shared foundations.

Keep your SMTP client or use the standard Email API. Both share domain verification, API Key permissions and quota checks.

Templates and variables

Manage subjects, HTML and plain text. Send using template_id and string variables. HTML previews are isolated from the console.

Read integration docs

Status and events

Query by message_id or receive signed Webhooks. Acceptance is not inbox delivery. Callbacks may retry; verify signatures and deduplicate.

Read integration docs

Start sending from your own domains.

Create an account, verify a sending domain, and send over standard SMTP or the Email API.