✨ Question: Adding new Push Provider – IO App (official Italian government service)

[francescor]

TL;DR:
We’ve implemented support for a new official Push Provider: [IO app](https://ioapp.it/), the notification and digital services platform of the Italian State (addressed to all Italian citizens).

• ✅ pnpm run test:providers passes
• 🙋 We’d like to know:
  1. How long does it usually take for such a provider PR to be merged and included in official Docker images?
  2. How can we build Novu’s Docker images locally (monorepo structure) so we can test the provider in our QA Docker Swarm environment before submitting the PR?

---

Hello Novu Team 👋,

First of all, thank you for your amazing work on this project 🙏. Novu is an outstanding platform that makes handling notifications across multiple channels simple and powerful. We greatly appreciate the effort of the contributors and maintainers, and we’re excited to contribute back. 🚀

We’re currently developing support for a new Push Provider: [IO app](https://ioapp.it/).

About IO

For context:

• IO is the official application of the Italian State, developed and distributed by PagoPA S.p.A. on behalf of the government.
• It is designed as the single digital channel through which Italian citizens interact with Public Administration (PA) services.
• With IO, users can:
  • Receive official communications and notifications from municipalities, universities, ministries, healthcare, transport networks, etc.
  • Get legal-value notifications (SEND), which otherwise arrive by paper mail.
  • Pay taxes, school fees, fines, and other administrative costs via pagoPA integration.
  • Store personal documents (driver’s license, Tessera Sanitaria, European Disability Card, etc.).
• IO is nationwide, used by all Italian residents, and represents the official trusted system for interactions with Italian public administration. 🇮🇹

We believe that adding IO as a push provider to Novu would be extremely valuable, especially for services operating in Italy that need to deliver trusted, government-certified communications.

Motivation / Community Value

While IO is a government-specific provider for Italy, we also believe it has strategic value for the broader Novu community:

• It shows that Novu can easily integrate with government-backed digital identity and notification platforms — something that many countries are starting to roll out (e.g. France’s FranceConnect, Estonia’s digital services, Germany’s BundID, etc.).
• It demonstrates that Novu can support not only commercial SaaS / cloud channels (Slack, Twilio, Firebase, etc.) but also citizen-facing platforms with legal value and compliance requirements.
• This contribution could serve as a blueprint for others who want to add similar integrations in their own countries.

Contribution Process

We’ve followed the recommendations in your documentation here:
👉 [Add a New Provider – Novu Docs](https://docs.novu.co/community/add-a-new-provider)

✅ Our implementation passes pnpm run test:providers successfully.

Before submitting a Pull Request, we’d like to ask a couple of clarifications:

1. PR Merge & Release Timeline

   • Once a new provider PR is submitted, how long (approximately) does it typically take before review and merge?
   • After merging, when can we expect the provider to be available in the official Novu Docker images, so that users can rely on it in production deployments?

2. Testing the IO Provider with Docker (QA Environment)

   • Before creating the PR, we’d like to test the IO provider in our internal QA environment (Docker Swarm) to make sure everything works end-to-end.
   • Could you guide us on the recommended workflow for building Novu’s Docker images locally (with our provider changes included)?
   • Specifically: which Dockerfiles or steps should we follow to ensure compatibility with the monorepo and image structure used by Novu?

Thanks again for your support 🙌. We’re looking forward to contributing IO as a new push provider and helping Italian services integrate seamlessly with Novu — while also setting a precedent for other state-backed notification platforms worldwide. 🌍

/francesco
OpencityLabs
https://opencitylabs.it/

[linear]

NV-6565 ✨ Question: Adding new Push Provider – IO App (official Italian government service)

[lorello]

/lorello here, CTO @ opencitylabs

I would also like to add that we would be happy to add novu to the European open source software catalog, as we have already done for our own software: https://interoperable-europe.ec.europa.eu/eu-oss-catalogue/solutions?oss_keys=opencity&sort_by=date

In this context, the presence of a push provider for one European country could stimulate the creation of other push providers for wallets in other countries. This is a highly developed area right now, thanks to the momentum of the e-idas project.

Finally, if the App.io provider were available in the SaaS version, I would be very happy to rely on your service instead of self-hosting.

[scopsy]

Thank you so much @francescor and @lorello I'll address the open questions here:

PR Merge & Release Timeline

Once a new provider PR is submitted, how long (approximately) does it typically take before review and merge? This depends on the PR size, and our ability to test it. But once submit I will personally make sure we will be able to merge this in the one to two weeks range
After merging, when can we expect the provider to be available in the official Novu Docker images, so that users can rely on it in production deployments? It is usually available on our cloud solution in the following day, we usually release a new community edition version every 2-4 weeks depending on progress.
Testing the IO Provider with Docker (QA Environment)

Before creating the PR, we’d like to test the IO provider in our internal QA environment (Docker Swarm) to make sure everything works end-to-end. Usually what we do is just running the project locally without docker (just pnpm start) of the env. And later do another set of tests on our staging environment (dockerized)
Could you guide us on the recommended workflow for building Novu’s Docker images locally (with our provider changes included)?
Specifically: which Dockerfiles or steps should we follow to ensure compatibility with the monorepo and image structure used by Novu? **Nothing specific, my suggestion would be to take an existing push provider like expo for example, and adjust it as needed. **

Here is the guide for new providers: https://docs.novu.co/community/add-a-new-provider

Please let me know if you will need any further help on it 🙏