Vendor Shutdown Risk: What to Check Before Betting on an AI Email Tool

Most buying guides in this category tell you how to compare features. Almost none tell you how to assess shutdown risk of an email tool — which is odd, because in roughly two years four mail products closed or lost a surface, and one of the best-known changed owner and then name.

You can't predict a shutdown. You can predict what it would cost you, and that number is knowable before you sign up.

This is the checklist we use, with a worked example, an export test you can run during a free trial, and the same checklist turned on AI Emaily — including the items we don't pass. Every fact below was verified in July 2026.

The short answer#

Stop asking whether the vendor will survive. Ask what you lose if it doesn't. Two tools with identical features can carry completely different continuity risk depending on where your mail sits and what the vendor holds that you can't get back.

The biggest single factor is whether your mail lives on a server you already control — Gmail, Microsoft 365, Exchange, or any IMAP host — or only inside the vendor's own system. In the first case the mailbox outlives the vendor and you change tools. In the second, a shutdown is a migration with a deadline.

After that it's a short list of testable questions: what exports, what exists only in the vendor's layer, who holds the OAuth grant, who owns the company, what the terms actually promise, and whether mail is the main business or a side project.

Four shutdowns and a rename, in about two years#

This is the real record for mail products, not a hypothetical. Re-check any row before you act on it — this category moves quickly.

Two patterns are worth naming. Every one of these was announced rather than sudden — the risk isn't waking up to a dead app, it's getting six to twelve weeks to do work you never planned for.

And in the Notion Mail case, messages were never at risk. Notion Mail synced two ways with Gmail, so every message also sat in the user's own Google account. What gets deleted is everything Notion Mail built on top.

The question underneath all the others: who holds the mailbox?#

An email tool is one of two things. Either it reads a mailbox you already own — over IMAP, Exchange or a provider API — or it hosts your mail itself and is the only place that copy exists.

That distinction sets the worst case. If the vendor holds a synced view, a shutdown costs you settings, habits, and whatever the AI layer generated. Your messages, folders and address are untouched, because your provider still has them, and you can point a different client at the same mailbox that afternoon.

If the vendor hosts the mailbox, a shutdown is a genuine migration: export the archive, re-point MX records if you used a custom domain, tell everyone your address changed if you didn't, and hope the export format is one your next tool can read.

Overlays sit in between. A tool that layers on top of Gmail or Outlook inherits the low risk of the mailbox, but can still hold rules, drafts and history that vanish with it.

This is a property of the category, not a virtue of any one product. A badly run IMAP client is still a bad product. It just fails less expensively.

The seven-point continuity checklist#

Each item is testable before you pay, and most take under ten minutes. Score them pass / partial / fail rather than adding up a number — one fail on item 1 outweighs four passes elsewhere.

Test the export during the trial, not during the wind-down#

Item 2 is the one everybody skips, and it's the one that costs most. An export you have never run is a promise, not a feature. Do this in the first week of a trial, while walking away still costs you nothing.

1. 1

   Put real data in

   Write two drafts, save a snippet or template, create one rule, schedule one send, and snooze a thread. This is the layer that dies first in every shutdown on record.

2. 2

   Find the export without asking anyone

   Look in settings. If the only route is emailing support, that is your answer for item 2 — record it as a partial at best.

3. 3

   Run it and time it

   Note how long it takes and whether the download link expires. Large mailboxes take minutes, and an expiring link matters if you run the export the night before a deadline.

4. 4

   Open every file

   Check the messages are readable, then look specifically for your drafts, rules, snippets and scheduled sends. What's missing is the real finding.

5. 5

   Try to import it somewhere else

   Take the export to one other tool you'd plausibly switch to. If nothing reads the format, treat it as an archive, not a migration path.

Scoring it: Notion Mail, in hindsight#

A checklist is only useful if it fires early. Score Notion Mail as it looked in early 2026 — months before any announcement — and three items were already red.

None of that is a criticism of the engineering — by most accounts the product was well built, and the stated reason for closing it was that users had moved their email workflows to agents. It failed on structure, and the structure was visible from outside.

A buyer who had run this checklist would probably still have used Notion Mail. They'd have kept snippets in a text file and rules they could rebuild, and lost an hour instead of a weekend.

Red flags worth more than the score#

• The export is "available on request." Anything routed through a support queue is not something you can rely on in the final week.
• The terms say nothing about discontinuation. Silence isn't a promise, it's an absence — and it's what you'll be holding at the end.
• Your mail is hosted by the vendor with no IMAP or Exchange access. That's the expensive failure mode, and no feature list compensates for it.
• The team's public attention has moved elsewhere. Shortwave's founding team, for instance, has shifted focus toward a separate agent product — that is not a shutdown and shouldn't be reported as one, but it is exactly the signal item 7 exists to catch.
• An acquisition closed and the roadmap went quiet. Postbox was acquired and discontinued in the same announcement.
• A single surface disappears before the product does. Edison Mail dropped its desktop app rather than the whole product, and if that surface was the one you used, the distinction doesn't help you.

The same checklist, applied to AI Emaily#

A checklist that quietly exempts its author is marketing. So here is ours, scored the same way, in July 2026 — and you should verify each line rather than take it from us, because that's the whole point of the exercise.

Run the checklist on us and AI Emaily passes items 1, 2, 4 and 7 — your mail stays in your own Gmail, Outlook or IMAP mailbox because we never host it, the export is a self-serve ZIP you can pull during the trial, the OAuth grant is yours to revoke at your provider, and email is the only thing this company builds — while item 3 is partial and items 5 and 6 are where we're genuinely weak.

Two more limits, since you'd rather hear them now: AI Emaily runs as a downloadable Electron desktop app on macOS (Apple Silicon only) and Windows, with no native Linux build, Android is a PWA with a native app on the roadmap, and offline support is partial by design.

None of that is continuity risk. It belongs in the same honest column.

What to actually do next#

Pick your two finalists and spend twenty minutes on each. Item 1 takes a minute, item 4 takes two, items 5 and 6 are reading, and item 2 is the trial-week export test above.

Then write one sentence: what would I lose if this disappeared in eighteen months? If the answer is "a weekend rebuilding rules," buy it. If the answer is "my mail," hold it to a much higher bar.

Apply that to every tool you're considering, this one included.