$9.99 once
One payment buys one license key. One key activates one installation: one Cloudflare account, one server, or one cluster that shares a database.
Self-hosted
Sending through your providers, a team inbox on your own domains with a spam filter, calendars, booking pages and Drive, on infrastructure you control. $9.99 once for one installation, with every future update included.
One payment, one installation, and every release after it. The software runs on infrastructure you control.
One payment buys one license key. One key activates one installation: one Cloudflare account, one server, or one cluster that shares a database.
Every future release of the self-hosted edition, with no renewal and no subscription. You choose when to deploy each one.
Mail, calendars, files, provider keys and logs stay in your Cloudflare account or on your server. No limits on domains, mailboxes, providers or sending.
Without a key it runs for evaluation: the dashboard, test API keys and the Sandbox provider work, and live email does not. OneSend is proprietary software under the OneSend License.
One license is the whole product, not a tier. Use only sending, or move your team's mail, calendars and files onto the same installation. All features
The same software runs in all three ways. Cloudflare runs it for you without a server, but it cannot accept the direct connections that mail apps use. Docker and Node.js can, and you run the server.
| Feature | Cloudflare | Docker | Node.js |
|---|---|---|---|
| Mail on your own domains | |||
| Sending through your providers, with routing and failover | Works | Works | Works |
| Receiving mail on your domains | Cloudflare Email Routing | MX record and port 25 | MX record and port 25 |
| Team inbox, spam filter, calendar, booking pages and Drive | Works | Works | Works |
| Templates, campaigns, lists and automations | Works | Works | Works |
| Your other email accounts | |||
| Gmail, Outlook and Zoho accounts in the inbox | Works | Works | Works |
| iCloud, Yahoo, Fastmail and other IMAP accounts | –Not available | Works | Works |
| New mail from IMAP accounts within seconds | –Not available | Works | Works |
| A campaign to more than about 3,500 recipients at once | Can reach Cloudflare’s per-run limit; the job is retried | Works | Works |
| Mail apps | |||
| IMAP and POP3 for desktop and phone mail apps | –Not available | Works | Works |
| SMTP submission from mail apps and devices | –Not available | Works | Works |
| Running it | |||
| What you need | Cloudflare Workers Paid | A server with Docker | A server with Node.js 22.13+ |
| HTTPS | Included | You add it (reverse proxy) | You add it (reverse proxy) |
| Database | D1 | SQLite or PostgreSQL | SQLite, PostgreSQL, libSQL or PGlite |
| Backups | D1 Time Travel, 30 days | You back up the volume | You back up the database |
| Installer | install.sh sets it all up | install.sh sets it all up | npm run setup |
Every option needs a sending provider for live mail (your own account with Amazon SES, Postmark, Resend or another) and a domain you can add DNS records to. The Connect Google, Microsoft and Zoho buttons need your own OAuth app with each of them; until then those accounts connect with an app password over IMAP, on Docker and Node.js. Gmail, Outlook and Zoho are checked for new mail every few minutes. Details: what is not available on Cloudflare, connected accounts.
Pricing
No subscription and no charge per email. The earlier you buy, the less you pay.
$9.99once
The key is shown after payment and sent by email. Payments are handled by Dodo Payments, the merchant of record. Prices in USD, plus tax where it applies. Full refund within 14 days of purchase: email us at support@onesend.email.
Buying now saves $15.00 on the standard price.
Enter the key from your purchase email to get the current release and earlier ones, with their SHA-256. Every update is included: come back here for new versions. A link works for an hour.
Or install from a terminal: it asks for the key, downloads the newest release, checks it and can set it up on Cloudflare or Docker.
curl -fsSL https://onesend.email/install.sh | shAdd the provider accounts you already have, in any combination. Provider keys are encrypted with your server secret and stay in your installation.
Logos are trademarks of their owners. OneSend is not affiliated with or endorsed by them.
Option 1
The main way to run it. One Worker runs the API, dashboard, jobs and inbound mail, with D1 as the database, Queues for jobs, R2 for attachments, imports and Drive files, and Email Routing for receiving. Nothing runs on a server of yours.
npm run cf:setup creates the D1 database, a queue and an R2 bucket, writes wrangler.jsonc and stores the secret.npm run cf:deploy builds the dashboard and the template snapshot, then deploys the Worker (the same step as npm run deploy -w @onesend/worker-cf). Tables are created on the first request.Not on Cloudflare: IMAP and POP3 for mail apps, SMTP submission, the built-in SMTP receiver, and connected IMAP accounts (iCloud, Yahoo, Fastmail); Gmail, Outlook and Zoho accounts work. They need a server that accepts connections, so use Docker or Node.js for them. Mail comes in through Email Routing instead. Starting one campaign to more than about 3,500 recipients can reach Cloudflare's per-run limit, and the job is then retried; see the guide's limits.
Cloudflare guidenpx wrangler login
npm run cf:setup # creates D1, a queue and R2, stores the secret
npm run cf:deploy # builds the dashboard and deploys the Workercd apps/worker-cf
npx wrangler secret put ONESEND_LICENSE_KEY # paste the keyOption 2
Docker builds the image from the download. It runs in production mode and exposes HTTP on 3000, SMTP submission on 2587, the inbound SMTP receiver on 2525, and IMAP (1143, 1993) and POP3 (1110, 1995) for mail apps. Data is kept in a volume.
Docker reads its settings from .env, so create it before the first start, with a generated ONESEND_SECRET. The installer command above does all of this for you.
Start from the release you download with your license key, unpacked. Questions: support@onesend.email.
Docker instructionstar -xzf onesend-selfhost-<version>.tar.gz # downloaded with your license key
cd onesend-selfhost-<version>
cp .env.example .env
# the server secret (required), your license key and a one-time setup code for the owner account
sed -i.bak "s|^ONESEND_SECRET=.*|ONESEND_SECRET=$(openssl rand -base64 32)|" .env && rm .env.bak
echo "ONESEND_LICENSE_KEY=OS-XXXXX-XXXXX-XXXXX-XXXXX" >> .env
echo "ONESEND_SETUP_CODE=$(openssl rand -hex 6)" >> .env && grep _SETUP_CODE .env
docker compose up -d --build
# With PostgreSQL in a second container instead of SQLite:
docker compose -f docker-compose.yml -f docker-compose.postgres.yml up -d --buildOption 3
npm run setup asks where the server runs, which database to use and who can create accounts. It generates ONESEND_SECRET, creates the tables and writes .env. Open the dashboard on port 3000 and create the owner account.
npm run doctor checks the configuration, database, ports and public URL at any time.
Start from the release you download with your license key, unpacked. Questions: support@onesend.email.
tar -xzf onesend-selfhost-<version>.tar.gz # downloaded with your license key
cd onesend-selfhost-<version>
npm install
npm run setup # asks a few questions, writes .env and creates the tables
npm run build:web # builds the dashboard
npm start # starts the server on port 3000Set DATABASE_URL, or choose one in npm run setup. SQLite supports one server process; use PostgreSQL for several.
The installer sets up the database, storage and the server. These steps connect it to your mail, once.
Sending works without it. To receive a domain's mail, add the domain, create its mailboxes or a catch-all, then send the domain's mail to your installation.
Booking pages, public Drive links, invitation answer links and calendar subscription links are opened by people outside your workspace, so they use your installation's public address.
ONESEND_PUBLIC_URL to the HTTPS address people will use. On Cloudflare, add a custom domain to the Worker first.ONESEND_TRUST_PROXY, so limits such as wrong link passwords count each visitor's own address.# Docker and Node.js: .env
ONESEND_PUBLIC_URL=https://mail.example.com
# Cloudflare: "vars" in apps/worker-cf/wrangler.jsonc
"ONESEND_PUBLIC_URL": "https://mail.example.com"The key is shown after payment and sent by email. Add it once; the server keeps it encrypted.
ONESEND_LICENSE_KEY before you deploy.Every release of the self-hosted edition is included. Back up first, then update. Migrations run by themselves.
tar -xzf onesend-selfhost-<new>.tar.gz # downloaded with your license key
cp onesend-selfhost-<old>/apps/worker-cf/wrangler.jsonc onesend-selfhost-<new>/apps/worker-cf/
cd onesend-selfhost-<new> && npm install
npm run cf:deploy # prints a D1 restore point, then deploysDownload the new release with your license key and unpack it next to the old one. Docker: copy .env across, then docker compose up -d --build (the data stays in its volume). Node.js: copy .env across (and the data folder, when it is inside the old one), then npm install, npm run build:web and restart.
npm run db:copy copies every table between any pair of SQLite, PostgreSQL, PGlite and libSQL or Turso. Use it to grow from SQLite to PostgreSQL, or to move to a new server. It does not support D1 yet.
npm run db:copy -- --from <source-database-url> --to <target-database-url>
npm run db:copy -- --dry-run # shows tables and row counts, writes nothingSet NODE_ENV=production and a generated ONESEND_SECRET from a secret store. Back it up with the database: it encrypts provider keys.
Run behind a reverse proxy with HTTPS, set the public URL, and configure TLS before exposing SMTP ingress or the mail-app ports.
On a fresh install the first account becomes the owner. The installer sets a one-time setup code, ONESEND_SETUP_CODE, so only you can create it.
The server speaks plain HTTP on port 3000. Put a reverse proxy in front for HTTPS. With Caddy it is three lines, and the certificate is issued and renewed for you. Then set ONESEND_PUBLIC_URL to the HTTPS address and ONESEND_TRUST_PROXY=1, and keep port 3000 closed to the internet. Cloudflare needs none of this.
# /etc/caddy/Caddyfile (Caddy gets the certificate by itself)
mail.example.com {
reverse_proxy localhost:3000
}The hosted cloud runs the same platform for you. The waitlist is open.