CORIVA

So, how does Coriva work?

Short answers on plans, delivery rates, and the reasons
teams move their sending over to a smaller API.

How is Coriva different from the large sending suites?

Coriva is a lean delivery platform built around one idea: a small, legible API and pricing you can predict before you send. The older suites grew into sprawling marketing consoles, so shipping a single receipt email now takes an afternoon of configuration and a call with an account manager. Here you mint a key, post to one endpoint, and watch every attempt land in a dashboard that fits on a single screen.

Who is this actually built for?

Product teams that send receipts, alerts and onboarding sequences from their own application, and want one bill and one log for all of it.

Is it only useful if someone on the team writes code?

No. The template studio and the campaign composer are visual, so a marketer can ship a send without opening an editor. The API is there when you outgrow that.

Does it hold up once volume gets serious?

Peak throughput sits near 340,000 messages an hour per account, spread across independent IP pools so a campaign burst never queues behind your receipts.

How fast does someone answer a support ticket?

Median first reply is 47 minutes on weekdays and under four hours at weekends. Every ticket reaches an engineer, not a scripted queue.

Will you help us move across from another provider?

Yes — we import your templates, warm the new addresses gradually and run both stacks side by side until the delivery numbers match.

Do you advise on inbox placement and reputation?

Accounts above the starter tier get a quarterly review covering authentication records, complaint rates, list hygiene and the shape of your bounce curve.

Is there a public library I can read before signing up?

The whole reference, every recipe and the release log are open — no account, no gated PDFs.

Who is behind Coriva?

A team of nine, most of whom spent years running delivery infrastructure for marketplaces and were tired of paying for features nobody opened.

Why did you decide to build it?

Because a password-reset email should not require a sales call, a contract minimum and three days of onboarding before the first message leaves the building.

How many teams are sending with you today?

4,180 accounts are active this month, and together they moved 1.62 billion messages over the last thirty days.

What sort of products run their sending on Coriva?

Booking tools, developer platforms, fintech dashboards and a good number of two-person side projects that grew into something larger.

What actually happens during an outage?

Accepted messages hold in a durable queue and drain in order once service returns. The status page updates within four minutes, and a written post-mortem follows.

📮

Put your first message on the wire

Receipts, alerts and campaigns from one small API.
No minimums, no sales call, no surprise invoice.