#305 - Add note to Nextcloud: mobile push notifications rely on non-open sourced vendor-operated infrastructure and limited for self-hosted server - danb/isitreallyfoss - Codeberg.org
This website requires JavaScript.
danb/isitreallyfoss
Watch
Star
118
Fork
You've already forked isitreallyfoss
15
Code
Issues
179
Pull requests
Activity
Add note to Nextcloud: mobile push notifications rely on non-open sourced vendor-operated infrastructure and limited for self-hosted server #305
New issue
Open
opened 2026-06-17 11:06:40 +02:00 by woolfg
0 comments
woolfg
commented 2026-06-17 11:06:40 +02:00
Copy link
Project Name
Nextclolud
The issue
Nextcloud is FOSS. I think that is broadly correct and should not be changed. Nextcloud server and clients are open source, and Nextcloud is doing important work for self-hosting, privacy, and digital sovereignty.
However, I would suggest adding a short nuance about mobile push notifications. I might be missing some details here, so I am also interested in your opinion on whether this is relevant and how it should be framed.
Suggested nuance
Nextcloud itself is FOSS, but the mobile push notification path used by the official iOS and Android apps is not fully self-hostable in the same way as the main Nextcloud server.
The official store apps rely on Nextcloud’s central push proxy at push-notifications.nextcloud.com. Nextcloud documents that this proxy is needed because the official App Store and Google Play apps are signed with Nextcloud’s developer credentials, and push notifications for those apps need to be signed with credentials from the same developer account (see https://github.com/nextcloud/notifications/blob/master/docs/push-v2.md )
The important FOSS nuance is that the currently used Nextcloud push proxy itself does not appear to be publicly available as open source software. I could not find a public source repository or community deployment documentation for the service behind push-notifications.nextcloud.com. The long-standing issue about deploying a custom push proxy has been open since 2017 (see https://github.com/nextcloud/notifications/issues/82 ).
Nextcloud’s Fair Use Policy also states that centrally provided infrastructure, including notification services, is limited and “will not work” for installations with more than 500 users unless they use Nextcloud Enterprise or qualify for an exception (see https://nextcloud.com/fairusepolicy/ )
This is practically relevant especially for Nextcloud Talk, where mobile background notifications are important for timely chat messages and incoming call alerts.
Why this matters
This does not mean that Nextcloud as a whole is not FOSS. The point is narrower:
Nextcloud server and clients are open source.
The official mobile push path depends on a Nextcloud-operated push proxy.
The currently used push proxy service does not appear to be open source or publicly community-deployable.
Larger community deployments may hit the 500-user fair-use limitation.
A fully independent setup with the official store apps is not straightforward, because Apple/Google push credentials are tied to the app publisher.
Nextcloud offers branded clients and optional custom push proxy support as an Enterprise route:
https://nextcloud.com/blog/branded-nextcloud-clients/
There is also an important distinction from notify_push: that project is open source and self-hostable, but it is not the same as the Apple/Google mobile push proxy used for official mobile app background notifications (see https://github.com/nextcloud/notify_push )
Proposed wording
Maybe the Nextcloud page could add a note like:
Mobile push notifications are a practical exception worth noting. Nextcloud itself is FOSS, but background push notifications for the official iOS and Android store apps rely on Nextcloud’s central push proxy, because Apple and Google require app-publisher-specific push credentials. The currently used push proxy service does not appear to be publicly available as open source software or as a community-deployable component. Nextcloud’s Fair Use Policy limits centrally provided infrastructure, including notification services, for installations above 500 users. This is especially relevant for larger self-hosted Nextcloud Talk deployments, where mobile push notifications are important for chat messages and incoming call alerts. Enterprise branding customers can use branded mobile clients and an optional custom push proxy. This does not make Nextcloud non-FOSS, but it is a practical self-hosting limitation worth documenting.
Again, this is meant as a neutral clarification, not as criticism of Nextcloud overall. The technical and economic reasons are understandable, but it seems relevant for users evaluating practical self-hosting independence. What is your opinion on that?
### Project Name
Nextclolud
### The issue
Nextcloud is FOSS. I think that is broadly correct and should not be changed. Nextcloud server and clients...