Cloud VPS 6 GB
Most popularA Cal.diy instance for personal scheduling or a small team.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Cal.diy hosting and run the Cal.com community edition as self-hosted booking pages on a dedicated Cloud VPS. xCloud starts the pinned Cal.diy 6.2.0 image with a private PostgreSQL 16 database, generates the secrets and encryption key, switches public sign-up off and serves it over HTTPS on your domain. Upstream recommends it for personal, non-production use, so weigh that first before you rely on it for a business.
Cal.diy is the open-source community edition of Cal.com, a scheduling platform you can self-host. It offers public booking pages, availability from connected calendars, team and round-robin events and webhooks, and upstream describes Cal.com as the open-source Calendly successor. Run on your own server it is a self-hosted Cal.diy, an alternative to a hosted booking tool such as Calendly, under the AGPL-3.0. Upstream recommends this edition for personal, non-production use.
On xCloud it is deployed as two containers pinned by digest: an xCloud rebuild of the Cal.diy 6.2.0 source and a private PostgreSQL 16 database. The calcom_postgres volume holds everything, including avatars and encrypted calendar credentials. No email, scheduler or calendar integration is preconfigured, so you add the ones you need.
A Cal.diy install normally means a Next.js container, PostgreSQL, several secrets, an encryption key, a setup wizard, a domain and a certificate before the first booking page. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Cal.diy from the OneClick catalog. Choose a domain and a server; the install form has no application fields, because xCloud generates the database credentials, secrets and encryption key.
Step 02
One click. We start the xCloud-built Cal.diy 6.2.0 image and postgres 16, both pinned by digest, mount calcom_postgres, generate the NextAuth secret, encryption key and cron tokens, turn public sign-up off and publish HTTPS. Migrations take a few minutes.
Step 03
Open the site and complete the setup wizard at once: whoever submits it first becomes the administrator. Choose the AGPLv3 licence option, then add users from the admin area and create your first event type.
Cal.diy 6.2.0 runs here as a private scheduling server, with everything it stores kept in a PostgreSQL volume you own.
Publish public booking pages and event types, so people pick a time from your availability instead of trading emails.
Cal.diy reads availability from connected calendars. Google Calendar, Outlook and others need OAuth credentials you create with each provider.
Define team events and round-robin assignment, as upstream lists, so bookings rotate between the people you add.
Cal.diy supports webhooks. Queued deliveries need a scheduler calling its job endpoints, and this template does not run one.
Public sign-up is turned off. You add people from the admin area, or set NEXT_PUBLIC_DISABLE_SIGNUP to false to open registration.
The template sets CALCOM_TELEMETRY_DISABLED, and the Enterprise Edition directories in the image stay inactive without a licence key.
Managed hosting for Cal.diy, so the parts that keep it online are not your problem.
Share a link where clients pick a free slot from your calendar, with the bookings stored in a PostgreSQL database you control.
Use team and round-robin events so incoming bookings are shared between the people you add as users.
Move your own scheduling to a server you host, remembering that upstream advises personal, non-production use of this edition.
Send booking events to your tools through webhooks, after adding a scheduler to run the queued tasks.
Dedicated Cloud VPS sizes, pre-configured for Cal.diy hosting. Pick the one that fits, and resize any time.
A Cal.diy instance for personal scheduling or a small team.
$24.99per month
More users and headroom for Next.js and the database.
$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. Cal.diy is AGPL-3.0 licensed, with Enterprise Edition files under Cal.com's commercial licence.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Cal.diy 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.
Cal.diy 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.
No. Cal.diy is the open-source community edition of Cal.com, intended for people who want to self-host their own instance. Cal.com is the vendor's hosted and commercial product, and upstream points commercial or enterprise users to it. This page hosts Cal.diy only.
Yes, and this template is Cal.diy Docker hosting without the compose file: an xCloud-built image of the 6.2.0 source and postgres 16, both pinned by digest, with the calcom_postgres volume and an HTTPS route to port 3000. Upstream also documents Docker self-hosting.
Upstream says use at your own risk and that Cal.diy is strictly recommended for personal, non-production use, and points commercial or enterprise users to Cal.com. Weigh that before relying on it for a business, and keep your own backups.
The template baseline is 1 GB of RAM, 2 CPU cores and 10 GB of disk. Next.js, the first-start migration and the app-store seed step all need memory, so more helps with concurrent users. This page sells the 6 GB tier.
Not by default. Outgoing email is off until you add EMAIL_SERVER_HOST, EMAIL_SERVER_PORT, EMAIL_SERVER_USER, EMAIL_SERVER_PASSWORD and EMAIL_FROM in the Environment editor and redeploy. Until then booking confirmations and reminders are not sent to anyone, so test a booking end to end first.
Create OAuth credentials with the provider, then set them as environment variables following upstream's per-integration instructions and redeploy. No integration credentials are part of this template, so calendars stay unconnected until you add your own.
No scheduler ships with the template. Cal.diy relies on an external scheduler calling its job endpoints, so without one booking pages work but timed reminders and queued webhook or workflow tasks do not run. The tokens are in the Environment editor.
The release is AGPL-3.0, except upstream's Enterprise Edition directories, which are under Cal.com's commercial licence and need a subscription in production. No key is set here, so those features stay inactive. Your plan pays for the dedicated Cloud VPS.
Back up the calcom_postgres volume together with NEXTAUTH_SECRET, CALENDSO_ENCRYPTION_KEY and the database password. Without the matching encryption key a restored database cannot decrypt stored calendar credentials. Nothing is scheduled by default, so turn on scheduled backups and rehearse a restore.
Nothing upgrades itself: your install stays on Cal.diy 6.2.0 and PostgreSQL 16, both pinned by digest, until you adopt a newer template version. Before you do, back up the calcom_postgres volume with NEXTAUTH_SECRET and the encryption key, and read the upstream release notes. Keep the encryption key unchanged for the life of the installation.
It is Cal.diy on a dedicated Cloud VPS under your xCloud login, a Cal.diy cloud of your own at your domain, not the vendor's hosted Cal.com. The first person to finish the setup wizard becomes administrator, so complete it straight after install.
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.