RadMail is an AI email operating system that reads every inbound message, surfaces only what matters right now, and drafts the follow-ups you promised on the day they are due.

> the inbox that thinks.

Opens lie. Replies don't. RadMail knows what got a reply, and drafts the follow-up you promised the day it's due.

RIGHT NOW — sample inboxwhy surfaced ▸
URGENTRe: COA for the Blue Dream batch — needs sign-off by Fri
SOONYou promised Tasha the report "by next week"
radmail@inbox:~$
// WATCH IT READ A LIVE INBOX

Press play. Watch the buried urgent wire jump to the top.

A faithful simulation of the live triage engine reading a raw inbox. Scripted re-enactment, not a live model call — the engine itself is live in a test bed on two real businesses.

radmail :: triage --live● running
ingesting inbox reading 0/5
RIGHT NOW
can wait
handled
sorting
// autonomous follow-through

It remembers what you promised. Then it writes the email.

RadMail tracks every commitment in your threads — both what you owe and what you are owed — drafts the reply the day it's due, and watches for the reply so it never nags you about what's already done.

commitment.statemachine
DETECTED"I'll send the COA Friday." — extracted from your sent threadowed by you
DRAFTEDFri 8:02a — reply written, attached, queued for your OKdraft ready ▸
DONEreply detected in-thread — task closed, you were never naggedcompletion seen ✓
OVERDUE"I'll loop in our rep." — 2 days late, party not yet contactedescalated ↑

Money, banking, and strangers? Always a human. Forever.

radmail :: auto-send guard

Pick a request — or type your own — and watch auto-send draft it or hard-stop.

requests

no request selected — auto-send is watching.

radmail@inbox:~$
// deliverability & engagement

RadMail ties each reply back to the send that caused it — something a send-only ESP structurally cannot do.

Apple opens a copy of every message, so a logged open means nothing. RadMail tells you which sends actually earned a reply because it reads your inbound mail too — the reply lands in the same mailbox it sent from.

deliveryinbox-placementopenclickREPLY
REPLY-CORRELATION — join a reply back to the send that caused itillustrative · sample data
Re: reorder — net-30 termsreply••
COA batch sign-off requestreply••
Newsletter — monthly dropreply
The REPLY column exists because the reply lands in the same mailbox — not a tracking-pixel guess.

SPF, DKIM, and DMARC come handled — a per-tenant wizard walks you from none → quarantine → reject, but only once your reports come back clean.

radmail@inbox:~$
// INBOUND BRAIN

Not an email client. An email operating system.

RadMail scores every email on two independent axes importance and urgency— never one blended number. A high-importance, low-urgency contract and a loud newsletter are never confused.

[ engine LIVE today in a test bed on two real businesses ]

Importance is not urgency. Your inbox finally knows it.

A two-axis engine scores importance AND urgencyindependently, and learns each sender's pattern from your behavior. Most “AI priority inboxes” collapse everything to one number. We don't.

The one lane that can't be missed.

A “Right Now”hero lane surfaces the highest-importance mail that actually needs you now — each item tagged with a plain-English “why surfaced.”The AI's judgment is auditable, not a black box.

From 'someone wants something' to a ready-to-send answer.

It reads what they want, gathers the facts with deterministic code (not the model guessing), and drafts a complete answer. The facts are code, so the proposal is solid enough to one-click. Human-confirm, always.

Triage that gets smarter every night.

Rules first, the model only when needed — with a self-learning loop that folds your fixes back in overnight. Plus one-click 4D (Do / Defer / Delegate / Delete) with an AI pre-pick.

See the engine Extract Gather Propose confirm Execute
// early access

The inbox that thinks is opening to design partners.

The engine is live today in a test bed on two real businesses. Join the waitlist to shape what ships.

signup connect first value in under 15 minutes
  • Get in before the doors open.

    We're onboarding design partners first. Waitlist members shape the roadmap, the regimes, and the pricing — and lock founding terms.

  • Built multi-tenant from row zero.

    Every tenant's mail is isolated at the row from day one. The Gmail / Outlook overlay ships after launch — waitlist members get it first.

join --waitlist● accepting

Founding partners lock early-access pricing + shape the roadmap.

No spam. We read our own inbound, so we know better.

// faq

Questions, answered straight.

What is RadMail, and how is it different from Superhuman or an AI inbox?

Those are clients you read mail in — a faster inbox. RadMail is an email operating system that does the work: it ranks each message by importance and urgency on two separate axes, surfaces a Right Nowlane with a plain-English reason it landed there, extracts the commitments hiding in your threads, and drafts the follow-up the day it's due. And it tells you what actually got a reply, not just an open — a send-only tool can't, because it never sees the replies. RadMail is a Sureel venture.

What is reply-correlation?

Most email tools report opens and clicks. RadMail can tell you which of your sends actually earned a reply, because it ingests inbound mail as well as sending outbound — a send-only email service provider never sees the reply, so it can't connect a send to the response it produced. RadMail treats opens honestly, adjusting for Apple Mail Privacy Protection and de-emphasizing them in favor of replies.

Does RadMail send emails on its own?

Only after it earns trust, and never for high-risk actions. RadMail rolls out in stages: surface-only, then draft-on-due (it writes the message and waits for you), then narrow auto-send for low-risk cases. Anything involving money, banking details, a decision, or first contact with a third party stays human-only, forever — a deliberate defense against business-email-compromise fraud.

Is RadMail HIPAA or SOC 2 compliant?

Compliance is a shared responsibility, and RadMail is a tool, not a guarantee of compliance. RadMail signs a BAA and processes on BAA-covered, encrypted, audited infrastructure, with a pluggable per-org regime (SOC 2, WSLCB, HIPAA, FedRAMP-CUI, BSA-AML) assembled from PolicyPacks. Controls are SOC 2-aligned with a Type II audit planned, and the infrastructure is FedRAMP-aligned / NIST 800-171-ready. For regulated tenants, HIPAA handling is draft/ingest-only at this stage. Using RadMail does not by itself make your organization compliant.
// outbound
rendering react-email :: dark-mode first :: built-for outlook+gmail ..... [ OK ]

Emails that don't break in Outlook. Or dark mode.

Designed dark-mode-first — where most branded email inverts to unreadable.

14-template librarytransactional lifecycle outreach

SHOWCASE :: priority-digest.tsxrendered ✓
radmaildark-mode build

Today, in priority order

4 need you · 11 handled · ranked by the importance engine

  • Re: contract sign-offOutside counsel
  • Draft ready: refund questionFront-desk lead
  • Balance low — action neededVendor billing
  • auto-ignored / bulkNewsletter x3
sent by the inbound brain

Your whole day's email, ranked, in one mail.

The Priority Digest: a single rendered summary of what needs you, in priority order. The daily proof the inbound brain is working for you.

radmail@inbox:~$ open --digest
Get on the waitlist
// COMPLIANCE

One platform, many rulebooks. A new vertical is a file, not a rebuild.

Compliance is a pluggable per-organization regime, assembled from PolicyPacks. We sign a BAA and process your data on BAA-covered, encrypted, audited infrastructure — compliance is a shared responsibility, and RadMail is a tool that supports your program, not a compliance guarantee.

RadMail is not a compliance certification; it is a tool that supports your program under a shared-responsibility model. The WSLCB cannabis PolicyPack is live in a test bed today; the SOC 2, HIPAA, and FedRAMP/CUI packs are architecture and roadmap.

regime_matrix --isolation --status

WSLCB pack live today; the rest are architecture, stated on the record.

show full regime matrix
  • noneshared-DB · RLSunregulated baselineBASELINE
  • SOC 2shared-DB · RLSSOC 2-aligned controls · audit plannedFLOOR
  • WSLCBshared-DB · RLSpack live in the test bed todaySHIPPED
  • HIPAAdedicated-DB · customer key (planned tier)draft/ingest-only · human-reviewed until SES-prodARCH/ROADMAP
  • FedRAMP-CUIregion-pin planned (Gov-Bedrock)TARGET design goal · no authorization held · NIST 800-171-aligned (roadmap) · no CUI in production todayARCH/ROADMAP
  • BSA-AMLdedicated · audited (planned tier)roadmap packARCH/ROADMAP

Honest about where each regime stands.

SOC 2-aligned controls today, audit planned. On FedRAMP/CUI: a target design only, no authorization held, and we do not handle CUI in production today. For HIPAA tenants, regulated sends are draft/ingest-only and human-reviewed — we do not auto-send regulated mail until SES-prod is in place.

Shared responsibility, stated plainly:RadMail signs a BAA and becomes your Business Associate. It then processes on BAA-covered, encrypted, audited infrastructure. The architecture is the premium lever — never a badge we'd claim we don't hold.

› Talk regimes with us
radmail@inbox:~$ regime --explain
// pricing

Early-access pricing.

Waitlist members shape it.

Four tiers — Starter, Pro, Business, Enterprise. Prices land later. Join early access, help set them, and lock founding terms.

Starter

one team, inbox under control

TBDearly-access

The inbound brain for one team. It tells you what matters now.

join early access>
Pro

it acts, then proves it landed

TBDearly-access

Adds autonomous follow-through and reply-correlation — it writes the email, then proves it landed.

join early access>
Business

multi-mailbox, growing ops

TBDearly-access

Multi-mailbox ops on a SOC 2-aligned controls floor.

join early access>
Enterprise

regulated, isolated, integrated

Customtalk to us

Regulated regimes, region-locked isolation, and a signed BAA.

talk to us>
capability_matrix.tsv
RadMail capability comparison across Starter, Pro, Business, and Enterprise tiers.
capabilityStarterProBusinessEnterprise
Inbound brain + importance engine[][][][]
Autonomous follow-through[][][][]
Reply-correlation[][][][]
Regulated regimes + BAA[][][][]
SOC 2-aligned controls floor[][][][]
founding_terms.txt
radmail@inbox:~$ pricing --status
[ pricing :: TBD — early-access partners lock founding rates ]

The engine is live today in a test bed on two real businesses. Early-access partners set the numbers and lock founding rates before public pricing posts.

On the regulated tiers we sign a BAA and process on BAA-covered, audited infrastructure. Compliance is a shared responsibility— a tool, not a guarantee.

Get founding terms >

join the waitlist for early-access pricing — no card, no commitment