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.
An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.
Against inbound parsing into tool calls and model-generated sends that must not duplicate, Foundation for Emails covers none of the capabilities this audience leans on (inbound parsing, idempotency keys, webhook coverage, event stream, batch sending, SDK breadth, and multi-tenant support), so it fits only where those needs are genuinely absent.
- Inbound parsing: No
- Idempotency keys: No
- Webhooks: No
- Operating since: Not published
- Event stream: No
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: No
- SDKs: None
- Multi-tenant: No
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 |