The main disadvantages of self-hosted push notifications are that you run the server, handle uptime, updates and backups, and still depend on browser push services such as Firebase Cloud Messaging (FCM) for delivery. You also pay for a VPS and, with most paid panels, a licence that covers one server. Those trade-offs are the price of owning the subscriber list.
I like self-hosted software, so I would rather be honest about the downsides than sell the category as a free lunch. This post is only about the drawbacks. If you want the balanced comparison, I already wrote self-hosted vs SaaS push notifications. Below is what you take on when you install the panel yourself.
Quick facts:
- You own the subscriber database and keys, but you also own restarts, patches and backups.
- Delivery still goes through the browser’s push service. Chrome uses FCM, Firefox uses Mozilla’s service and Safari uses Apple’s, as the Push API model requires.
- A small VPS is usually enough, but it is a recurring host bill on top of the licence.
- LaraPush has no free plan, and one licence covers one server. Support windows are limited after the included term.
What are the main disadvantages of self-hosted push notifications?
The main disadvantages of self-hosted push notifications are operational, not a weaker notification format. The messages still look like ordinary web push. What changes is who keeps the system alive.
In practice, the downsides cluster into five groups:
| Disadvantage | What it means for you | Who feels it most |
|---|---|---|
| You run the server | You rent a VPS, apply updates and watch disk space | Anyone without a regular server habit |
| Uptime is yours | If the panel or queue stops, sends wait | Sites that send time-sensitive alerts |
| Backups are yours | A lost disk can take the subscriber list with it | Anyone who has no restore plan |
| Delivery is not fully self-hosted | FCM, Mozilla or Apple still carry the last hop | Teams who expected a fully offline stack |
| Cost is licence plus hosting, not zero | You pay for the VPS, and often for one server only | People comparing it with a free SaaS tier |
None of those is a reason to avoid self-hosting on its own. However, each one is a reason to pause if you wanted “set it and forget it” software.
Do you have to manage the server yourself?
Yes. With self-hosted push notifications, you or someone you appoint has to manage the server. The vendor can install the panel and answer support questions, but the VPS still sits in your account.
That work includes creating the server, pointing a domain at it, keeping the operating system patched, and checking that the web server, database and queue worker are running after a reboot. Even when installation is automated, as it is with LaraPush, those surrounding jobs stay with you. If nobody on your team is comfortable in a hosting panel, this is the first disadvantage that should stop the purchase.
You do not need to become a systems engineer. You do need a named person who can log in, restart a service and restore a backup. If that person leaves, write down the steps before they go.
What happens to sending when the server has a problem?
When the self-hosted push server has a problem, new campaigns usually cannot go out until the panel and its queue are back. Existing subscriptions on the user’s device are not deleted just because your VPS is down, but they will not receive a new message from you during the outage.
That is different from a SaaS outage, where the vendor’s status page and staff are responsible for the fix. With self-hosting, you are the status page. A queued campaign may resume after a restart, but only if the worker is running and the database is intact. So monitoring and backups are not optional extras. They are how you reduce this disadvantage.
For the install sequence and the queue’s role, see how to install a self-hosted push panel on a VPS. I would rather spend an hour on a restore plan than discover a missing backup after a disk failure.
Do self-hosted push notifications still depend on third parties?
Yes. Self-hosted push notifications still depend on the push service each browser chooses. You host the dashboard and the subscriber list, but you do not host Chrome’s, Firefox’s or Safari’s delivery network.
The Web Push protocol (RFC 8030) is designed that way. Your server encrypts the payload, signs it and posts it to the subscription endpoint. The browser vendor’s service then wakes the device. In other words, “self-hosted” describes where the list and the sending software run, not the entire delivery path.
Some panels also require a Firebase project for configuration, even though FCM delivery itself can be no-cost. That is another third-party account to create and keep safe. If you wanted a stack with no Google or Apple dependency at all, web push will not give you that, whether the panel is self-hosted or SaaS.
How much extra cost is there beyond the licence?
Beyond the licence, you pay for the VPS and for your own time. There may also be a new licence if you need a second server, and a paid upgrade if you want a later major version.
The VPS bill is the obvious extra. A small server is enough for many setups; LaraPush’s llms.txt says 1 GB RAM and 1 vCPU is enough. I will not invent a monthly price, because hosts and regions differ. Count whatever your provider charges, plus the domain if you need a new one, and the time spent on updates.
Paid panels often cap the licence at one server. LaraPush does this, while allowing unlimited domains and subscribers on that server. That is fine until you want a separate staging server or a second region. Major version upgrades, for example a jump from v2 to v3, are a separate optional purchase rather than a lifetime update promise. Compared with a free SaaS tier, the first year can therefore cost more. Compared with a large per-subscriber SaaS bill, the same setup can cost less over time. The disadvantage is simply that the cost does not start at zero.
Who should not choose self-hosted push notifications?
You should not choose self-hosted push notifications if you want a free start, if nobody can look after a VPS, or if you only need a tiny list for a short campaign. In those cases a hosted tool is the more honest fit.
I would also steer you away if you need native mobile app push as the main channel, because a web-push panel is not an APNs and FCM mobile-app suite. And if your team cannot accept weekday support hours, check the vendor’s window before you buy. LaraPush support is Monday to Friday, 09:00–18:00 IST, for 6 months on Startup and 12 months on Pro.
If you are still choosing from the wider market, the best push notification services and tools pillar and the best self-hosted push notification software list put those trade-offs next to other options.
Can you reduce the downsides?
You can reduce the downsides, but you cannot remove them entirely. The useful mitigations are simple and should be in place on day one.
- Pick a panel with automated installation, so you are not debugging a manual stack on the first afternoon.
- Use a VPS provider that offers snapshots, and also export or back up the panel’s data.
- Write a one-page runbook: where the server is, how to log in, how to restart the queue, and how to restore a backup.
- Subscribe from your own devices and send a test after every update.
- Watch disk space and the queue, not only the campaign editor.
LaraPush can help with some of this: free installation, documented backups, and automated Google Drive backups on the Premium Add-on. The VPS and the runbook are still yours.
Where does LaraPush fit?
LaraPush is a self-hosted web push panel, so it has the disadvantages above and the benefits that come with them. You install it on your VPS, you own the subscriber data, and you pay a one-time licence from $499 (Startup) or $799 (Pro), exclusive of tax. See pricing for the current figure. Unlimited domains and subscribers run on that one licensed server.
The honest trade-off is the same as the category’s: no free plan, you maintain the server, and you connect Firebase when you add a site. If you want that model, start with the features overview and the setup guide. If you do not want to run a server, choose a SaaS tool instead.
Frequently asked questions
Not by design. Both send through the same browser push services. Reliability depends on how well the sending server is run. With SaaS, the vendor does that work. With self-hosting, it depends on your VPS, your queue and your monitoring. A well-run small server can be perfectly reliable.
You do not automatically lose the subscriptions stored in the browser. However, you cannot send new notifications while the panel or queue is down, and you can lose the list if the server’s disk fails and you have no backup. Uptime and backups are what protect you.
No. You also pay for the VPS, and you spend time on updates and backups. If you need another server, you may need another licence. If you want a later major version, that upgrade can be a separate purchase. Compare the full cost, not only the licence price.
Sometimes. The Web Push protocol and VAPID keys can work without a Firebase project, although Chrome still delivers through FCM behind the scenes. Some commercial panels still ask you to add Firebase config. I explain that distinction in self-hosted web push without Firebase.
They outweigh the benefits when nobody can maintain the server, when you only need a small temporary list, or when you wanted a free plan with no hosting work. They are usually acceptable when you want data ownership, a flat licence and several sites on one server.




