Howdy

Provider-agnostic email marketing

Route every send to the provider that delivers.

Connect Amazon SES, SendGrid, Postmark — any sender you like — and Howdy splits, balances, and fails over your campaigns across them automatically. Cost, health, and inbox placement make the call. You stay in control.

Start free See routing in action

Free developer plan · 2,000 orchestrated emails/mo · No credit card

Bring the providers you already trust — or all of them

  • Amazon SES
  • SendGrid
  • Postmark
  • Mailgun
  • Resend
  • Brevo
  • Mailjet
  • SparkPost
  • MailerSend
  • Elastic Email
  • Mandrill
  • Generic SMTP

Why Howdy exists

Your ESP owns your templates, your list, and your reputation. That's the bug.

Bundled platforms couple the tools you love to sending infrastructure you can't control. Howdy decouples them — so a vendor problem is a routing decision, not a quarter-long migration.

Lock-in by design

Switching ESPs means rebuilding templates, automations, suppressions, and analytics. So nobody switches — even when they should. With Howdy, all of that stays put while delivery vendors come and go.

One reputation, one point of failure

A blocklisted IP or a provider outage takes your whole program down with it. Howdy scores provider health continuously and fails over in seconds — automatically.

Paying for contacts twice

Contact-based ESP pricing bills you for storing people you already pay a provider to reach. Howdy charges for orchestration and intelligence — and never marks up sending.

Routing engine

Route email like traffic, not like a mail merge.

Thirteen policy scopes, from organization default down to a single automation step. Set it per campaign, per stream, per recipient domain — or let health decide.

Weighted split

70% SES, 20% SendGrid, 10% Postmark — deterministic per recipient, stable across sends.

Health failover

Circuit breakers pause a degrading provider and re-open with canary traffic.

Mailbox-aware

Gmail via SES, Outlook via Postmark — route by recipient domain performance.

Cost-aware

Cheapest provider that still clears your deliverability thresholds.

Warmup plans

New domain or IP? Howdy ramps volume gradually on a schedule you approve.

Canary sends

First 5% through the new provider. Evaluate. Then open the floodgates.

Stream isolation

Transactional never shares a reputation pool with promotions. Ever.

Deliverability autopilot

When a provider has a bad day, your campaign doesn't.

Howdy scores every provider connection on twenty-plus live signals — deferrals, bounces, complaints, API latency, blocklist status, webhook lag, quota headroom. When a score drops below your threshold, traffic shifts before your open rate feels it.

  • Automatic failover chains: primary → secondary → tertiary
  • Pause, throttle, or rebalance any queue — per campaign, provider, or domain
  • Recovery canaries re-test a paused provider before full traffic returns

Provider-normalized analytics

Compare providers like for like.

Every provider speaks a different webhook dialect. Howdy normalizes them into one event schema — accepted, delivered, deferred, bounced, complained, opened, clicked — so you can finally answer: who actually delivers my email?

  • Delivery, engagement, and cost — side by side, per provider
  • Mailbox-domain breakdowns: Gmail, Outlook, Yahoo, Apple
  • Cost per delivered, per open, per click — not per "send"
Delivered rate · last 30 days
Amazon SES99.2%
Postmark99.0%
SendGrid97.4%
Mailgun96.1%
Best performing provider by mailbox domain
MailboxBest routeDelivered
GmailSES99.4%
OutlookPostmark99.1%
YahooSES98.7%

AI campaign builder

Paste a URL. Get a campaign.

Point Howdy at a product page, changelog, or launch post. It extracts your brand kit, drafts the newsletter, writes subject-line variants and the plain-text version, and recommends a segment — then a human approves before anything sends.

  • URL-to-newsletter, prompt-to-campaign, URL-to-drip sequences
  • Compliance QA: links must resolve, prices come from the source, unsubscribe present
  • Every generation stores its prompt, sources, and model — fully auditable
Subject A Atlas is here — 30% lighter, twice the range
Subject B Meet Atlas: the update your commute asked for
Links resolve Unsubscribe present Prices match source

Everything else you'd expect

All the marketer table stakes. None of the ceiling.

Visual email designer

Drag-and-drop blocks, brand kits, dark-mode preview, accessibility and spam QA.

Automations canvas

Welcome series, re-engagement, abandoned cart — with node-level analytics and replay.

Segmentation

Fields, tags, engagement, revenue events — plus a SQL-style builder for power users.

A/B/n testing

Subjects, content, send time, and even providers — pick winners on clicks or revenue.

Transactional streams

Same platform, separate reputation pools, suppression logic, and routing policies.

Forms & preference center

Double opt-in, topics, frequency caps, pause-for-30-days — consent logged.

Send-time optimization

Deliver in each recipient's timezone at their historical engagement peak.

Imports without drama

Dedupe, invalid and disposable detection, risk scoring, and quarantine review.

Built for engineers too

A sending control plane, not a black box.

Under the hood Howdy is a .NET, REST, Kubernetes-native delivery pipeline with durable PostgreSQL-backed work and adaptive per-provider rate limiting. On the surface, it's one clean API.

  • One webhook schema across every provider — no more twelve parsers
  • Idempotent sends with uncertain-state reconciliation. No duplicate blasts.
  • Pause, resume, retry, or cancel — per campaign, provider, domain, or globally
  • Provider credentials envelope-encrypted; never logged, never exported
1M+emails/hour per tenant
4msp99 route decision
12providers on day one
send-campaign.sh 
curl -X POST https://api.howdy.app/v1/campaigns/cmp_9f3k/send \
  -H "Authorization: Bearer hd_live_…" \
  -H "Idempotency-Key: launch-jul-11" \
  -d '{
    "routing_policy": {
      "strategy": "weighted",
      "providers": [
        { "connection": "ses_primary",   "weight": 70 },
        { "connection": "sendgrid_eu",   "weight": 20 },
        { "connection": "postmark_warm", "weight": 10 }
      ],
      "failover": ["mailgun_standby"],
      "health_rules": { "pause_on": "complaint_rate > 0.1%" }
    }
  }'

Pricing

Pay for orchestration. Never for sending markup.

You pay your providers directly, at their prices. Howdy charges for the routing, analytics, automation, and AI on top — starting at free.

Developer

$0

Validate the abstraction

  • 500 contacts · 2k emails/mo
  • 1 provider connection
  • 7-day analytics
  • 25 AI generations/mo
Start free

Starter

$29/mo

Small newsletters & startups

  • 10k contacts · 50k emails/mo
  • 2 providers · manual failover
  • 30-day analytics
  • 250 AI generations/mo
Choose Starter

Most popular

Growth

$99/mo

SaaS & e-commerce teams

  • 50k contacts · 250k emails/mo
  • 5 providers · weighted & quota routing
  • 90-day analytics · A/B tests · automations
  • 1k AI generations/mo
Choose Growth

Scale

$299/mo

High-volume senders

  • 250k contacts · 1M emails/mo
  • 15 providers · health & mailbox routing
  • 365-day analytics · warmup policies
  • 5k AI generations/mo
Choose Scale

Enterprise

Custom

Agencies, media, regulated teams

  • SSO/SAML · audit logs
  • VPC / private cluster
  • Custom policies & connectors
  • Dedicated CSM + SLA
Talk to us

Overages from $0.10 per 1,000 orchestrated emails. Provider sending costs are always billed to you by the provider — Howdy adds nothing on top.

Say howdy to your subscribers.

Connect a provider, import your list, and route your first campaign in under an hour.

Start free Book a demo