Skip to content
Nabvia
Setup
Sign inStart free

Email safety net for Google Workspace and Microsoft 365

Some of your email is already lost. Nabvia gets it back.

Messages sent to a typo, to someone who left, or to an address that never existed get bounced or dumped in a catch-all nobody reads. Nabvia picks them up, works out who they were meant for, and tells that person. One routing rule, ten minutes, and nothing about your normal mail changes.

Start freeSee the setup
  • 14-day trial, no card
  • Never your MX
  • One routing rule

Nabvia is never in your delivery path.

This is a structural fact about where Nabvia sits, not a promise about how carefully we operate.

Your MX record still points at Google Workspace or Microsoft 365. Your provider still accepts every message, still applies your filters, still delivers to your mailboxes. Nabvia only ever sees what your provider was about to refuse.

Nabvia is never the MX record, never the first SMTP hop, and never a relay for valid mail. There is no configuration of this product in which a message to a real mailbox passes through us.

So the worst thing a Nabvia outage can do is stop the rescue. Unknown recipients go back to bouncing or landing in your catch-all, exactly as they do today, and every real address keeps working.

Where Nabvia sits in your mail pathMail arrives at your provider. Valid recipients go to their mailbox unchanged. Unknown recipients branch off to Nabvia.InternetGoogle / Microsoft 365Still your MXValid recipientUnknown recipientNormal mailboxUnchangedinbound.nabvia.comNotification
Nabvia hangs off the side of your provider. It is never in front of it.
  1. A message arrives from the internet at your provider, which is still the MX record for your domain.
  2. If the recipient exists, the message is delivered to that mailbox exactly as it is today.
  3. If the recipient does not exist, your routing rule hands the message to inbound.nabvia.com.
  4. Nabvia decides whether it matters and sends a notification to the right person.
What happens when Nabvia is unavailableThe same path with the Nabvia branch cut. Valid mail is unaffected; unknown recipients revert to the provider's existing behaviour.Google / Microsoft 365Valid recipientUnknown recipientNormal mailboxUnchangedBounce or catch-allNabvia unavailableRescue stops
You lose the rescue. You do not lose mail.
  1. Your provider is still the MX record and still accepts mail.
  2. Valid recipients are delivered exactly as before, because Nabvia was never in that path.
  3. Unknown recipients go back to bouncing or landing in your catch-all, as they did before Nabvia.

One routing rule. Ten minutes. Nothing else changes.

This is a configuration change in a console you already administer, not a migration.

  1. Create your tenant and add your domain

    Sign up, add the domain you want protected, and add the TXT record Nabvia gives you at your DNS host.

    2 minutes

  2. Add one routing rule in your admin console

    In Google Workspace, a Gmail default routing setting scoped to unrecognized addresses. In Microsoft 365, an accepted domain set to internal relay plus a connector to inbound.nabvia.com.

    5 minutes

  3. Name who hears about a rescue

    One address for the whole domain, or a rule per department. This is the person who receives the notification.

    3 minutes

The routing rule you addAn abstraction of the admin form, with the real field names and the values you paste.Admin console: Google WorkspaceMatch onEnvelope recipient: @acme.comActionacme@inbound.nabvia.comApply toUnrecognized onlyThe safety control
This is the whole change. The highlighted control is what keeps it away from real mailboxes.
  1. The rule matches on the envelope recipient for your domain.
  2. The action changes the recipient to your tenant address at inbound.nabvia.com.
  3. The scope is restricted to unrecognized addresses only, so no real mailbox is affected.

You do not change your MX record. You do not move a mailbox. You do not install anything.

Read the full setup

Priced on what it rescues, not on seats.

You can decide without talking to anyone.

Starter

One domain, one team, one address to notify.

€19per month

€190 per year, billed yearly

Start the trial

Business

Several domains and routing rules per department.

€49per month

€490 per year, billed yearly

Start the trial

Scale

Multi-entity, with an audit trail and an SLA.

from €149per month

Start the trial

Billing starts at the first rescue, not at signup.

Only rescued messages count. Spam Nabvia discards is free.

Prices are excluding VAT. French VAT is added for customers in France; customers elsewhere in the EU with a valid VAT number are reverse charged.

See the full pricing page

What Nabvia keeps, and what it drops.

The catch-all you do not read is where your invoices go.

This is the reason you cannot see the problem: the bounce goes to the sender, not to you. Somebody outside your company learns that your address does not work, and you never find out they tried.

550 5.1.1 The email account that you tried to reach does not exist.
What your provider tells the sender. Nothing in your inbox records that it happened.

Where the mail goes

An address that never existed
Someone guessed at contact@, invoices@ or your name, and guessed wrong.
A typo
One letter off in a domain your supplier has typed correctly a hundred times before.
Someone who left
The mailbox was closed the week they left. Their suppliers were not told.
An address you meant to create
It went on a quote, a website footer or an invoice template, and was never set up.
An unmonitored catch-all
Everything above is accepted, filed in one mailbox, and read by nobody.

Rescued

  • Supplier invoices
  • Customer requests
  • Contracts and signatures
  • Quotes and orders
  • Delivery notices

Dropped

  • Spam
  • Newsletters
  • Cold outreach
  • Automated marketing
  • Bulk mail with an unsubscribe header

Doing nothing has a price, it is just invisible. An unmonitored catch-all is the same outcome with an extra step: the message is accepted, filed somewhere nobody opens, and lost just as completely.

Two worked decisionsAn invoice to a former employee is rescued. A newsletter to a generic address is not.From: billing@supplier.exampleTo: j.martin@acme.comInvoice 2026-0417Decision

{ relevant: true, confidence: 0.92, reason: "Invoice from a known supplier, addressed to a former employee", recipient: "accounting@acme.com" }

Notification sentFrom: news@marketing.exampleTo: info@acme.comYour October product roundupDecision

{ relevant: false, confidence: 0.97, reason: "Bulk marketing newsletter with an unsubscribe header", recipient: null }

Nothing sent
The decision is a stored record with a reason, not a black box.
  1. An invoice from a supplier, addressed to an employee who left, is judged relevant with high confidence and routed to accounting.
  2. A marketing newsletter to a generic address is judged not relevant and nothing is sent.
  3. Both decisions are stored with their confidence and their stated reason.

You get one email. You never have to open an app.

The product fits inside the inbox you already live in, and correcting it costs one reply.

Illustration. This is a mock-up, not a screenshot of a shipped interface.

Acme via Nabvia <acme@notify.nabvia.com>

Rescued: Invoice 2026-0417 for a closed address

What the notification tells you

  • Who sent it, and from which address
  • Which address at your domain it was sent to
  • The original subject line
  • Why Nabvia decided it was worth rescuing

Open the message in the viewer

Reply to teach it

Every notification carries its own reply address. Reply "always send these to accounting@acme.com" or "stop sending me newsletters like this" and the routing changes. What you tell it outranks what the model inferred, and nobody has to open an admin screen.

The viewer shows a sanitised copy of the body with remote images off, lists every attachment with its scan status, and offers the untouched .eml for download.

We hold other people's email. Here is exactly how.

Answers to the security questionnaire, before you send it.

Position in the mail pathNever your MX record, never the first SMTP hop.
The original messageNever relayed onward. Nabvia composes a new message instead.
Notification identitySent from notify.nabvia.com, with SPF and DKIM aligned to that domain.
HTML handlingSanitised server-side. Scripts, forms, iframes, objects and embeds are stripped.
Remote imagesBlocked by default, so tracking pixels do not fire.
AttachmentsStored separately, scanned, and never attached to a notification.
Model boundaryEmail content is data to the model, never instructions.
HostingEuropean Union. Compute in France, object storage in the EU.
EncryptionTLS 1.2 or better in transit, encrypted at rest.

Read the full security page

What Nabvia is not.

Five things people reasonably assume, and none of them are true.

Not a shared inbox

There is no queue to work, no assignment, no team view. Nabvia sends one message to one person.

Not an email client

You keep Gmail or Outlook. Nabvia does not replace anything you open every morning.

Not a replacement for Google Workspace or Microsoft 365

It sits beside your provider and depends on it. Your provider stays in charge of delivery.

Not a primary gateway

It is never the MX record and never filters your inbound mail. It only sees what your provider refused.

Not a general forwarding service

Nabvia never relays the original message to anyone, because relaying breaks SPF and fails DMARC.

The questions your IT lead will ask.

Will this change how my normal email is delivered?

No. Nabvia only ever receives messages your provider was going to reject or drop into a catch-all. Valid mail never passes through it, and your MX record does not move.

What happens if Nabvia goes down?

Unknown recipients go back to bouncing or landing in your catch-all, exactly as they do today. Valid mail is untouched, because Nabvia was never in its path.

What exactly do I receive, the original message or something else?

Nabvia never forwards the original. Relaying it would break SPF and fail DMARC, which would make your delivery problem worse. You receive a new message, signed by Nabvia from notify.nabvia.com, carrying the original's sender, recipient, subject, the reason it was rescued, and a link to it.

Can I still read the original?

Yes. The viewer shows a sanitised copy with remote images off so tracking pixels do not fire, and you can download the untouched .eml at any time.

Is my email used to train an AI model?

No. Content is classified and routed, then kept for the retention window in your plan. It is passed to the model as delimited data, never as instructions, and it is not used for training.

What does it cost if Nabvia never finds anything?

Nothing. Billing starts at the first rescued message, not at signup, and messages Nabvia discards as spam are never counted.

Add the rule. Stop losing mail.

Ten minutes in a console you already administer, and your normal delivery is untouched.

Start freeSee the setup
  • 14-day trial, no card
  • Never your MX