Cloud VPS 6 GB
Most popularA single Frigate NVR watched for one household.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Frigate-Notify hosting and add a self-hosted Frigate notifier that watches the Frigate NVR you already run and sends an alert with a snapshot to your phone. xCloud starts the pinned image, points it at your Frigate address, and sends alerts to the ntfy server and topic you chose, generating a hard-to-guess topic if you leave it empty. There is no web interface to log in to: settings live in one environment file.
Frigate-Notify is a small headless service, released under the MIT licence, that sends notifications from a Frigate NVR to the platforms you already use. Upstream lists polling the Frigate API or MQTT for events and delivery to Discord, Gotify, Matrix, Mattermost, ntfy, Pushover, Signal, SMTP, Telegram and webhooks, with many more through the Apprise API. It is a notifier rather than an NVR, and upstream says Home Assistant is not required. Self-hosted Frigate-Notify is the lightweight route when you want camera alerts without building automations around a larger home-automation stack.
On xCloud the template runs the official ghcr.io/0x2142/frigate-notify v0.5.4 image, pinned by digest, as one container with no database and no persistent volume. Frigate itself is not included: you supply its address and an alert destination. Settings are read at startup from the environment file, and the optional management API is published on the server's loopback address only.
Self-hosting a Frigate notifier normally means a container, an environment file of provider settings and a secret topic to keep straight before a single alert arrives. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Frigate-Notify from the OneClick catalog. Enter your existing Frigate server's URL — for example http://192.168.1.10:5000.
Step 02
One click. We bring up the official ghcr.io/0x2142/frigate-notify image pinned by immutable digest, point it at your Frigate server, and generate a private, hard-to-guess ntfy topic if you left that field empty.
Step 03
Save the ntfy topic from your protected installation credentials, subscribe to it in the ntfy app on your phone or desktop, and the next Frigate detection arrives with its snapshot.
Frigate-Notify runs in full here — detection alerts with snapshots, read from the Frigate NVR you already run.
Events are read straight from the Frigate API by polling, so no Home Assistant or MQTT broker is required.
Each alert carries the camera name, the detected object labels, a link back to the Frigate review and a snapshot image.
Leave the topic field empty and a hard-to-guess 24-character ntfy topic is generated at install, so you can subscribe and start receiving alerts immediately.
Discord, Telegram, Gotify, Matrix, Mattermost, Pushover, Signal, SMTP, webhooks and Apprise are all available through environment settings.
Set quiet hours, a custom alert title and a public Frigate URL for alert links, all through the environment file.
Settings live in the environment file, so alerting resumes by itself after an xCloud restart — there's no state to lose.
Managed hosting for Frigate-Notify, so the parts that keep it online are not your problem.
Receive a notification with a snapshot on your phone, via ntfy, each time Frigate raises a review.
Run the notifier next to your own ntfy server and keep alert content off third-party notification services.
Route Frigate events to Discord, Telegram, Matrix, Gotify or email instead of opening the Frigate interface.
Poll the aliveness endpoint from an uptime tool so you notice if camera alerts stop arriving.
Dedicated Cloud VPS sizes, pre-configured for Frigate-Notify hosting. Pick the one that fits, and resize any time.
A single Frigate NVR watched for one household.
$24.99per month
Notifications alongside other monitoring tools.
$59.99per month
Frigate-Notify alongside a whole self-hosted stack.
$84.99per month
Every size is a dedicated Cloud VPS we provision, patch, monitor and restore. Billed monthly with no lock-in — delete the server and the unused balance comes back to your account. Frigate-Notify itself is free under the MIT licence.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Frigate-Notify on it through the same panel, for a per-server management fee instead of a Cloud VPS rental.
Start your journey without cost.
$0forever
Your rate with 2–5 servers connected.
$5per server / month
The same platform, discounted at 6–10 servers.
$4per server / month
The same platform, discounted at 11+ servers.
$3per server / month
Priced per connected server, so your rate adjusts automatically as you add or remove servers. You pay your own provider for the server itself.
Frigate-Notify on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own the config. Stay in control.
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
From Server creation to application deployment, everything can be managed from our intuitive control panel.
See why agencies, developers, startups, and growing businesses choose xCloud to power their projects.
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising. Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Brian GeovannyI've been with runcloud for the last 3 years. However, after trying xcloud for the last month, I'm switching over. They are on a roll with their setup.
Kevin PinedaI'm moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud! #xCloud #wordpress #hosting
Leo KooHow Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
Ed EllinghamxCloud is like having an expert server team on call — without the big agency costs. It's given me back my time and given my clients peace of mind. Highly recommended for freelancers and small teams who want reliable performance and security.
Dumitru ButucelxCloud isn't just a solution. It's like one of that friend who got your back when you screw things up pretty bad.
Waqar AhmedTrust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahul SinghSo far my experience has been smooth like silk. I didn't imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included). For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation. I'm sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Massimo VillaCame from cloudways then to runcloud then to xcloud. Looks like I'm staying here.
Gerson ElI've recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud. I have to say, I'm really impressed with xCloud so far! The interface is definitely the standout feature for me.
Tony LewisI came from Cloudways and won't go back. Highly impressed with xCloud. Glad I gave them a chance.
Jared McDowellI like xCloud better than RunCloud, but one thing I'll point out is that some years ago RunCloud was hungry for business, the support was outstanding, and the community was active and helped each other. Maybe it was sold, there was a change in management, or they stopped being hungry, but the quality of the RunCloud offering declined and it hasn't been moving forward quickly. My point is that currently the xCloud team has the edge and it is theirs to keep or lose
David McCanHow Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
Kevin HeinrichsI had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
Dan SpinozaDear xCloud Team, I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It's a fantastic service, and my experience so far has been very positive. Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Rahil MaknojiaCame from runcloud. Tried xcloud and never came back.
Karl FanegaHow Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
Gary MoodyxCloud gave me what no other hosting platform could: the flexibility of a VPS with the convenience of managed WordPress. As a solo founder running an entire business on one server, that combination is an important unfair advantage.
Jorge de los Reyes MartínezI use Server Avatar and xCloud and I'll sooner use xCloud than Server Avatar personally.
Jay PaganoHow Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
Lori NewmanI too have moved over to xCloud. It's pretty sweet. One click n8n and uptime Kuma apps
John ApertureI went from Cloudways to xCloud. No intention on switching in the foreseeable future.
Blaine MooreFeel free to contact us with any questions or concerns you may have.
Yes. For Frigate-Notify Docker hosting, the template runs the official ghcr.io/0x2142/frigate-notify v0.5.4 image, pinned by digest, as a single container with no database or volume. Configuration arrives as FN_* environment variables from the install's environment file. The image has no shell, so no in-container health check runs.
The software is open source under the MIT licence, so the notifier has no licence fee. xCloud charges for the Cloud VPS and the deployment. Your alert destination is separate: the public ntfy.sh server is the default, or you can point the install at an ntfy server of your own.
The manifest asks for 256 MB of RAM, one CPU core and 1 GB of disk, because it is one small binary with no database. The 6 GB plan on this page is far above that floor, so it comfortably covers the notifier with room for anything else you run on the server.
No. This template deploys only the notifier. You need a running Frigate server that this server can reach, and you enter its address when you deploy. Frigate-Notify checks the address at startup, retries every 30 seconds for about two minutes, then exits and restarts if Frigate never answers.
The template asks for an ntfy server and topic, with ntfy.sh as the default. Upstream also lists Discord, Gotify, Matrix, Mattermost, Pushover, Signal, SMTP, Telegram and webhooks, and many more through the Apprise API. Add those by editing the environment file and redeploying, since settings are read only at startup.
The default alert mode is reviews, which needs Frigate 0.14 or newer. For an older Frigate, set FN_APP__MODE to events in the environment file and redeploy. Events are read by polling the Frigate web API every 30 seconds, and MQTT is the alternative event source upstream supports.
The API has no authentication, returns the running configuration including provider credentials, and accepts changes, so the template publishes it on the server's loopback address only and never through a domain. Do not expose that port publicly. If you place your own reverse proxy in front, add Basic Auth there.
There is no volume and no database, so there is nothing to restore from the container. Keep a private copy of the environment file contents, which holds your Frigate address, ntfy topic and any provider credentials. Treat that copy as sensitive, because a public ntfy topic is readable by anyone who knows it.
Version v0.5.4 is fixed by digest, so a catalog update does not alter the running notifier. Keep a copy of your environment file, read the upstream release notes, then adopt a newer template version when you choose. Configuration is re-read from that file on each start, so your settings carry over.
Yes. Frigate-Notify cloud use means a dedicated Cloud VPS sends the alerts. The one requirement is that your Frigate address must be reachable from that server; if it is not, the container exits at startup. Alternatively, connect a server from another provider as self-managed.
No. It is headless: alerts arrive in your notification app, and the only other surface is the loopback-only management API with its status and documentation pages. There is no dashboard or login, so you change behaviour by editing the environment file and redeploying.
Yes. There is no lock-in — cancel any time. Hosting is billed monthly and charged for what you actually use, so when you delete the server the unused balance is refunded to your account, less up to 10% in payment-processing fees.
Connect your first server in minutes. No plan you have to grow into.