Cloud VPS 6 GB
Most popularOne CrowdSec Local API, comfortably above the template floor.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
CrowdSec hosting runs a Local API that collects detections and serves block decisions to your bouncers: detect here, remedy there. Deploy CrowdSec v1.8.1 as a self-hosted security engine: xCloud runs the pinned image, pre-registers a bouncer with a generated API key, keeps decisions and configuration on persistent volumes, and receives the Community Blocklist by default. It detects locally only once you add log sources.
Self-hosted CrowdSec is a security engine. Its README calls it an open-source and participative security solution offering crowdsourced server detection and protection against malicious IPs: the Security Engine is an all-in-one IDS, IPS and WAF that detects bad behaviour by analysing log sources and HTTP requests, and remediation components, called bouncers, act on its decisions, following a detect here, remedy there approach. Detection rules on its Hub are MIT licensed. It is used in place of paid IP reputation feeds or per-host scripts.
On xCloud the template runs the crowdsecurity/crowdsec v1.8.1 image as one container pinned by immutable digest, with crowdsec_data and crowdsec_config volumes. The Local API is published on a dedicated server TCP port as plain HTTP, with no web UI and no domain, and a bouncer named default is registered with a generated key. It registers with the CrowdSec Central API by default.
Self-hosting CrowdSec normally means a Docker host, hub-content bootstrap and a bouncer registration step before the first decision is served. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick CrowdSec from the OneClick catalog. There are no extra fields — xCloud generates the Bouncer API Key.
Step 02
One click. We bring up the pinned CrowdSec v1.8.1 image, register the default bouncer with a generated API key, and publish the Local API on a dedicated server port.
Step 03
Point a bouncer at the Local API URL with the Bouncer API Key, then mount log sources and configure acquisition so CrowdSec has something to analyse.
The CrowdSec Security Engine runs in full here — detection, decisions and the Community Blocklist, on infrastructure you control.
Bouncers — firewall, reverse proxy, CDN — query one Local API for block decisions, decoupling detection from remediation.
Registered with the CrowdSec Central API by default: share signals, receive the curated list of malicious IPs. Opt out any time.
Detect brute force, port scans, web scans and more from the CrowdSec Hub — add collections such as crowdsecurity/nginx or crowdsecurity/sshd.
A bouncer named 'default' is ready with a generated API key from first boot — no manual cscli bouncers add step.
Decouples detection from remediation and lets remote agents report into one central place instead of each host acting alone.
Decisions, configuration and credentials all survive an xCloud Restart — verified: the key was not re-registered.
Managed hosting for CrowdSec, so the parts that keep it online are not your problem.
Point your firewall, reverse proxy or CDN bouncers at one Local API, so detection and remediation are decoupled and every host benefits from the same decisions.
Registered with the Central API by default, your install shares signals and receives the curated list of malicious IPs, which you can opt out of with DISABLE_ONLINE_API=true.
Mount log sources and configure acquisition, then add Hub collections such as crowdsecurity/nginx or crowdsecurity/sshd to detect brute force, port scans and web scans on your servers.
Connect agents on other machines so they report into one central place instead of each host acting alone, which is the centralised model the README describes.
Dedicated Cloud VPS sizes, pre-configured for CrowdSec hosting. Pick the one that fits, and resize any time.
One CrowdSec Local API, comfortably above the template floor.
$24.99per month
More log sources and higher decision volume.
$59.99per month
CrowdSec alongside a whole self-hosted stack.
$84.99per month
CrowdSec is free and open source under the MIT license; this is the managed server it runs on. The template manifest asks for 1 CPU core, 512 MB of RAM and 2 GB of disk. This page sells the 6 GB tier. Every size is a dedicated Cloud VPS we provision, patch, monitor and restore.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy CrowdSec 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.
CrowdSec on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own your detections and decisions. 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.
The manifest sets CrowdSec's floor at one core, 512 MB of RAM and 2 GB of disk, and QA measured about 75 MB idle, growing once log sources are mounted. The 6 GB Cloud VPS sold on this page leaves plenty of room as you add acquisition and Hub collections.
Yes. CrowdSec is MIT licensed, per the LICENSE at the v1.8.1 tag, and its Hub detection rules are MIT too. There is no licence fee for the engine. xCloud bills only for the dedicated Cloud VPS. The separate Console is an optional enrolment with its own terms.
Yes, and this is CrowdSec Docker hosting prepared for you: the template runs the official crowdsecurity/crowdsec v1.8.1 image as one container, pinned by immutable digest, with crowdsec_data and crowdsec_config volumes and the Local API on its own server port. No compose file is yours to write.
Per its README, CrowdSec takes a detect here, remedy there approach: it analyses logs from several sources in one place, and bouncers block at a firewall, reverse proxy or CDN on another machine. Users also share the threats they face, feeding the Community Blocklist.
Use the Local API URL and the Bouncer API Key from your installation credentials; the key belongs to the pre-registered default bouncer, so no cscli bouncers add step is needed. Valid key returns 200, a missing or wrong key gets 403, and /health needs no key.
No. It receives the Community Blocklist by default, but it detects local attacks only once you mount log sources and configure acquisition, or connect remote agents. And the engine only decides: something still has to enforce, through a bouncer, so install one on the machine that should block.
No. It is plain HTTP on a raw server TCP port, with no domain and no xCloud-managed HTTPS, so restrict it to trusted IPs at the server firewall and do not treat it as encrypted transport. There is also no web interface; the Prometheus metrics port is not published.
By default yes: the install registers with the Central API, shares signals and receives the Community Blocklist. Set DISABLE_ONLINE_API=true in the Environment editor to opt out, at the cost of losing the blocklist. Linking the optional Console is a separate enrolment you choose.
A backup is both persistent volumes, crowdsec_data for the runtime database and decisions and crowdsec_config for configuration, registration and credentials, taken together as a consistent pair with writes paused. Keep the bouncer key with them, and test a restore.
Nothing upgrades it for you: the image is pinned at v1.8.1 by immutable digest. Existing installs keep their image until you adopt a newer template version. Read the upstream release notes, take fresh backups of both volumes, apply the newer template version, and confirm your bouncers still authenticate afterwards.
It is your own Local API on a dedicated Cloud VPS provisioned by xCloud, not a hosted CrowdSec service, and not an official CrowdSec offering. The container, both volumes and the bouncer key belong to your install, and no partnership is implied.
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.