Notavia is live: one API for every channel your users live in

After months of building and testing, Notavia is live in production today. One API. Four channels. One template system.

What Notavia does

Every SaaS product eventually needs to tell its users something. A new invoice. A failed sync. A teammate's comment. A security alert at 2am. You need that message to arrive on whichever channel the user is actually paying attention to — and you need to know it arrived.

Notavia solves that in a single call:

POST /v1/send
{
  "template": "invoice.paid",
  "recipient": "user_abc",
  "data": { "amount": "€49.00", "invoice_id": "inv_123" }
}

Notavia looks up the recipient's channel preferences, renders the template for each active channel, dispatches the messages, and gives you a delivery log — all without you managing provider credentials per channel or writing the same routing logic for the fourth time.

The four live channels

Email connects to your own SMTP relay or any compatible provider, and paid plans include managed EU sending with no provider setup at all. Transactional volume, custom sender domains, GDPR-clean unsubscribes — handled.

In-app inbox drops a real-time notification bell into your product. Users see unread counts, mark-as-read state, and a full notification history. You supply the bearer token; Notavia supplies the inbox.

SMS uses your own Twilio or Vonage credentials. Numeric sender IDs, regional routing, delivery receipts. There is no managed SMS option.

Chat delivers to Slack, Microsoft Teams, and Discord. Useful for internal tooling and DevOps alerting where the users are developers who live in those apps.

Push notifications are on the roadmap. The architecture is already there; we are working through the certificate management and TTL edge cases before we call it production-ready.

One template, every channel

The thing we spent the most time on is the template system. Templates are written in Scriban — a clean, logic-capable templating language that renders well to HTML, plain text, and short-form messaging bodies. You write one template file per event type, and Notavia renders the right variant per channel automatically.

Templates are runtime-editable: tenant administrators can modify the copy through the console without a deployment. You ship the default; your customers adjust the wording for their brand.

Who Notavia is for

If you are building a SaaS product and have ever written a notification service from scratch — or inherited one that was held together with scheduled jobs and a half-finished email queue — Notavia is for you.

The .NET, TypeScript, Python, Go, and PHP SDKs are all published. The REST API works directly if you prefer no SDK dependency.

Getting started

Create a free account, connect your providers, and send your first notification. The free tier covers 1,000 sends per month with no time limit and no card required. We built Notavia so you can go from sign-up to your first real notification in production in well under a day.

We built Notavia because we kept rebuilding it. We hope it saves you the same frustration.