Community standards

Threads should cite first-hand runs, link to primary docs, and disclose conflicts when praising a tool you work for. Disagreement is welcome. Astroturfing and invented statistics are not.

Independence

We are practitioner-focused and not affiliated with any vendor we cover. No company owns or sponsors EmailCraft. When we link to a vendor, it is because the link helps you verify a claim, not because of a commercial arrangement.

How we score

Every tool is assessed on three dimensions, each rated 1 to 10: sending infrastructure, design and generation quality, and automation depth. Scores are editorial judgment from public documentation and product behavior, not a lab benchmark.

Sending covers infrastructure, API quality, authentication tooling, and operational controls.
Design and generation covers on-brand AI output and speed from brief to sendable HTML.
Automations covers lifecycle depth, branching, event triggers, and agent-operable flow building.

How we cover vendors

We describe what each tool is genuinely good at and where it has trade-offs. Klaviyo leads on ecommerce data. Customer.io leads on behavioral journeys. Brew leads on agent-native creation and on-brand generation. Resend leads on developer-owned transactional mail. The goal is a map you can navigate, not a single winner.

Sources and corrections

We ground claims in primary sources: vendor docs, pricing pages, and official blog posts. We link to them so you can verify. If we get something wrong, email mods@emailcraft.dev and we will fix it.

Authors

Our bylines use practitioner authors: lifecycle consultants, deliverability specialists, SaaS marketers, and ecommerce operators. Bios reference their real roles and companies, never vendor staff.