opensend.cc

Product Introduction

1. Definition: Opensend.cc is an open-source, self-hosted email API and delivery platform. Technically, it is a full-stack email infrastructure application built on a modern web stack (Next.js, Convex, Better Auth) and designed to be deployed via Docker Compose. It functions as a drop-in replacement for hosted email API services.
2. Core Value Proposition: It exists to give developers and businesses complete ownership and control over their email-sending infrastructure, data, and sender reputation. The primary value is eliminating per-email fees and vendor lock-in by allowing users to run a Resend-compatible API on their own servers while leveraging their own AWS SES account for delivery.

Main Features

1. Resend-Compatible REST API & SDKs: Opensend.cc provides a REST API that is functionally identical to Resend's API. This includes support for scoped API keys, batch sending, and idempotent retries. How it works: Developers can point existing Resend SDKs (e.g., for Node.js, Python) simply by changing the base URL to their self-hosted Opensend instance, requiring minimal code changes. The API endpoints for sending, retrieving logs, and managing domains mirror Resend's structure.
2. Unified Dashboard with React Email Templates: The platform includes a self-hosted Next.js dashboard for full operational management. A key technical feature is integrated React email template development. How it works: Users build email components using React, preview them directly within the dashboard, and then send them via the API using a template name and props, streamlining the design-to-send workflow.
3. Comprehensive Email Operations Suite: Beyond sending, Opensend.cc provides tools for managing the entire email lifecycle. This includes: Contact and audience management stored in the local Convex database; broadcast capabilities for newsletters; signed webhook delivery for events (deliveries, bounces, complaints) with retries; and a full searchable log with analytics. All features are accessible via both the Dashboard and the API.

Problems Solved

1. Pain Point: High and unpredictable costs associated with per-email pricing models of SaaS email APIs, coupled with a lack of infrastructure transparency and control over sender reputation data.
2. Target Audience: The primary personas are Cost-Conscious SaaS Founders and Full-Stack Developers/DevOps Engineers at startups and agencies. Secondary audiences include Marketing Managers needing broadcast tools without external SaaS costs and Enterprise IT Teams requiring data sovereignty and on-premise deployment options.
3. Use Cases: Essential for: 1) Startups scaling their transactional email volume who want to cap costs at AWS SES rates. 2) Agencies building client applications who need a standardized, billable email stack they fully control. 3) Projects with strict data residency requirements (GDPR, HIPAA) where user email data cannot leave owned infrastructure. 4) Developers migrating from Resend who want to maintain their codebase but reduce long-term operational expenses.

Unique Advantages

1. Differentiation: Unlike SaaS providers like Resend or SendGrid, Opensend.cc has no per-email fees—users pay only for underlying AWS SES usage and their server hosting. Unlike setting up SES directly, it provides a polished developer experience (API, SDK, Dashboard) and advanced features (templates, audiences, webhooks) without building them in-house. Compared to other open-source solutions, its Resend API compatibility and integrated modern stack (Next.js/Convex) offer a unique developer-centric workflow.
2. Key Innovation: The product's core innovation is the fully integrated, self-contained stack deployable via a single Docker Compose command. It uniquely combines a Resend-clone API, a production-ready dashboard, a reactive database (Convex), and an auth layer (Better Auth) into one cohesive, easily deployable package. This "batteries-included, but you own the factory" approach significantly lowers the barrier to self-hosting a professional email platform.

Frequently Asked Questions (FAQ)

1. Is Opensend.cc truly free to use? Yes, the Opensend.cc software is open-source (Apache 2.0 license) and free to self-host. There are no licensing fees or feature gates. Users only pay for their own infrastructure costs: the server/VPS hosting the Docker containers and the AWS SES (or other SMTP provider) usage fees for sending emails.
2. How difficult is it to migrate from Resend to Opensend.cc? Migration is designed to be straightforward for developers. The primary technical step is changing the API base URL in your Resend SDK configuration to point to your self-hosted Opensend instance. Your email-sending code, template logic (if using React Email), and webhook handling can typically remain unchanged due to the API compatibility.
3. What are the technical requirements for self-hosting Opensend.cc? You need a Linux server (VPS or dedicated) capable of running Docker and Docker Compose. You must have a domain name for sending email and the ability to configure its DNS records (for DKIM, SPF, DMARC). An AWS account with SES configured (or credentials for another SMTP relay) is also required for actual email delivery.
4. Does using Opensend.cc with AWS SES guarantee good email deliverability? Opensend.cc manages the integration and guides DNS setup, but ultimate deliverability depends on your domain reputation and AWS SES sending practices. The advantage is that your sender reputation is isolated to your own AWS account and domain, not shared with other users, giving you full control to build and maintain a positive reputation.
5. What is the difference between the Self-hosted and Cloud (waitlist) versions? The Self-hosted version requires you to manage the Docker deployment, updates, and underlying infrastructure. The upcoming Cloud version is a managed SaaS where the Opensend.cc team runs the servers, handles updates, and manages SES configuration, offering the same API but as a hosted service for teams that prefer not to self-manage.