Runtime and processes
Check Java services that need a defined JDK, heap budget, process supervision, ports, logs, database connectivity, and enough memory headroom for the chosen framework.
Java application hosting
Choose a VPS around your application's JVM, heap and database requirements. Leave room for the operating system and other services.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check Java services that need a defined JDK, heap budget, process supervision, ports, logs, database connectivity, and enough memory headroom for the chosen framework.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
A Java service uses more memory than its heap: metaspace, thread stacks, direct buffers, and JIT code all live outside the heap figure. Set the maximum heap explicitly with -Xmx to a size that leaves real headroom for the operating system and these off heap areas, or the kernel will kill the process under pressure.
Garbage collection behaviour decides how the service feels under load. Long pauses usually trace to a heap sized far from the live data set, so measure the steady state heap after a full collection and size the young and old generations around that measurement, then watch pause times in the GC log during peak traffic.
Confirm the JVM version reads container or cgroup memory limits correctly, or set heap values explicitly. Older JVMs sized the heap from the host machine's memory.
Enable GC logging and check pause distribution during your busiest hour. Frequent full collections mean the heap or the allocation rate needs attention.
Multiply the thread count by the stack size setting and include the result in your memory plan. Hundreds of threads can consume gigabytes outside the heap.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.