One API for every customer communication.

You should not have to build this again

Sending the message is the easy part.

The first notification takes an afternoon. Then comes everything around it.

NotifHQ packages these behind one communication layer.

More than a send endpoint

Your application owns the event. NotifHQ owns the communication.

Your application describes what happened. NotifHQ decides how that communication is produced, whether it is permitted, how it is rendered, where it goes and what is recorded.

3 channels available now; 6 declared across the roadmap.

Typed notifications

Stop sending arbitrary blobs.

Define a communication once. NotifHQ then knows its required payload, its permitted channels, whether a preference may override it, how it de-duplicates and how long it stays worth sending.

58 notification types are described in the dictionary today, across 18 business domains.

The rule everything else follows

Requested is not sent. Sent is not delivered. Delivered is not engaged.

Most tools collapse these into one green tick. NotifHQ keeps them apart in the API, the events, the metrics and the timeline — because the moment they merge you can no longer answer the only question that matters when something goes wrong.

An email open is a tracking-pixel fetch a mail client may make, prefetch, cache or block. We call it an open observation, and the metric is named for what it is.

Evidence, not assertion

“I never got the email.”

Answer it from stored state, in seconds, without opening a transport's logs and hoping they are still in retention. Every state transition writes an append-only, hashed evidence row carrying two separate times: when the world produced the signal, and when we recorded it.

73 event families are declared, each emitting evidence before anything reacts to it.

Do not start from a blank screen

Install communication patterns, not a folder of HTML files.

A pack installs notification types, schemas, contracts, templates, routing defaults, preference categories and analytics definitions together — so a team starts with a shared vocabulary instead of assembling one.

32 packs: 16 sector, 13 functional and 3 compliance.

AI where it helps, guardrails where they matter

AI drafts the copy. The contract keeps it safe.

Drafting is a stage inside the template rail, never a bypass around it. Generated content enters as a draft and traverses variable validation, preview, review and a recorded human approval like anything else.

Respect preferences automatically

Your code should not branch before every send.

Preferences, consent, suppressions, quiet hours and rate limits are evaluated as part of the communication lifecycle. You call the same endpoint; the decision is made once, recorded, and explainable afterwards.

54 registered reason codes, so “why was this suppressed?” is answerable in a support conversation without reading code.

Process first, store less

The payload is minimised before anything stores it.

One rail runs over every payload class — notifications, inbound mail, attachments, ticket messages, webhook bodies. A field your contract does not declare is dropped before persistence, so it never needs classifying and never needs protecting.

Detection is deterministic and authoritative. A card number is caught by a checksum, not by resemblance — an order reference that looks like a card is not one, and an embedding never gets a say in a security decision.

Measured, not claimed

Every policy decision, in under 1 millisecond.

Consent, suppression, quiet hours, jurisdiction, sector and every installed compliance pack — 27 policies can bear on a single send, and the ones that apply to a given workspace are evaluated to one decision. Not a claim somebody typed: a benchmark runs the real decision plane on every build and fails over the budget, so this page cannot state a number the product no longer meets.

Measured over 50,000 runs against the heaviest configuration — every compliance pack installed — rather than the lightest. The full request is slower than the decision inside it, and we publish the decision because it is the part we control absolutely.

Drop-in customer experiences

Ship the interface, not just the send.

Preferences, consent and data requests your users control, embedded in your product and enforced by the same rail that delivers. Each renders in a shadow root, so your CSS cannot break it and its styles cannot leak into your page.

The workspace API key never reaches the browser. Widgets authenticate with a short-lived, recipient-scoped token minted server-side — and the widget refuses a token that looks like an API key.

API first

Your integration should look this small.

Behind the call: contract resolution, schema validation, classification, policy evaluation, preference and consent resolution, template selection, routing, dispatch, evidence capture and webhook fan-out. None of it appears in the signature.

106 endpoints and 134 operations, generated from the same document the SDK is built from.

Compliance packs

On the roadmap · phase 2

Controls in the pipeline, not badges on a page.

Compliance packs are sets of executable controls — classification, detection, minimisation, redaction, retention and subject-access workflows — that run in the same pipeline as your sends. The control happens before sensitive data reaches logs, search or analytics, not after.

A compliance pack is a set of technical controls. It is not a certification, an attestation or a legal status, and we will not describe it as one. Genuine standing under health-privacy law also needs agreements no software can sign for you.

What is built, and what is next

Shipped work and planned work, told apart.

A page cannot let you tell shipped from planned unless it says so. These are the rails, with their real status from the registry that drives the build.

Built to compound

The capabilities share one communication model.

Templates share schemas. Packs share vocabulary. Widgets read the same preferences the rail enforces. Evidence, analytics and search all read the same canonical objects. Each capability is more useful because the others exist — which is a harder thing to reproduce than a send endpoint.

One layer, several jobs

Useful to more than the team that installs it.

Designed for teams building

Sector packs for the products people actually run.

Each sector pack installs the notification types, contracts and templates that sector needs, drawn from the same dictionary.

We do not show customer logos. When there are references worth naming, they will appear here with permission and not before.

Pricing

Priced on what is governed, not just what is sent.

Volume is a capacity dimension inside a plan, never the whole of it. Billing is metered from the evidence plane: a notification that policy denied produced no delivery and is not billed as one.

A rail your plan does not include is absent rather than locked — it does not appear in your dashboard or your API reference.

Add-ons

Secure by design

Communication infrastructure should reduce your attack surface.

Centralising communication means your application surfaces stop each holding delivery credentials, template implementations and logging pipelines of their own.