Cloud VPS 6 GB
Most popularA clip-sharing app for one Jellyfin household or group.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Jelly-Clipper hosting and run a self-hosted Jellyfin clip tool that lets your Jellyfin users cut, save and share short clips from the library. xCloud starts the pinned image with an embedded SQLite database, two persistent volumes and HTTPS on your domain. It needs an existing Jellyfin server this server can reach, and nobody has a separate account: sign-in is checked against Jellyfin. Open the setup page straight away to bind it to yours.
Jelly-Clipper is an open-source web app, released under the MIT licence, that lets Jellyfin users create, share and manage video clips from their media library. Upstream describes pasting a Jellyfin media link, choosing a start and end, and getting a shareable clip that only other users of the same Jellyfin instance can open. Its interface is inspired by YouTube and Twitch clips, and a self-hosted Jelly-Clipper is the clip counterpart to those services for a private library.
On xCloud the template runs the community ghcr.io/arnolicious/jelly-clipper 1.3.6 image, pinned by digest, as one container with SQLite and two volumes: jelly_clipper_db and jelly_clipper_videos. Jellyfin itself is not included. No media folder is mounted, so each source video is downloaded from Jellyfin before clipping, and downloaded originals are cleaned up after seven days by default.
Self-hosting Jelly-Clipper normally means a container, two volumes, a domain, a certificate and the right origin setting before anyone can sign in. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Jelly-Clipper from the OneClick catalog. Choose your domain and target server — there are no extra fields to fill in.
Step 02
One click. We bring up the community Jelly-Clipper image, pinned by immutable digest, as a single container with embedded SQLite, mount the jelly_clipper_db and jelly_clipper_videos volumes, set the site origin to your domain, and publish it over HTTPS.
Step 03
Open the Setup URL right after install, enter the address of your Jellyfin server and sign in with a Jellyfin account. Then pick a library item, choose the start and end points and create your first clip.
Jelly-Clipper runs in full here: a clip-sharing web app in front of your Jellyfin library, on your own domain, with clips stored on your own server.
Create clips from your favourite movies and shows in an existing Jellyfin library, choosing the start and end of the moment you want to keep.
Each clip gets a link you can copy and share, and a signed-in user can also download it as video or audio.
There are no Jelly-Clipper accounts: sign-in is checked against the Jellyfin server saved during setup, and clips are visible to signed-in users only.
Downloaded originals are deleted automatically after 7 days by default to save storage, while the clips themselves are kept.
The database and clips live on persistent named volumes, and both survived a container restart in QA.
A single container with embedded SQLite — measured idle use in QA was about 184 MiB, and about 260 MiB after creating a clip.
Managed hosting for Jelly-Clipper, so the parts that keep it online are not your problem.
Cut a short clip from a film or episode in your library and send a link to other members.
Limit viewing to people who can sign in to your own Jellyfin server instead of posting publicly.
Save clips to each person's profile, where others on the instance can browse them.
Let downloaded originals expire on a schedule while the clips you made remain.


Dedicated Cloud VPS sizes, pre-configured for Jelly-Clipper hosting. Pick the one that fits, and resize any time.
A clip-sharing app for one Jellyfin household or group.
$24.99per month
More headroom if Jelly-Clipper sits alongside other media 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. Jelly-Clipper itself is licensed by its maintainers under MIT.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Jelly-Clipper 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.
Jelly-Clipper 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 Jelly-Clipper Docker hosting the template runs the community ghcr.io/arnolicious/jelly-clipper 1.3.6 image, pinned by tag and digest, as one container on port 3000. It uses an embedded SQLite database with no separate service, and xCloud's nginx publishes it over HTTPS.
Jelly-Clipper is open source under the MIT licence, so the clip tool has no licence fee. Upstream calls it a first, somewhat hacky open-source project and invites fixes. xCloud charges for the dedicated Cloud VPS and the deployment work, while your Jellyfin server keeps its own hosting arrangement.
The manifest floor is 512 MB of RAM, one core and 5 GB of disk. Disk matters most, since each source video is downloaded from Jellyfin before clipping and saved clips are kept until you remove them. The 6 GB plan here leaves ample memory above that floor.
No. Jelly-Clipper does nothing on its own: it needs an existing Jellyfin server that this server can reach over the network. Enter that server's public address or IP during setup, because localhost would point at the Jelly-Clipper container itself rather than your media server.
Wait about thirty seconds, then open the Setup URL on your credentials panel straight away and enter your Jellyfin address and a Jellyfin login. Until setup finishes, anyone who reaches the site could bind it to a Jellyfin server of their choice. Afterwards, any Jellyfin user can sign in and see other users' clips.
Back up jelly_clipper_db (the Jellyfin address, users, sessions and clip records) and jelly_clipper_videos (saved clips and temporary originals) together while the container is stopped. The originals are deleted on a schedule, so the saved clips are what matter. Test a restore.
Release 1.3.6 stays put until you act, because the tag and digest are pinned and catalog changes only reach new installs. Snapshot both volumes, check the upstream notes, and then pick a later template version. Keep JELLY_CLIPPER_ORIGIN equal to your public HTTPS address, or sign-in and setup fail.
Downloaded originals are cleaned up after seven days by default, and the cleanup runs nightly in the time zone you set. Saved clips are kept until you remove them. You can change the schedule and age with the optional CLEANUP settings in the environment file.
Yes. Jelly-Clipper cloud use gives the app a dedicated Cloud VPS with your domain and certificate. The server must be able to reach your Jellyfin address over the network. Hosting elsewhere? You can connect that server as self-managed instead.
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.