zend.shzend.sh
Provision
BYO is the zero-friction default: connect Google Workspace, Microsoft 365, or any SMTP/IMAP provider and start sending. Azure provisioning — ACS + Cloudflare DNS + Mailcow mailboxes — is available via the REST API and guided onboarding.
Bring your own
The fastest path to sending: point your Google Workspace, Microsoft 365, or any SMTP/IMAP inbox at zend.sh and you own everything that happens next — full mailbox rotation, health scoring, and warmup included.
Google Workspace
Connect via OAuth or app-password
Microsoft 365
Modern auth or app-password
Any SMTP / IMAP provider
Standard credentials, zero lock-in
Rotation + health scoring
Automatic across all connected mailboxes
Warmup — free forever
Enrolled immediately on connect
Or provision on Azure
When you need dedicated sending infrastructure, our provisioning API stands up the full Azure ACS stack, pushes Cloudflare DNS records, creates Mailcow mailboxes, and hands you API credentials. Available via the REST API and guided white-glove onboarding. You choose BYOA (your Azure subscription) or house-provisioned — you stay in control either way.
# Trigger provisioning — returns 202 immediately
# (optional) BYOA: pass azure_subscription_id to use your subscription
curl -X POST https://app.zend.sh/api/v1/domains/$DOMAIN_ID/provision \
-H "Authorization: Bearer $ZEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"rep_ids": ["<rep-uuid>"],
"mailboxes_per_rep": 3
}'
# → 202 Accepted { "status": "provisioning" }
# Poll for progress:
curl https://app.zend.sh/api/v1/domains/$DOMAIN_ID \
-H "Authorization: Bearer $ZEND_API_KEY"
# → { "status": "warming" } (dns_pending → verified → active → warming)Your domain, your nameservers
Point your domain's nameservers to Cloudflare — you registered it, you own it, we do not buy domains on your behalf. Once nameservers are active, we push SPF, DKIM, DMARC, and the ACS verification record, trigger verification, link the domain once verified, and enroll mailboxes in warmup and rotation.
Point nameservers to Cloudflare
Your registrar → Cloudflare NS (ns1/ns2.cloudflare.com)
DNS records pushed + ACS verification
SPF, DKIM, DMARC, MX, verification TXT — all auto-pushed
Domain verified → linked → active
Lifecycle: dns_pending → verified → active (finalize cron completes after DNS propagates)
Mailboxes enrolled in warmup + rotation
Warmup starts at 3 sends/day, ramps automatically
No. BYO inboxes is the zero-friction path — connect Google Workspace, Microsoft 365, or any SMTP/IMAP provider and start sending without any Azure involvement. Azure provisioning is optional: bring your own Azure subscription (BYOA) or use house-provisioned infrastructure, both accessed via the REST API and guided onboarding.
No. You own the domain and manage your registrar. Point your domain's nameservers to Cloudflare and we handle the rest — SPF, DKIM, DMARC, ACS verification, and mailbox creation. Your domain stays yours.
Not yet. Today, Azure provisioning runs via the REST API and guided white-glove onboarding — call POST /api/v1/domains/:id/provision and poll for status. BYO inboxes require no provisioning at all: connect and send. Talk to us for the guided onboarding path.
The API returns 202 immediately and runs asynchronously. The pipeline — ACS resource creation, Cloudflare DNS push, ACS verification, Mailcow mailbox creation — typically completes in a few minutes. A finalize cron completes the domain link after DNS propagates if verification does not complete in the initial window.