Email that stays on your infrastructure

Why public organisations self-host

A hosted marketing platform puts residents' email addresses, names and reading habits on someone else's servers, under someone else's sub-processors. For a public body, that means a data processing review for every campaign tool — and a dependency you cannot inspect.

Self-hosted, the picture is simpler: the software runs where your other systems already run, the database is yours, and the code can be read by your own teams.

What you can verify before you buy

• The code. The source is public, and each release becomes AGPL-3.0 after four years.
• The licence. What needs a key, what never will, and what happens without one — written, dated and versioned on our licence page.
• The security process. Private vulnerability reports, a reply within three business days, fixes in the latest release with a public advisory. Details on our security page.
• Access control. Single sign-on through your identity provider, granular permissions, and audit logs of admin actions.
• No phone-home. Licence keys are checked locally. Nothing about your installation is sent to us.

An example

Illustrative scenario — not a customer case.

A group of municipalities runs Notifuse on its shared infrastructure. Each town has its own workspace, contacts and domain; the shared IT service keeps the templates and the settings. Staff sign in through the organisation's identity provider, and admin actions are kept in audit logs. Newsletters and transactional messages — registration confirmations, service alerts — go out through the provider the group already uses.

Each workspace is isolated in its own database, so one town never sees another town's residents.

How purchasing works

Standard licences are bought online. Larger deployments — several entities, more than fifteen workspaces, specific requirements — use a Custom licence: quoted per deployment, with purchase-order purchasing. Paid licences include private email support in English and French, Monday to Friday.