Built on Amazon SES

Private email,
on your own domain.

Verify a domain, get a working inbox in the dashboard. Addresses like hello@yourco.com send and receive real mail — plus campaigns and a transactional Send API, all on infrastructure you don't have to run.

Start free trial Read the docs

Try it — live demo tenant

demo.centralbox.co

A pre-seeded demo tenant with a real inbox, contact list, and a completed campaign.

Press the button — this hits the demo tenant live via GET /v1/analytics/deliverability.

Running your own mail server vs. CentralBox

Self-hosting mail means Postfix/Dovecot config, DKIM key rotation, and a blocklist to babysit. CentralBox is one API call.

Before — self-hosted mail Servers, DNS, ongoing ops

# Provision a mail server (Postfix + Dovecot), then:
apt install postfix dovecot-imapd opendkim
# Generate and rotate DKIM keys yourself
opendkim-genkey -s mail -d yourco.com
# Configure SPF/DMARC by hand, watch your IP's
# reputation, and hope you don't land on a blocklist
# after your first bulk send.
sendmail -f hello@yourco.com someone@else.com < message.txt

curl TypeScript Python

curl https://api.centralbox.co/v1/messages \
  -H "Authorization: Bearer pb_live_..." \
  -d '{"from":"hello@yourco.com","to":"someone@else.com","subject":"Hi","text":"Hello!"}'

# { "messageId": "0100019...", "folder": "sent" }

import { CentralBox } from "@centralbox/client";

const client = new CentralBox({ apiKey: process.env.CENTRALBOX_KEY });
await client.messages.send({
  from: "hello@yourco.com",
  to: "someone@else.com",
  subject: "Hi",
  text: "Hello!",
});

import requests

requests.post(
    "https://api.centralbox.co/v1/messages",
    headers={"Authorization": "Bearer pb_live_..."},
    json={"from": "hello@yourco.com", "to": "someone@else.com",
          "subject": "Hi", "text": "Hello!"},
)

Everything a private inbox needs

One product for one-to-one mail, bulk campaigns, team inboxes, and a transactional API — all on your own domain.

Bring your own domain

Verify a domain you already own — CentralBox generates the DKIM/SPF/DMARC/MX records, and a poller flips it to verified the moment your DNS is live.

A real inbox, not just an SMTP relay

Addresses like hello@yourco.com and support@yourco.com send and receive real mail in a dashboard inbox — threaded conversations, attachments, search.

Reputation isolation, per tenant

Every tenant gets its own SES configuration set, suppression list, and (on Business) a dedicated IP pool — one customer's bounces never touch another's sender reputation.

Shared inboxes, team roles

Invite teammates as owner, admin, or agent, and grant them access to specific shared addresses — support@ can be a team, not just one person.

Campaigns with real guardrails

Bulk sends enforce suppression lists, list opt-in state, and a working one-click unsubscribe link before anything reaches SES — not after.

A transactional Send API, too

The same account doubles as a transactional-email API for your own apps — mint a scoped API key and send from your verified domain over HTTPS.

CentralBox vs. the alternatives

An honest comparison — no strawmen. Self-hosted mail and generic inbox suites both have their place.

	CentralBox	Self-hosted mail	Generic inbox suites
Setup time	Verify a domain, paste 3 DNS records, done	Provision a mail server, configure Postfix/Dovecot, fight spam filters	Instant, but on a shared/generic domain
Your own domain	Yes — hello@yourco.com	Yes, but you run the infrastructure	Often not supported, or a paid add-on
Deliverability reputation	Isolated per tenant (SES configuration sets + suppression lists)	Entirely your responsibility — one bad send can sink your IP	Shared with every other customer on the platform
Ongoing maintenance	None — CentralBox runs the mail server	Patching, monitoring, blocklist firefighting	None, but you're locked into their platform
Bulk / marketing email	Built in, with suppression + one-click unsubscribe	Bring your own campaign tooling	Rarely supported alongside a personal inbox
Transactional Send API	Included — same account, same domain	Build and operate it yourself	Not typically offered
Team roles / shared inboxes	Owner / admin / agent, per-address grants	Whatever your mail server supports	Varies, often a higher-tier add-on
Pricing model	Volume-metered, monthly	Server + ops time (your cost, not billed)	Flat per-seat, regardless of usage

How it works

1

Verify a domain

Add your domain and we generate the DKIM/SPF/DMARC/MX records. Paste them into your DNS — a poller flips it to verified automatically.

2

Create an inbox

Add addresses like hello@ and support@, share them with your team, and start reading/sending mail right in the dashboard.

3

Send at scale

Run campaigns to a contact list, or call the Send API from your own app — all on the same domain, with reputation kept isolated to your account.

Your registry password never touches our database.

API keys are minted with AES-256-GCM: your credential is encoded into the key itself, tamper-evident and decrypted per-request. Revoke a key and the credential is gone with it — read the key-design writeup.