# opensend.cc vs Resend: pricing, API and email limits

> opensend.cc is a self-hosted, open-source alternative to Resend with a Resend-compatible API. Compare price, rate limits, API compatibility and migration.

Canonical: https://versuscraft.xyz/p/opensend-vs-resend
Published: 2026-11-20
Last verified: 2026-11-20

_Last verified: 20 November 2026_

opensend.cc is a self-hosted, open-source alternative to Resend with a Resend-compatible API: you run it on your own server and pay only for that server and your email provider (like AWS SES). ([opensend.cc](https://opensend.cc)) Choose it when you want its Apache-2.0 source and your email running on your own infrastructure. A move to opensend.cc needs the URL for your own installation, and you must switch sending traffic in your application; opensend.cc provides no automatic migration command.

## Key takeaways

- opensend.cc Self-host gives you Apache-2.0 source and lets you send through AWS SES or another SMTP relay. ([opensend.cc docs](https://opensend.cc))

- Switching from Resend takes work in your application: opensend.cc has no automatic migration or command to gradually build sending reputation (a warm-up).
- Choose Resend if your workflow needs threaded inbox messages or the ability to replay webhook events. ([Resend docs](https://resend.com/docs/webhooks/introduction))

## At a glance

| Measure | opensend.cc | Resend |
| --- | --- | --- |
| Entry plan base price | Self-host: $0 forever | Free: $0/mo |
| Paid plan | Cloud: coming soon (waitlist) | Pro: $20/mo for 50,000 emails |
| Team API request rate | 10 requests per second | 10 requests per second |
| API | Resend-compatible REST API and SMTP | REST API and SMTP relay |

## opensend.cc vs Resend features for campaigns and inboxes

opensend.cc lists email and campaign tools and supports receiving messages with your AWS account; Resend offers scheduled broadcasts, threaded inboxes and automation runs. ([opensend.cc docs](https://opensend.cc), [Resend pricing](https://resend.com/pricing))

Pick opensend.cc if its listed campaign tools and your own AWS account fit the application. Pick Resend if threaded inboxes or the documented automation allowance drive the design.

## Is the opensend.cc API compatible with Resend?

opensend.cc follows Resend's HTTP API shape, and its SDK keeps Resend's resource and method names so most integrations need only a new import and installation URL. opensend.cc uses JSON email requests authenticated with a bearer token; send them to the base URL of your installation. Resend's email request format is also JSON.

Reusing an idempotency key with a different method, path, or request body returns a conflict; if the original request is still running, retry the same request later. ([opensend.cc docs](https://opensend.cc/docs/dashboard/emails/idempotency.md)) An opensend.cc send ID means the email has been saved in its sending queue for processing; it does not mean the email reached an inbox. If a send to Amazon SES times out, opensend.cc marks it failed without automatically sending it again; the timeout does not establish whether SES sent the email.

## opensend.cc vs Resend API rate limits

Both publish the same default limit: 10 requests per second per team, shared across all of a team's API keys. ([opensend.cc docs](https://opensend.cc/docs/api-reference/introduction), [Resend docs](https://resend.com/docs/api-reference/rate-limit)) Resend's limit is the same on every plan, so upgrading doesn't raise it; its Batch Email API sends up to 100 emails in one request, and each batch counts as a single request against the limit. ([Resend pricing](https://resend.com/pricing)) Plan burst traffic around the request limit and batching rather than expecting a plan change to lift it.

## opensend.cc vs Resend API keys and webhook signatures

opensend.cc authenticates server requests with team API keys; a sending key can be restricted to one domain, and opensend.cc stores only the key's hash. ([opensend.cc docs](https://opensend.cc/docs/create-an-api-key.md))

When moving to opensend.cc, test webhook verification with the new secret before switching traffic.

## opensend.cc vs Resend test mode and developer tools

For staging without emailing real users, opensend.cc test keys accept requests but deliver nothing, and Node.js applications can send through its SDK. Resend test emails count against the account's sending quota. ([opensend.cc docs](https://opensend.cc), [Resend docs](https://resend.com/docs/dashboard/emails/send-test-emails)) Resend's CLI can register a temporary webhook for local testing, and event replay lets you process a webhook again if your endpoint missed it. ([Resend docs](https://resend.com/docs/webhooks/introduction))

To self-host opensend.cc, use a server with Docker Engine and the Compose v2 plugin. Resend's hosted MCP server uses OAuth, so an AI client can sign in instead of requiring an API key or manually configured header.

## opensend.cc vs Resend pricing and email limits 2026

The self-host monthly email allowance is not shown on opensend.cc's pricing page (checked 20 November 2026). opensend.cc Cloud pricing is coming soon. ([opensend.cc docs](https://opensend.cc))

If you need annual billing, Resend is not a fit: it offers monthly plans only. ([Resend pricing](https://resend.com/pricing))

Choose opensend.cc if you can operate the stack; choose Resend if published email allowances and overage pricing are more useful for forecasting.

## Where opensend.cc wins

- Choose opensend.cc Self-host if you want its Apache-2.0 source and the option to use AWS SES or another SMTP relay. ([opensend.cc docs](https://opensend.cc))
- If you already use Resend, point a Resend-style SDK at your opensend.cc installation URL and keep your app code. ([opensend.cc docs](https://opensend.cc))
- Use opensend.cc test keys to exercise requests in automated build and test runs or staging without sending email to real users. ([opensend.cc docs](https://opensend.cc))

## Where Resend wins

- Choose Resend if your team needs inbox workflows: received messages are grouped into threads, and the Free, Pro and Scale plans each include 3 inboxes. ([Resend pricing](https://resend.com/pricing))
- Choose Resend if you need to recover missed webhook events or test a webhook locally: it supports event replay, and its CLI can register a temporary webhook for local testing. ([Resend docs](https://resend.com/docs/webhooks/introduction))

## Limitations to plan for

- opensend.cc has no automatic migration or sending warm-up command, so plan and execute the traffic switch in your application.
- For opensend.cc contact imports, split files into batches of at most 500 rows and stay within the API's separate parsed-data limit. ([opensend.cc docs](https://opensend.cc/docs/migrate-from-resend.md))

- Resend test emails use part of your account's sending quota. ([Resend docs](https://resend.com/docs/dashboard/emails/send-test-emails))

opensend.cc is a poor fit if you need a published Self-host monthly email allowance or an automatic tool to migrate and warm up sending.

## Migration impact

Moving from Resend to opensend.cc can preserve much SDK code: opensend.cc keeps Resend resource and method names, with most code needing a new import and installation base URL. Check opensend.cc's compatibility limits: its Convex IDs are opaque identifiers, attachment URLs must be publicly reachable over HTTPS, and each template has one draft and one published version.

Because opensend.cc has no automatic migration or sending warm-up command, plan and carry out the move to it in your application. Both products use Svix-compatible webhook signatures; before switching to opensend.cc, test verification with its new secret. opensend.cc's suppression batch API adds manual entries; it does not import the previous provider's bounce or complaint metadata.

When moving from opensend.cc to Resend, account for opensend.cc's identifier, attachment-URL, and template limits; Resend webhook payloads use Svix signature headers.

## Which one fits your use case

- Pick opensend.cc if you want self-hosted Apache-2.0 source and the choice of AWS SES or another SMTP relay. ([opensend.cc docs](https://opensend.cc))

- If you are moving from Resend and want to self-host, opensend.cc gives you Apache-2.0 source and a Resend-compatible API. ([opensend.cc docs](https://opensend.cc))
- Pick Resend if your application needs received messages grouped into threads or the ability to replay missed webhook events. ([Resend docs](https://resend.com/docs/webhooks/introduction))

## Verdict

Pick opensend.cc if you can run the infrastructure and want Apache-2.0 source, a choice of email relay, and an API shaped like Resend's. ([opensend.cc docs](https://opensend.cc)) Pick Resend if you need published Free and Pro sending allowances, threaded inbox messages, or webhook event replay. ([Resend pricing](https://resend.com/pricing), [Resend docs](https://resend.com/docs/webhooks/introduction))

## Frequently asked questions

### Does a queued opensend.cc email ID prove inbox delivery?

No. An opensend.cc ID means the email entered the durable queue; it does not prove inbox delivery.

### How many rows can opensend.cc export to CSV?

The opensend.cc CSV export limit is 200,000 rows and 16 MiB. ([opensend.cc docs](https://opensend.cc/docs/self-hosting/background-jobs.md))

### Do inbox messages use a separate Resend email allowance?

No. Emails sent or received through Resend inboxes count toward the transactional email quota. ([Resend pricing](https://resend.com/pricing))

### Can Resend customers pay annually?

No. Resend offers monthly plans only. ([Resend pricing](https://resend.com/pricing))

### What happens to Resend's audience endpoints?

Resend has deprecated its audience endpoints in favor of Segments; the endpoints still work but are scheduled for future removal.

## Try opensend.cc

- Check that your server has Docker Engine and the Compose v2 plugin.
- Choose AWS SES or another SMTP relay for opensend.cc Self-host. ([opensend.cc docs](https://opensend.cc))
- Point a Resend-style SDK at your opensend.cc installation URL and test the integration before switching sending traffic. ([opensend.cc docs](https://opensend.cc))

## Sources

- [opensend.cc](https://opensend.cc/)
- [opensend.cc/docs/migrate-from-resend.md](https://opensend.cc/docs/migrate-from-resend.md)
- [github.com/resend/resend-cli](https://github.com/resend/resend-cli)
- [resend.com/docs/webhooks/introduction](https://resend.com/docs/webhooks/introduction)
- [resend.com/pricing](https://resend.com/pricing)
- [opensend.cc/docs/create-an-api-key.md](https://opensend.cc/docs/create-an-api-key.md)
- [opensend.cc/docs/index.md](https://opensend.cc/docs/index.md)
- [resend.com/openapi.yaml](https://resend.com/openapi.yaml)
- [opensend.cc/docs/self-host-in-10-minutes.md](https://opensend.cc/docs/self-host-in-10-minutes.md)
- [opensend.cc/docs/dashboard/emails/idempotency.md](https://opensend.cc/docs/dashboard/emails/idempotency.md)
- [github.com/resend/resend-skills](https://github.com/resend/resend-skills)
- [resend.com/docs/dashboard/emails/send-test-emails](https://resend.com/docs/dashboard/emails/send-test-emails)
- [opensend.cc/docs/quickstarts/nodejs.md](https://opensend.cc/docs/quickstarts/nodejs.md)
- [opensend.cc/docs/self-hosting/background-jobs.md](https://opensend.cc/docs/self-hosting/background-jobs.md)
