Java hosting on a server that is only yours
A separate VPS for every customer, set up for Tomcat, Spring Boot, Quarkus, WildFly, Payara or Docker. Pick the memory your application needs, then we install it or run it for you.
How a server's memory is used by a Java application
- JVM heap
- 3.6 GB
- Database buffers
- 1.2 GB
- System and file cache
- 3.2 GB
- This server
- €45.05 4 vCPU, 80 GB NVMe, per month
The JVM heap is only part of what a Java process uses. How much RAM a Java app needs
Java needs its own memory, not a slice of a shared account
The JVM reserves its memory up front and keeps it. On shared hosting that is the first thing to go wrong. A VPS gives your application a guaranteed amount of RAM and the freedom to configure it.
- One server per customer
- No neighbours. Your RAM, CPU and disk are yours, so a busy site next door cannot slow your application down.
- Set up the way Java expects
- OpenJDK, your application server, Nginx with free SSL, firewall and automatic security updates, installed and tuned for the memory you chose.
- Any Java version, any framework
- Java 8 to 21 today. Run Tomcat, WildFly or Payara, a Spring Boot, Quarkus or Micronaut JAR, or your own Docker image.
- Your database next to your code
- MySQL, MariaDB or PostgreSQL on the same server, listening only locally, with a nightly dump.
- Deploy with one command
- Upload a WAR or JAR and run deploy-app. The previous version is kept, so a bad release is easy to undo.
- We can run it for you
- Choose Managed and we handle updates, backups, monitoring and JVM tuning. Switch to Self-managed any time you want root access back.
Pick the Java stack you run
Each runtime has its own page with versions, memory advice and how deployment works.
- Apache Tomcat
WAR and JSP applications, servlets, Spring MVC. The most common Java web server.
Tomcat 9, 10.1, 11 - Spring Boot
A runnable JAR as a systemd service behind Nginx. Update it with one command.
Java 17 and newer - Quarkus
Fast startup and low memory use. Run the JVM build, or a native executable you build in CI.
Java 17 and newer - Micronaut
Small footprint microservices, with no runtime reflection.
Java 17 and newer - WildFly
A full Jakarta EE application server with EJB, JMS and CDI.
Jakarta EE 10 and 11 - Payara Server
Jakarta EE 11 with the GlassFish heritage. The upgrade path for GlassFish applications.
Payara 6 and 7 - Docker
Bring any container image. It runs with Docker Compose behind Nginx.
Any Java version - JSP and servlets
Classic server-rendered Java pages on Tomcat.
Servlet 4 to 6 - JSF
Faces applications on WildFly, Payara or Tomcat with MyFaces.
Faces 3 and 4
From payment to a running application
The same four steps for every runtime.
- Pick a sizeChoose memory for your JVM heap and decide between Self-managed and Managed.
- Subscribe with PayPalTell us which stack and database you run. The first payment starts a monthly subscription.
- We build your serverWe install Java, your application server, Nginx and SSL, then email you the access details.
- Deploy and go liveUpload your WAR or JAR, point your domain at the server and run deploy-app.
Why a VPS and not shared Java hosting
Shared Java hosting puts many customers on one JVM or one machine. A VPS gives you the whole machine.
| Shared Java hosting | Java VPS from Super Java Host | |
|---|---|---|
| Memory | Capped, shared with other accounts | Dedicated. 2 GB to 64 GB, all yours |
| Java version and flags | The version the host offers | Any. You set -Xmx, GC and system properties |
| Application server | A fixed Tomcat or a control panel | Tomcat, WildFly, Payara, Spring Boot, Docker |
| Other services | Usually none | Database, cron, queues, Redis, anything that fits in RAM |
| Isolation | Neighbours can affect you | Separate server per customer |
Self-managed or Managed
Same server, different amount of work for you. Managed starts at €30.30 a month.
| Self-managed | Managed | |
|---|---|---|
| Root access | Yes, full control | Yes, we only use it for maintenance |
| Server setup | Done for you, once | Done for you, once |
| OS, JDK and server updates | You apply them (security updates run automatically) | We apply them |
| Backups | Local database dump nightly | Offsite, 7 daily, 4 weekly and 6 monthly copies |
| Monitoring | You | We watch uptime, memory, CPU and disk, and alert |
| JVM tuning | You | We tune heap and garbage collection for your application |
| Migration help | Email support for setup | We migrate one existing application |
Questions
What does Java VPS hosting mean?
It means a virtual private server set up for Java: your own operating system, a JDK, an application server such as Tomcat or Spring Boot, and a reverse proxy with SSL. Nothing is shared with other customers.
Which Java application servers can I run?
Apache Tomcat, WildFly, Payara, Spring Boot, Quarkus and Micronaut JARs, and any Docker image. Tell us what you run when you subscribe.
How much memory do I need?
As a rule, give the JVM heap about 45% of the server RAM when a database runs on the same server and about 60% when it does not. A small Spring Boot API runs in 2 GB. A production application with a database is comfortable on 8 GB.
How is it billed?
Monthly through PayPal. You subscribe once and PayPal charges you every month until you cancel in your PayPal account.
Do you offer a free trial?
No. Servers are real, dedicated resources, so we do not run free trials. The Refund Policy covers the first payment.
Start with a server of your own
Billed monthly through PayPal. Cancel any time.