//emails-for-saas providers ↗
← all providers
Templates

Foundation for Emails

Responsive email framework with Inky markup and Sass tooling.

overview

Foundation for Emails is a ZURB responsive HTML email framework. It provides a grid, common email UI patterns, Inky markup, Sass variables, templates, and an inliner workflow for teams that want production-ready HTML without hand-writing every table.

for SaaS product teams

A SaaS product sends on behalf of its customers, so the deciding factors are tenant isolation, whether suppressions can be scoped rather than global, and whether support can answer why one specific account did not receive one specific email. Lifecycle automation and transactional sending usually need to coexist.

Against trial expiry notices, dunning, onboarding sequences, and per-tenant transactional mail, Foundation for Emails covers none of the capabilities this audience leans on (multi-tenant support, event stream, the suppressions API, scheduling, and webhook coverage), so it fits only where those needs are genuinely absent.

  • Multi-tenant: No
  • Event stream: No
  • Suppressions API: No
  • Operating since: Not published
  • Scheduling: No
  • Best published rate per 1,000: Tiers not published in comparable form
  • Deliverability: Not applicable; template framework only.
  • Webhooks: No
  • Starts at: Free
deliverability

Not applicable; template framework only.

best for

Teams that want a mature, vendor-neutral responsive email framework.

not great for

React teams that want templates to share app component conventions.

pros
  • Email-specific grid, components, templates, and inlining workflow
  • Designed for Outlook and major email-client compatibility
  • MIT-licensed and vendor-neutral
cons
  • Older workflow assumes Node and Sass build tooling
  • Inky syntax is another template layer to learn
  • Less fashionable than React Email or Tailwind-based Maizzle in modern web teams

Features at a glance

API No
SMTP No
SDKs None
Webhooks No
Templates rich
React Email No
Batch send No
Scheduled send No
Suppressions No
Multi-tenant No
Inbound parsing No
Event stream No
Idempotency keys No
Dedicated IP No

Appears in rankings