Helo Review (2026): Pricing, Features & Honest Verdict

TLDR

Helo is a new email API and SMTP service with one plan: $5 a month plus $0.00035 per email, unlimited domains and users included. It undercuts Postmark and Resend at most volumes, but it is days old. Best for: SaaS teams and platforms sending for their users. Price: from $5/mo, free plan no. Rating: 7.5/10.

What is Helo?

We found Helo on Product Hunt, where it launched on 30 September 2026. It’s a transactional email service for developers: your app hands it password resets, receipts and sign-up confirmations through an HTTP API or SMTP, and Helo delivers them. It also sends broadcasts, so a product update to your whole list can go out through the same account.

The company behind it is Helo Ehlo LLC, a small, self-funded team. Its about page says most of the people on it previously worked on Postmark, one of the best-regarded transactional email services. That history shows. The promise is the same one Postmark built its name on (fast, reliable delivery of the emails people are waiting for), with a much simpler price list and a strong focus on platforms that send email on behalf of their own customers.

What Are Helo’s Key Features?

Separate infrastructure for transactional and broadcast mail

Helo runs transactional and broadcast email through separate endpoints, separate queues and separate groups of sending IPs. The docs give the reason in one line: if a newsletter gets flagged as spam, it shouldn’t drag your password resets down with it. You pick the mail type per request (POST /send/transactional or POST /send/broadcast), and Helo routes it. Broadcasts are paced on purpose. The docs estimate about 15 minutes for 10,000 recipients and about two hours for 100,000.

Channels for isolated sending

Channels are Helo’s unit of separation. Each one has its own stats, its own reputation, its own suppression list and its own tracking settings, and credentials can be scoped to a single Channel. Helo watches each Channel and raises a warning when bounces pass 3 percent or spam complaints pass 0.08 percent, with critical alerts at 5 percent and 0.1 percent. A Channel that keeps crossing those lines can be suspended without touching the others on the account.

Tools for platforms sending on behalf of others

This is where Helo is most opinionated. If you run a booking tool, a newsletter builder or a fundraising app, you can give every customer their own Channel and their own authenticated domain, then pull per-customer stats through the statistics endpoints. The docs include a long guide to automating customer DNS by delegating a subdomain to nameservers you control at a major DNS host, so DKIM and Return-Path records stop being a support ticket for every new customer.

Sandbox Channels, webhooks and five SDKs

A Sandbox Channel processes messages exactly like a live one, fires webhooks and supports simulated bounces, but never delivers to a real inbox. Webhooks cover 13 events, from accepted and delivered through bounces, complaints, unsubscribes and DNS verification results. Official SDKs cover five languages, among them JavaScript, Python, Go and C#, and SMTP listens on ports 587, 25, 2525 and 465. Open and link tracking are off by default, and Helo says it filters out automatic image prefetches so open rates aren’t inflated.

What Is It Like to Use Helo?

We read the docs and the published OpenAPI spec rather than sending production traffic, and the docs are a good sign. They’re compact, opinionated and honest about limits. The sending guidelines advise you to warm up new domains over days or weeks, to bring your old suppression list across before your first send, and to add your own DMARC record because Helo won’t create one. That’s the voice of people who have handled deliverability support before.

New accounts start in Test Mode. You can send up to 1,000 emails, but only to addresses on domains you have verified in Helo, and tracking is switched off. That’s enough to test an integration against your own inbox, not enough to send anything to a real user. To leave Test Mode you verify a domain and start the paid subscription.

The API design is careful: idempotency keys on every send, batch sending for transactional mail, and broadcasts treated as stored objects you can query afterwards for failures and suppressed recipients. Suppressions follow a clear priority order, so a subsequent spam complaint upgrades a manual suppression rather than overwriting it with something weaker. The status page shows 100 percent uptime for the app, API and SMTP over the roughly three months it covers, which is a short window.

Where Does Helo Fall Short?

There is no free plan. Helo is upfront about why (free sending attracts spammers), but it still means a side project sending 500 emails a month pays $5.18, while Resend and Postmark both have free tiers. If your volume is tiny, Helo is the more expensive choice.

The feature list is narrower than the incumbents’. The docs and the OpenAPI spec show no inbound email processing, no dedicated IPs, and no stored template library; templates are passed inline with each request. Link tracking runs through Helo’s own tracking domain for now, with custom tracking domains listed as coming soon. Stats history is limited too: hourly stats cover 24 hours and the per-day stats endpoint covers 90 days.

Sandbox messages are billed as normal usage, which is unusual for a test environment. The privacy policy says customer data is stored and processed on servers in the United States, with no EU region mentioned. And the terms are customer-unfriendly in the usual ways: purchases are non-refundable except where law requires, liability is limited to three months of fees, and disputes go to binding arbitration under Pennsylvania law.

Finally, Helo is days old. The team’s track record is real, but the company has no public sending history, no published deliverability numbers and only a few months of uptime data. Moving a critical password reset flow onto a brand new provider is a risk you should size carefully.

How Much Does Helo Cost?

Helo starts at $5 per month, plus $0.00035 per email. That’s the whole price list. There are no tiers, no volume commitments and no overage fees. Unlimited users, domains and webhooks are included on the single plan. The $5 platform fee is charged in advance each month, and the emails you sent are charged in arrears at renewal. Helo can raise prices with 30 days’ notice under its terms.

The maths is easy. 10,000 emails cost $8.50, 100,000 cost $40, and 500,000 cost $180. Because there are no tiers, 82,000 emails cost $33.70 rather than the price of the next bundle up. We checked these against the per-email rate and they hold.

Against the competition, Helo wins most of the middle. Postmark’s Basic plan is $15 a month for 10,000 emails, with extra emails at $1.80 per 1,000, so Helo is roughly half the price at that volume. Resend’s Scale plan is $90 a month for 100,000 emails, against Helo’s $40.

The claim that Helo is cheaper at almost every volume needs care, though. Resend’s Pro plan is $20 a month for 50,000 emails, while Helo charges $22.50 for the same 50,000. And Amazon SES charges $0.10 per 1,000 emails with no platform fee, which is $10 for 100,000. SES is far cheaper if you’re happy to build the dashboards, suppression handling and support yourself.

Who is Helo Best For?

Use Helo if you run a SaaS product or a platform that sends email for its customers, you send somewhere between 10,000 and a few million emails a month, and you want per-customer isolation and stats without paying for a higher plan. It also suits teams that want one predictable invoice line rather than a tier they have to guess in advance.

Skip Helo if you send a few hundred emails a month and want it free, if you need inbound email parsing or a dedicated IP today, or if your data has to stay in the EU. Skip it too if your company won’t put a critical email flow on a vendor without years of operating history.

Best Helo Alternatives

Postmark

The established transactional specialist and the obvious comparison, given where Helo’s team came from. A free plan covers 100 emails a month, Basic is $15 a month for 10,000 emails and Pro is $16.50 with inbound processing and longer data retention. Choose it if you want a long track record and inbound email, and accept paying more per email.

Resend

A developer-first email API with a generous free plan of 3,000 emails a month (100 per day), Pro at $20 a month for 50,000 emails and Scale at $90 for 100,000. Dedicated IPs are an add-on at $30 a month. It’s cheaper than Helo for very small senders and at exactly 50,000 emails, and more expensive almost everywhere else.

Amazon SES

The raw cost floor: $0.10 per 1,000 outbound emails with no monthly fee. It’s the right pick for high-volume senders with engineers to spare, since you build bounce handling, per-customer separation and reporting yourself on top of AWS.

Final Verdict: Is Helo Worth It?

Yes, for the right team. Helo takes the parts of transactional email that experienced teams care about (separate infrastructure for different mail types, per-customer isolation, honest docs, human support) and prices them at $5 plus a fraction of a cent per email. For a SaaS app or platform sending tens or hundreds of thousands of emails a month, that’s a real discount on Postmark and Resend with nothing locked behind a higher plan.

The trade-offs are newness and a narrower feature set. There is no free plan, no inbound mail, no dedicated IPs and only a few months of operating history. We’d start new projects and secondary flows on Helo now, keep the most critical mail where it is until Helo has a longer record, and revisit once custom tracking domains and more history arrive. We rate it 7.5 out of 10.