Cloud VPS 6 GB
Most popularAn image resizing endpoint for one site or a small set of projects.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Next Image Transformation hosting on xCloud gives you a self-hosted image optimization API on your own domain. Deploy Next Image Transformation and xCloud runs the pinned official image beside a private imgproxy, asks you for the source hostnames it may fetch, publishes the API over HTTPS, and keeps no data at all. Request an image with width, height and quality parameters and get a resized AVIF or WebP back. There is no login, so keep the allowlist narrow.
Self-hosted Next Image Transformation is an open-source, self-hostable image optimization service, described upstream as a drop-in replacement for Vercel's Image Optimization. A small Bun API accepts Next.js-style image requests, turns them into imgproxy requests and forwards them to an imgproxy service that resizes, crops and re-encodes remote images on the fly, using width, height and quality parameters. It is Apache-2.0 licensed, and the project also runs a cloud version.
On xCloud the template runs ghcr.io/coollabsio/next-image-transformation 0.0.3 and imgproxy v3.31.4, both pinned by digest. You enter the hostnames the API may fetch at install, and that list is the only access control. The stack is stateless, with no volume, and always asks imgproxy for AVIF or WebP, so a JPEG source comes back in a newer format.
Self-hosting an image resizing API normally means pulling two images, wiring them together on a private network, locking down which hosts can be fetched, and adding a domain and a certificate. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Next Image Transformation from the OneClick catalog. Choose your domain and target server, then enter the allowed source hostnames, for example example.com,cdn.example.com.
Step 02
One click. We bring up the official Next Image Transformation image and a private imgproxy container, both pinned by immutable digest, keep imgproxy off the public network, and publish the API on port 3000 over HTTPS on your domain. There is no volume: configuration lives in the environment.
Step 03
Open your HTTPS URL to see the service banner, then request /image/ followed by a source image URL on an allowed host with width, height and quality parameters. Check the response Content-Type and size before pointing your Next.js custom loader at it.
Next Image Transformation runs in full here: one URL route that fetches, resizes and re-encodes images, with the hostname allowlist you control.
Set width, height and quality as query parameters on a Next.js-style /image/ route and get the resized image back from the same URL.
JPEG sources come back as AVIF, or WebP when AVIF is unavailable, regardless of the client Accept header. In QA a 128 KB JPEG returned as a roughly 14 KB AVIF at width 300.
Transformations run in imgproxy v3.31.4, the open-source edition rather than Pro, on a private network next to the API with no host port of its own.
Only the source hostnames you list in ALLOWED_REMOTE_DOMAINS are fetched. In verification, other hosts, look-alike hostnames, localhost, cloud metadata addresses and file URLs were refused with 403.
An unauthenticated /health route is available for uptime monitoring, and the root URL shows a service banner.
Both containers used about 34 MiB while idle on QA, and with no volumes there is nothing to lose on a restart.
Managed hosting for Next Image Transformation, so the parts that keep it online are not your problem.
Point a custom image loader at the image route so pages request resized AVIF or WebP versions instead of the originals.
Allow your own CDN or media hostname and let the API produce the sizes your layouts need on request.
Any client that can call a URL can use the same resize and quality parameters, with no image library to install.
Run the transformation on a Cloud VPS you control, with a narrow allowlist deciding exactly which sources can be fetched.
Dedicated Cloud VPS sizes, pre-configured for Next Image Transformation hosting. Pick the one that fits, and resize any time.
An image resizing endpoint for one site or a small set of projects.
$24.99per month
More headroom for large images or many concurrent transforms.
$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. Next Image Transformation itself is licensed by its maintainers under Apache-2.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Next Image Transformation 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.
Next Image Transformation 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. Next Image Transformation is licensed Apache-2.0 on its main branch, though the 0.0.3 tag carries no licence file. The software has no licence fee, and imgproxy is a separate project. You pay xCloud for the dedicated Cloud VPS that runs both.
Yes, and this template is Next Image Transformation Docker hosting without the assembly. It starts the 0.0.3 API image beside imgproxy v3.31.4, both pinned by digest, proxies the API on port 3000 behind HTTPS, and keeps imgproxy private. It has no volumes.
The manifest asks for 256 MB of RAM, one CPU core and 2 GB of disk. This page sells the 6 GB Cloud VPS for a Next Image Transformation cloud install, which is mostly headroom. Large source images and many concurrent resizes are what use memory.
Set a custom image loader in your Next.js config and point it at your domain's image route, passing the source URL with width, height and quality query names. Upstream's README shows the loader file. Omit height to keep the source aspect ratio.
There is no login, so the allowed source hostnames list is the only access control. Disallowed hosts get a 403. Keep the list narrow, such as your own CDN, and avoid the wildcard that permits every host unless you really intend to proxy images from anywhere.
The API ignores the client Accept header and always asks imgproxy for AVIF, WebP or any format, so a JPEG source comes back as AVIF, or WebP when AVIF is unavailable. Check the response content type and dimensions before you rely on a given format.
No. The stack is stateless: source images and transformed bodies are request-scoped, and there is no volume. Keep your originals in your own storage. A malformed image URL makes the app return an error, which is normal.
There is nothing to back up. The template has no data volume, so only the environment settings, including your allowed hostnames, need keeping. Keep originals in your own storage. A server-level snapshot covers the rest of the machine.
Your install stays on its pinned 0.0.3 version until you adopt a newer template version. Do not move imgproxy to a new major version, because the API builds URLs for v3. Read the upstream release notes, then request a test image and check the format.
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.