# Introduction

Send email from your own infrastructure with a Resend-compatible API.

opensend.cc is an open-source email platform you run yourself. Manage domains, send transactional email, receive messages, and build campaigns using your own AWS account.

## Start sending

- [Run opensend.cc](/docs/self-host-in-10-minutes): Start your own installation.
- [Get an API key](/docs/create-an-api-key): Connect your application.
- [Send your first email](/docs/quickstarts/http): A few lines of HTTP.

## How it works

Next.js (Dashboard) → Convex (API · storage · jobs) → AWS SES (Email delivery).

Delivery feedback returns from SES to Convex over HTTPS.

Your Next.js dashboard manages the installation. Self-hosted Convex stores data, serves the API, and runs durable jobs. AWS SES delivers email and sends delivery feedback back to Convex. Incoming mail passes through a temporary S3 bucket into Convex file storage.

## Resend compatibility

Use familiar email fields and SDK calls with your own API origin. There is no shared opensend.cc cloud API URL. The API origin is the public Convex HTTP service, usually behind HTTPS on port 3211 internally. It is separate from your dashboard and Convex query service.

Compatibility has boundaries: IDs are opaque Convex IDs, attachment URLs must use public HTTPS, and templates have one draft and one published snapshot. Read the [API introduction](/docs/api-reference/introduction) and [compatibility with Resend](/docs/api-reference/compatibility) before migrating.

## Choose your path

Already running opensend.cc? [Create a key](/docs/create-an-api-key), [verify a domain](/docs/add-a-domain), and follow the [HTTP quickstart](/docs/quickstarts/http).

Starting from scratch? Use [Docker Compose](/docs/self-host-in-10-minutes). Local setup is quick; AWS production approval and DNS propagation can take longer.

Send from Node with `@opensendcc/sdk`, or from any language over HTTP. The MCP server, `@opensendcc/mcp`, connects AI agents. [SDKs and tools](/docs/sdks) explains both.
