LanguageGB
Managed Java — a machine of its own

A machine for your Spring Boot app, built and operated for you.

Tell us the size, the JDK, the repository and the artifact path. We build the VM, install and maintain the toolchain, renew the TLS, take the backups and watch it — you deploy the application and you own it.

orders-api.yourdomain.com
Managed Java VMorders-api.yourdomain.com

JDK 21 + Maven/Gradle + TLS

Business website
SSLReady
BackupsReady
JV
IncludedNot sure what size? Send your current heap settings and traffic and we will tell you.

In practice

Java needs a machine, not a share of one.

Our shared runtime gives every app a fair share rather than a hard cap, which suits Node and Python because they degrade under pressure. A JVM does not: it reads the machine, sizes its heap, and a build spikes on top. So Java gets a machine of its own — and since we are operating it anyway, we keep the toolchain, the certificates and the backups working too.

Spring Boot API

A production API with its own heap, its own build, and a health endpoint that is checked rather than assumed.

Batch and scheduled work

Jobs that need memory in bursts without starving anything else on the box.

An app you already run

Tell us the JDK and build tool you use; the machine arrives ready for them.

A move off shared hosting

An app that keeps hitting limits because its memory profile never fitted a shared runtime.

Why CM Cloud

Built to do more.

Sized to your app, not a shared pool

A JVM sizes its heap from what it believes the machine has, and a build is a memory spike by nature. Both make Java a poor tenant on a shared runtime and a good fit for a machine of its own, with a memory ceiling that is real rather than a fair share.

A toolchain we keep working

Maven or Gradle and the JDK you pinned, installed and kept current across security updates, so a patch is not a weekend of yours.

TLS, backups and monitoring included

Certificate renewal, nightly backups into offsite storage with the retention you choose, and the same monitoring that watches the rest of the platform.

A support boundary written down

We own the VM, its toolchain and the platform services. You own the application, deploying it, and your JVM tuning inside it. That line is on the order form, not discovered during an incident.

Who it's for

Managed Java VM is the right fit if you need:

✓Spring Boot, Quarkus or Micronaut services that need a real heap
✓Teams who want a managed machine without managing the machine
✓Apps whose memory profile makes them a bad neighbour on shared hosting
✓Anyone who wants a machine and a support boundary rather than an abstraction
✓Java shops with their own CI opinions who still want the box managed

How it works

Up and running in three steps.

1Fill in the sizing form — size, JDK, build tool, repository, artifact path
2We confirm the sizing and build the VM
3You deploy your app onto the machine; we watch the health endpoint you nominate
4You get SSH details and the machine's status in your dashboard

Included, not an add-on

Protected against attacks from the first day

Automated attacks sweep the web constantly, looking for any site running common software. Yours is watched for them around the clock — and every part of this is in your plan already, at no additional cost.

✓Password-guessing and abusive automated traffic are detected and blocked before they reach your site.
✓An attacker stopped at one site is blocked across every site we host, at our firewall and at Cloudflare's global edge.
✓Daily encrypted off-site backups, free SSL, and account-level isolation so a neighbouring site can never affect yours.

Complete your setup

Works best alongside Managed Java VM.