What this covers
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, obtain and renew the TLS certificate, take the backups and watch it. You deploy your application onto it, and you keep root.
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.
How to do it
- Open Services in the portal and choose Managed Java VM, or go straight to the sizing form.
- Pick a size. Small is 2 vCPU and 4 GB, Standard is 4 vCPU and 8 GB, Large is 8 vCPU and 16 GB.
- Enter your repository URL, branch, and the path your build writes the jar to.
- Pick your JDK version — 21 or 17. Both are long-term-support releases.
- Add a start command only if yours differs from java -jar <your artefact>.
- Enter the domain the app will serve on, so we can issue its certificate.
- Submit. Your sizing is saved as a numbered request you can refer to.
What our team checks
We read every sizing before the machine 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.
Next step
Open the sizing form and fill in what you know. If you are unsure which size to pick, describe your application in the notes field and we will advise before building.