Helo

Product Introduction

1. Definition: Helo is a modern, developer-centric Email API and SMTP service designed for programmatic email delivery. It falls under the technical categories of Email Service Provider (ESP), Transactional Email API, and Email Infrastructure.
2. Core Value Proposition: Helo exists to solve the core problem of email deliverability with a focus on simplicity, reliability, and fairness. Its primary value proposition is providing a fast, affordable email delivery service that ensures emails reach the inbox, especially for platforms and developers sending on behalf of multiple users or tenants.

Main Features

1. Dual Delivery Protocols (REST API & SMTP): Helo provides both a modern RESTful API and a standard SMTP gateway for email sending. The REST API offers granular control, webhook integrations, and detailed analytics, while the SMTP option allows for easy integration with legacy systems or applications that require SMTP. This dual-protocol approach ensures compatibility with virtually any tech stack.
2. Tenant & Stream Isolation for Platforms: A core technical feature for multi-tenant applications. Helo allows platforms to create fully isolated sending environments for each of their customers. This includes separate credentials, statistics, bounce/unsubscribe handling, and sender reputations. This prevents one spammy tenant from negatively impacting the deliverability of all other users on the platform.
3. Pre-Send Spam Detection & Reputation Protection: Helo proactively scans outgoing emails for spam-like content and suspicious sending patterns before they hit the public internet. This "containment" feature helps platforms identify and block bad actors within their user base before those actors can damage the platform's overall IP and domain reputation with mailbox providers like Gmail and Outlook.
4. Separate Transactional & Broadcast Infrastructure: Helo operates distinct, optimized infrastructure for transactional emails (e.g., password resets, receipts) and promotional/broadcast emails (e.g., newsletters). This separation is a critical email deliverability best practice, as mailbox providers evaluate these email types differently. It prevents a high-volume newsletter from slowing down or blocking time-sensitive transactional messages.

Problems Solved

1. Pain Point: Poor email deliverability and sender reputation damage, especially for platforms where one user's bad behavior affects all others. Traditional ESPs often pool sending, leading to collective reputation harm.
2. Target Audience: SaaS platform developers, product managers at B2B software companies, indie developers building multi-user applications, and marketing teams needing reliable transactional and promotional email delivery.
3. Use Cases:
   • A SaaS platform (like a project management tool) needs to send notifications from each customer's own domain without risking its core sending IPs.
   • An e-commerce plugin must send order confirmations and shipping updates with guaranteed inbox placement, separate from marketing blasts.
   • A developer building a new app requires a simple, affordable email API without complex tiered plans or overage fees.

Unique Advantages

1. Differentiation: Unlike large corporate ESPs focused on upselling and feature tiers, Helo offers a transparent, usage-based pricing model ($5/month + $0.00035 per email) with all features included. Compared to other startup ESPs, its deep focus on multi-tenant isolation and pre-send spam filtering for platforms is a specialized, core competency.
2. Key Innovation: The combination of tenant-level sending isolation with proactive spam containment is a unique architectural approach. It treats each customer of a platform as a first-class sender with their own reputation buffer, which is a significant technical and operational advantage over providers that offer mere sub-account features on a shared reputation pool.

Frequently Asked Questions (FAQ)

1. How does Helo's pricing compare to SendGrid or Mailgun? Helo uses a simple, flat usage-based model: a $5 monthly base fee plus $0.00035 per email sent, with all advanced features included. This contrasts with the complex tiered plans and potential overage fees common at larger providers, often making Helo more cost-predictable for growing applications.
2. Can my customers send email using their own domain with Helo? Yes. Helo provides full support for custom domain authentication (SPF, DKIM, DMARC). For platforms, this means you can easily allow your end-users to configure their own sending domains, which improves their email deliverability and maintains brand consistency.
3. Is Helo suitable for sending high-volume marketing newsletters? Yes, but with a key best practice: Helo recommends and provides separate infrastructure for broadcast emails. This ensures your marketing sends are optimized for volume and analytics without interfering with the performance of your critical transactional email stream.
4. How does the pre-send spam detection work for platforms? Helo's system analyzes email content and sending patterns in real-time before relaying messages to internet mail exchangers. If a user's behavior or content triggers spam alerts, the platform can be notified or the send can be blocked, protecting the sender reputation for all other tenants on the platform.
5. What kind of developer support and documentation does Helo offer? Helo provides comprehensive REST API documentation, SMTP configuration guides, and officially supported SDKs for popular programming languages (e.g., Node.js, Python, Ruby, PHP) to enable developers to integrate email sending within minutes.