Application email automation for SaaS teams
SkyMailr

Application email

Run application email from one control plane

Manage senders, domains, templates, workflows, and message events for every app and tenant—account-aware, API-first, with visibility for your team and your customers.

Tenants

  • acme-prodActive
  • acme-stagingPaused

Domain

mail.acme.com

DKIM SPF Checking

Template

collaborator_invite

Workflow

onboarding_drip

Multi-tenant architecture API-first Domain verification Templates + workflows Message events Account-level controls

Core platform

Everything you need to run product email in one place—without wiring SMTP by hand in every service.

Accounts & tenants

Billing, members, and quotas per account; tenants for environments or product surfaces.

Domains & senders

Attach domains per tenant and see DNS readiness before mail leaves your stack.

Templates & approvals

Version templates, approve changes, and call stable keys from your application code.

Workflows & events

Multi-step flows with delays and branches; correlate sends with events in your systems.

How it fits together

Account structure, sending readiness, template lifecycle, and automation—shown the way your team sees them in the product.

Accounts & tenants

Model customer orgs and split apps or environments under one account. Usage and API keys stay scoped per tenant.

Account · northwind
Tenant · billing-api
Tenant · storefront

Sending domain

notify.northwind.io

Last check · 2m ago

Aligned

Sending domains & readiness

See whether DNS and sender configuration are ready before production traffic uses a domain.

Templates & approvals

Iterate on copy and variables, route approvals, then promote—your app keeps calling the same template keys.

password_reset_v2 Awaiting approval
Workflow · trial_expiry
enroll → wait 7d → send → branch

Workflows & events

Chain steps with timing and branches; tie outcomes back to message IDs your support and analytics tools already use.

Developer API

Trigger app email with tenant-scoped API keys and reusable template keys.

Example: POST /api/v1/messages/send-template/ with templates such as collaborator_invite or welcome_email.

import requests

resp = requests.post(
    "https://api.example.com/api/v1/messages/send-template/",
    headers={"Authorization": "Bearer YOUR_TENANT_API_KEY"},
    json={
        "to": "colleague@example.com",
        "template": "collaborator_invite",
        "variables": {"inviter": "Ada", "org": "Northwind"},
    },
    timeout=30,
)
print(resp.status_code, resp.json())

Use cases

Common application email your product team already owns—centralized and observable.

Welcome emails

First-run and signup confirmation from the same template keys in every environment.

Email verification

One-time links and verification flows with clear send and delivery status.

Password resets

Security-sensitive mail with approvals before production content changes.

Collaborator invites

Team and partner invitations tied to tenant context and message history.

Billing & receipts

Invoices and payment notices with explicit sender domains per tenant.

Product notifications

Usage alerts, digests, and in-product email triggered from your backend.

Onboarding sequences

Time-based steps and exits for new accounts—without a separate blast-email tool.

Internal ops

Staff notifications and handoffs with the same pipeline as customer-facing mail.

Old way vs SkyMailr

Move from ad-hoc plumbing to a single place for application email operations.

Old way

  • SMTP credentials scattered across services and repos
  • Template changes shipped with application code
  • Little shared visibility into sends, failures, or per-tenant volume
  • Domain and sender setup easy to get wrong under pressure

SkyMailr

  • Tenant-scoped API keys and explicit sending identities
  • Managed templates with approvals before production use
  • Domain and sender readiness surfaced in one place
  • Message events visible to product teams and staff alike

Customer portal & staff portal

Two interfaces on the same platform: self-service for customer accounts and oversight for your team.

Customer portal

Web app under /app/

  • Accounts, members, and tenants
  • Sender and domain setup
  • Templates and workflows for your apps
  • Message history scoped to the signed-in account

Staff portal

Cross-account access for your team

  • Cross-tenant operations and support
  • Suppressions and incident visibility
  • Oversight for templates and workflows
  • Provider health and webhook intake

Readiness & transparency

SkyMailr helps you see sender and domain readiness, authentication alignment (SPF, DKIM, DMARC), and message outcomes—so you fix configuration instead of guessing. We do not guarantee inbox placement; your provider and content still matter.

  • Visible checks before you scale sends on a domain
  • Suppression and delivery signals surfaced in the product
  • Event visibility for operations and support—not a deliverability scorecard

Pricing

Plan limits match what the product enforces—start free and scale when you are ready.

Free

$0

For evaluation and light use

  • Up to 1 connected app
  • Up to 2 sending domains per app
  • 500 sends / mo
  • 10 templates · 5 workflows
  • 3 API keys · 5 members
Start free

Growth

Custom

Higher limits and rollout support

  • Up to 25 connected apps
  • Up to 100 sending domains per app
  • 500,000 sends / mo
  • 500 templates · 200 workflows
  • 100 API keys · 100 members
Contact sales

Run app email like infrastructure

Set up accounts, domains, approved templates, and workflows in one place—then call the API from your services with tenant-scoped keys.

Replace the contact address with your production support email when ready.