Cloud VPS 6 GB
Most popularA Temporal dev server for a team's experiments.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Temporal hosting and run a self-hosted workflow engine for development and small internal workloads on a dedicated Cloud VPS. xCloud starts the pinned Temporal 1.9.1 development server with its web UI behind a Basic Auth gateway, generates the password, keeps workflow history in an embedded SQLite file on a persistent volume and binds the unauthenticated gRPC port to the server's loopback address only.
Temporal is a durable execution platform that lets developers build scalable applications without sacrificing productivity or reliability. Its server executes units of application logic called Workflows in a resilient way, handling intermittent failures and retrying failed operations, and it originated as a fork of Uber's Cadence. Run on your own server it is a self-hosted Temporal, an alternative to a cloud orchestrator such as AWS Step Functions or Temporal Cloud, under the MIT licence.
On xCloud it is the Temporal CLI's single-node development server, temporalio/temporal 1.9.1 pinned by digest, with an embedded SQLite file on the temporal_data volume. A pinned nginx gateway adds Basic Auth to the web UI, and the gRPC port is loopback-only. It is not Temporal's production cluster.
A Temporal dev server normally means the CLI image, a database file, an authentication layer for the web UI, a safely bound gRPC port, a domain and a certificate before the first workflow. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Temporal from the OneClick catalog. Choose a domain and a server; the install form has no application fields because xCloud generates the gateway password.
Step 02
One click. We start temporalio/temporal 1.9.1, pinned by digest, as the start-dev server with SQLite on the temporal_data volume, put a pinned nginx Basic Auth gateway in front of the web UI, bind gRPC to loopback and publish HTTPS. It is usually ready in about a minute.
Step 03
Sign in to the web UI as temporal with the generated password. For workers and the CLI, open an SSH tunnel to the loopback gRPC port, or run them on the same Docker network, and use the default namespace.
Temporal 1.9.1 runs here as a single-node development server, with its history kept in a file on a volume you own.
The Temporal server executes Workflows in a resilient manner, handling intermittent failures and retrying failed operations for your application logic.
Temporal's web UI has no authentication of its own, so the template puts a Basic Auth gateway with a generated password in front of it.
SDK clients, workers and the CLI use the gRPC frontend, which has no authentication, so it is bound to 127.0.0.1 and reached through an SSH tunnel.
Workflow history lives in one SQLite file on the temporal_data volume. Removing the volume deletes all history and recreates an empty default namespace.
Add start-dev options such as a namespace through TEMPORAL_EXTRA_ARGS and redeploy. An unknown option makes the container exit, so test changes carefully.
This is the development server: one process, no high availability. Upstream does not intend it for production, so size it for experiments and small internal use.
Managed hosting for Temporal, so the parts that keep it online are not your problem.
Give developers one shared server and UI to test workflows against, instead of each person starting a local dev server on a laptop.
Write Workflows with the Temporal SDKs, run them against this server and watch retries and history in the UI, knowing it is a development setup.
Run low-volume internal jobs that need retries and durable state, accepting a single node, an SQLite file and no high availability.
Connect SDK workers over an SSH tunnel and explore namespaces, workflows and history in the web UI without paying for a managed cluster.
Dedicated Cloud VPS sizes, pre-configured for Temporal hosting. Pick the one that fits, and resize any time.
A Temporal dev server for a team's experiments.
$24.99per month
Room for workers and Temporal beside other services.
$59.99per month
Temporal alongside a heavier 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. Temporal itself is released under the MIT licence.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Temporal 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.
Temporal on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own your data. 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, and this template is Temporal Docker hosting without the compose file: the temporalio/temporal 1.9.1 image running start-dev, plus a pinned nginx gateway for Basic Auth, with the temporal_data volume. Upstream's CLI README shows the same image with the dev server listening on an external IP.
No. Upstream describes this as a development server, and here it is one process with an embedded SQLite database, no high availability and no authentication of its own. Use it for development and small internal workloads, and plan a proper cluster for production.
The gRPC port 7233 has no authentication, so it is published on the server's loopback address only. Open an SSH tunnel to the host port shown in the endpoints, or run the worker on the same Docker network, and use the default namespace.
The template does it for you: a pinned nginx gateway asks for a username, temporal, and the generated password before proxying to the UI. That login is the template's own addition. Keep the password private and rotate it by editing GATEWAY_PASSWORD.
The template manifest asks for 256 MB of RAM, 1 CPU core and 2 GB of disk for the dev server and the gateway. This page sells the 6 GB tier, which leaves ample room for workers or other apps on the same server.
In one SQLite file on the temporal_data volume, mounted at /home/temporal. Workflow history is stored there, and removing the volume deletes it all and recreates an empty default namespace. The platform does not back this volume up for you.
Copy the temporal_data volume, which holds the SQLite file, ideally with the server stopped for a consistent copy. Nothing schedules the backup, so do it yourself and test a restore. Remember it is a development database, not a replicated store.
Nothing upgrades itself: 1.9.1 is pinned by digest, bundling Temporal Server 1.32.0 and UI 2.54.1. To upgrade, back up temporal_data, read the release notes, then adopt a newer Temporal template version when xCloud publishes one. Extra start-dev options go in TEMPORAL_EXTRA_ARGS.
Yes. Temporal and its CLI are released under the MIT licence, so the software costs nothing to run. Your plan pays for the server underneath. It is developed by Temporal Technologies, a startup by the creators of Cadence.
Yes, through TEMPORAL_EXTRA_ARGS in the Environment editor, for example a namespace or a UI flag. Save and redeploy to apply. An unknown option makes the container exit, so add one at a time and check the logs.
It is a Temporal development server on a dedicated Cloud VPS under your xCloud login, a Temporal cloud of your own but not Temporal Cloud and not highly available. Plan on one node, one SQLite file and an SSH tunnel for workers.
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.