MarkRelay
Documentation navigation

Production Checklist

Use this checklist before launch and during regular operation to keep your MarkRelay workspace reliable, secure, and ready for your team.

Before launch

  • Use a production hostname with HTTPS.
  • Verify Cloudflare Email Routing and outbound sending for each domain.
  • Publish SPF, DKIM, and DMARC records and confirm they pass.
  • Test inbound mail, Webmail replies, API sending, and attachments.
  • Send webhook and broadcast tests for the workflows you will use.
  • Invite team members and review their mailbox assignments.

Protect access

  • Enable strong authentication for your Cloudflare account.
  • Keep MarkRelay administrator access limited to trusted operators.
  • Use a separate scoped API key for every application or agent.
  • Store authentication and webhook secrets in a secret manager.
  • Disable users and credentials promptly when they are no longer needed.

Watch the workspace

Review these areas on a schedule that matches your sending volume:

  • Send and receive logs for recurring errors;
  • broadcast progress, bounces, replies, and unsubscribes;
  • webhook health for integrations;
  • D1, R2, Worker, and Queue usage in Cloudflare;
  • mailbox and stored-object growth in the admin dashboard.

Plan for growth

MarkRelay does not meter your number of messages, members, domains, or mailboxes. Your practical capacity follows the Cloudflare services and account plan behind your installation. Review Cloudflare usage as your audience, storage, or automation volume grows.

Broadcasts support up to 10,000 recipients per campaign. Compose and API sends support up to 20 attachments with a combined size of 25 MB.

Maintain your deployment

  • Back up important D1 and R2 data according to your business requirements.
  • Review release notes before applying updates.
  • Test major updates in a separate Cloudflare deployment when appropriate.
  • Keep domain authentication, consent records, and suppression handling current.
  • Repeat an inbound and outbound test after DNS, domain, or binding changes.

See Deployment for installation and Deliverability for sender setup.

← PreviousDeliverabilityNext →Email Editor