Cloud VPS 6 GB
Most popularA shell history sync server for you or a small team.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy hiSHtory Server hosting and run a self-hosted shell history sync server so one searchable, encrypted history follows you across every laptop, server and container. xCloud starts the pinned LinuxServer.io image with a SQLite database on a persistent volume, applies the registration cap you choose and publishes the sync API over HTTPS on your domain. The server has no browser interface: you point each machine's shell at it.
hiSHtory is a shell history tool, released under the MIT licence, that records each command with its context, such as the directory, exit code and duration, and syncs it end-to-end encrypted between your machines. Upstream supports bash, zsh and fish, a Control+R search with filters, and redaction of entries you did not mean to keep. The hiSHtory Server is the sync API behind it. A self-hosted hiSHtory Server keeps that traffic on infrastructure you run instead of the default one.
On xCloud the template runs the LinuxServer.io hishtory-server v0.335 image, pinned by digest, as one container with a SQLite database on the hishtory_config volume. It has no accounts and no web page: a client registers with the secret key it generates, and the registration cap you set is the only gate. History is encrypted on your machines, so the server cannot read it.
A self-hosted hiSHtory backend normally means running the server binary or container, persistent storage, a domain, a certificate and a way to limit who registers before the first command syncs. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick hiSHtory Server from the OneClick catalog. Choose your domain and target server, then set the Maximum number of users — it defaults to 1.
Step 02
One click. We bring up the LinuxServer.io hiSHtory Server image, pinned by immutable digest, as a single container with its SQLite database on the hishtory_config volume, apply your registration cap, and publish the sync API over HTTPS on your domain. The container is bound to localhost and reached only through xCloud's HTTPS proxy.
Step 03
On each machine, add export HISHTORY_SERVER=https://<your domain> to your shell profile and open a new shell. Run hishtory init on the first machine, then hishtory init <secret key> on the others, using the key from hishtory status. Register your own client straight away.
hiSHtory Server runs in full here: the sync API that the hiSHtory command-line client talks to, on your own domain, with its database on a volume you own.
Commands from your laptops, servers and containers land in one history, so a pipeline you wrote on a server is searchable from your laptop.
History is encrypted on your machines before it is uploaded, so the server stores only encrypted records and cannot read your commands.
hiSHtory records the directory, exit code and duration of each command, and the client can search on them from your terminal.
The hiSHtory client manages history for bash, zsh and fish; point it at your domain with one environment variable.
The server has no login. HISHTORY_MAX_NUM_USERS limits how many different history keys may register, and devices of an existing key can still join.
A single container with a SQLite database. Idle use measured about 48 MiB of RAM in QA.
Managed hosting for hiSHtory Server, so the parts that keep it online are not your problem.
Press Control+R and find a command you ran on another laptop or server, with its directory and exit code.
Sync through a server you run, with history encrypted on your machines before upload.
Set the maximum number of users so strangers cannot use your server once your own devices have registered.
Add a new machine with the secret key and see every command from the others in the same search.
Dedicated Cloud VPS sizes, pre-configured for hiSHtory Server hosting. Pick the one that fits, and resize any time.
A shell history sync server for you or a small team.
$24.99per month
More headroom if hiSHtory Server sits alongside other developer tools.
$59.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. hiSHtory Server itself is licensed by its maintainers under MIT.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy hiSHtory Server 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.
hiSHtory Server on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own the server. 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 hiSHtory Server Docker hosting, the template runs the LinuxServer.io hishtory-server v0.335 image, pinned by tag and digest, as a single container. It uses SQLite on one volume with no database sidecar, and xCloud's nginx serves HTTPS on your domain and forwards it to the API on container port 8080.
hiSHtory is open source under the MIT licence, so there is no licence fee for the server. xCloud bills for the dedicated Cloud VPS and the deployment. The client is installed separately on each machine, and the server needs outbound internet access to reach api.github.com.
The manifest asks for 128 MB of RAM, one CPU core and 1 GB of disk, since it is a small API with a SQLite file. The 6 GB plan here is many times that floor. Disk use grows only with the number of synced commands.
On each machine add export HISHTORY_SERVER=https://your-domain to the shell profile and open a new shell. Run hishtory init on the first machine, then hishtory init followed by the secret key from hishtory status on every further one. Register your own client right after install.
No. There are no accounts; a client registers with the secret key it generates, and every device holding that key shares one history. The registration cap is the only gate, so register first. Status pages under /internal/api/v1/ answer without authentication and list registration IP addresses.
Back up the hishtory_config volume, which holds the hishtory.db SQLite file. Stop the container first, or use SQLite's .backup command, for a consistent copy. Your clients also keep their own local history, but the secret key is needed to rejoin, so store it safely.
Version v0.335 is fixed by tag and digest, so a catalog update reaches new installs only. Back up hishtory_config, read the upstream release notes, then adopt a newer template version. Clients update themselves separately with hishtory update, so keep client and server versions in step.
No. Upstream stores history locally and syncs it end-to-end encrypted, so the server holds only encrypted records and cannot read your commands. It does see the registration IP addresses and device counts, which is why the status pages should not be left exposed.
Yes. hiSHtory Server cloud use gives the sync API its own Cloud VPS, a domain and a certificate; clients then set HISHTORY_SERVER to that address. A server from another provider can be connected as self-managed, and the template runs there unchanged.
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.