Cloud VPS 6 GB
Most popularA private forecast endpoint for your own apps and automations.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Open-Meteo hosting and serve weather forecasts from your own domain. xCloud runs the pinned Open-Meteo 1.6.0 image as a single container, mounts a persistent volume for the local cache and publishes the API over HTTPS in minutes — weather data is downloaded on demand from the public Open-Meteo data store, so there is no data sync to set up and no per-call limits from the hosted service.
Open-Meteo is an open-source weather API. Upstream builds it from open forecasts published by national weather services, processes them into a compressed time-series file format and serves them through an HTTP API written in Swift that compiles to a single binary. The hosted service at api.open-meteo.com needs no API key and is free for non-commercial use.
This template runs the upstream server as a single container on your own xCloud server. It downloads weather data on demand from the public Open-Meteo data store and keeps a local cache, so you can serve /v1/forecast requests from your own domain. Upstream licenses the server under AGPL-3.0 and the weather data under CC BY 4.0, and states that self-hosting is available for commercial use.
A self-hosted weather API normally means pulling an image, pointing it at a data source, mounting a cache volume, adding a domain and a certificate before the first forecast. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Open-Meteo from the OneClick catalog. Choose your domain and target server — there are no credentials to generate and no extra fields to fill in. Avoid a domain containing open-meteo.com: the server treats those hosts as the hosted service and answers 404.
Step 02
One click. We bring up the official Open-Meteo 1.6.0 image, pinned by immutable digest, as a single container with no other services, mount the open_meteo_data volume for the local cache, and publish the API over HTTPS on your domain. It is usually healthy within about a minute.
Step 03
Open https://your-domain/v1/forecast?latitude=52.52&longitude=13.41&hourly=temperature_2m and read the JSON response. The site root returns 404 by design — it is an API only. The first request for a location is slower while data is fetched and cached.
Open-Meteo runs in full here: a weather forecast API on your own domain, backed by a local cache you own.
Serve /v1/forecast requests from your own HTTPS address for apps, dashboards and automations, instead of sending them to someone else's endpoint.
Weather data is downloaded from the public Open-Meteo data store (REMOTE_DATA_DIRECTORY) when a request needs it, so no manual data sync is required.
Downloaded data is cached in the open_meteo_data volume, and repeat requests for a location are served from it. CACHE_SIZE sets the cache file's maximum size; this template defaults to 5GB.
There is no sign-in and no administrator setup. The API answers anyone who can reach the site, so add your own access layer such as HTTP Basic Auth if it should not be public.
The API answers CORS requests with Access-Control-Allow-Origin: *, so a web page can call it directly from the browser.
Concurrency limits, log level, maximum request body size and more are listed as commented settings in the environment file. Change them, then Save & Redeploy.
Managed hosting for Open-Meteo, so the parts that keep it online are not your problem.
Point a web or mobile app at your own /v1/forecast endpoint, and answer its requests from a server you control.
Feed forecast values such as hourly temperature into dashboards, scripts and home or office automations over a plain HTTPS request.
Upstream notes that self-hosting pays off for workloads with enough repeated calls to benefit from caching: repeat requests for a location are served from the local cache.
The per-visitor call limits of the hosted service do not apply on your own domain, so request volume is bounded by your server and the concurrency settings you choose.
Dedicated Cloud VPS sizes, pre-configured for Open-Meteo hosting. Pick the one that fits, and resize any time.
A private forecast endpoint for your own apps and automations.
$24.99per month
More headroom for a larger cache and heavier request volume.
$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. Open-Meteo itself is licensed by its maintainers under AGPL-3.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Open-Meteo 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.
Open-Meteo 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.
No. Data is fetched on demand from the public Open-Meteo data store (REMOTE_DATA_DIRECTORY) and cached locally in the open_meteo_data volume.
You don't: Open-Meteo is an API only, with no web interface, accounts or administrator setup. The site root returns 404 by design; request forecasts at /v1/forecast.
Nothing. It is a single container with no database or other private services.
Yes. There is no built-in authentication, so anyone who can reach the site can query it, and every request uses your server's CPU, cache and outbound bandwidth. If that matters, put your own access layer such as HTTP Basic Auth in front of the API.
Weather data is fetched from the public data store and cached the first time it is needed. Repeat requests for that location are served from the local cache. Upstream notes a self-hosted instance is generally slower than the free hosted API, especially while the cache is cold.
Avoid a domain containing open-meteo.com. The server treats such hosts as the hosted service and answers 404.
Nothing essential. The open_meteo_data volume holds only cached data that is re-downloaded on demand, so a volume backup is optional.
Yes. CACHE_SIZE sets the maximum size of the cache file, which is reserved inside the open_meteo_data volume. This template defaults to 5GB; keep it below your free disk space, then Save & Redeploy after changing it.
Yes. The x86-64 build requires a CPU with AVX2.
No. The template pins Open-Meteo 1.6.0 by immutable digest; new installations use the pinned release, existing sites are not automatically upgraded. Read the upstream release notes, then bump the readable tag and digest together on your own schedule. Server-level backups and snapshots are available on every Cloud VPS.
The template's baseline asks for 1 CPU core, 512 MB of RAM and 10 GB of disk; measured idle use in QA was about 21 MiB. Upstream recommends 8 GB of RAM and 100 GB of disk for a heavily used self-hosted API, and this page sells the 6 GB tier as the entry rung, with headroom for the cache and traffic.
Data on the open_meteo_data volume — the cached data survived an xCloud Restart in QA, because it is a persistent named volume.
Upstream licenses the weather data under CC BY 4.0, so attribute Open-Meteo.com if you publish results. The server software is AGPL-3.0.
No. No official partnership or endorsement between xCloud and the Open-Meteo project has been verified. This is a deployment and server-management option for the open-source Open-Meteo project.
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 credit card required, and no plan you have to grow into.