Order a managed Java VM

What this means

What this means

You get a machine of your own — not a share of a pool — running your Java application. We build the VM, install and maintain the JDK, run the build-and-deploy pipeline, obtain and renew the TLS certificate, take the backups and watch it. You keep root on it.

Before you start

Before you start

Have your repository URL and branch ready, know whether you build with Maven or Gradle, and know the path the build writes your jar to (for Maven that is usually target/your-app.jar). If your app does not expose a health endpoint, decide what URL we should poll — Spring Boot ships /actuator/health.

Step-by-step guidance

Step-by-step guidance

1. Open Services in the portal and choose Managed Java VM, or go straight to the sizing form.
2. Pick a size. Small is 2 vCPU and 4 GB, Standard is 4 vCPU and 8 GB, Large is 8 vCPU and 16 GB.
3. Enter your repository URL, branch, and the path your build writes the jar to.
4. Pick your JDK version — 21 or 17. Both are long-term-support releases.
5. Add a start command only if yours differs from java -jar <your artefact>.
6. Enter the domain the app will serve on, so we can issue its certificate.
7. Submit. Your sizing is saved as a numbered request you can refer to.

What CM Cloud support will review

What CM Cloud support will review

We read every sizing before anything is built. Support will confirm the JDK, build tool and artefact path make sense together, and will come back to you if the size looks wrong for what you have described rather than building something that will not cope.

What is not automated yet

What is not automated yet

Submitting the form does not build the machine on the spot. Demand for these is higher than the capacity we have online, so an order may be queued — if yours is, the form tells you so, nothing is charged, and support contacts you. Nothing about your application is guessed: if the artefact path or the start command is wrong, the build stops rather than serving something broken.