Foundation for Emails
Responsive email framework with Inky markup and Sass tooling.
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.
Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.
Against high-frequency programmatic sends where a missed delivery is a product failure, Foundation for Emails covers none of the capabilities this audience leans on (idempotency keys, webhook coverage, event stream, the suppressions API, batch sending, and SDK breadth), so it fits only where those needs are genuinely absent.
- Idempotency keys: No
- Webhooks: No
- Event stream: No
- Operating since: Not published
- Suppressions API: No
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: No
- SDKs: None
- Deliverability: Not applicable; template framework only.
Not applicable; template framework only.
Teams that want a mature, vendor-neutral responsive email framework.
React teams that want templates to share app component conventions.
- › Email-specific grid, components, templates, and inlining workflow
- › Designed for Outlook and major email-client compatibility
- › MIT-licensed and vendor-neutral
- › 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 |