Executable JAR deployments
Deploy a Spring Boot, Quarkus, Micronaut or plain executable JAR from GitHub or a ZIP/RAR archive.
Deploy your Java JAR with memory sized for the JVM.
Host Spring Boot, Quarkus, Micronaut or a plain executable Java JAR from GitHub or ZIP/RAR. Select the Java runtime, allocate RAM for the JVM and application, then use logs and metrics to tune it.
Build once, then run with JVM headroom
Java
select the Java version in the live runtime catalog
Optimized JVM
optimized JVM
1,536 MB
1,536 MB starting allocation for Spring Boot
Live
application logs and resource metrics
Java workload examples
From Spring Boot APIs to custom JVM processes.
The Java runtime runs executable JARs. Package the application first, give the JVM enough headroom, and use the same deployment flow for web services and background processes.
Explore capabilitiesSpring Boot APIs
Deploy a Spring Boot executable JAR for REST APIs, webhooks or internal services. Start with 1,536 MB, then use observed memory to choose the right plan.
Quarkus and Micronaut services
Package your Quarkus or Micronaut application as an executable JAR and configure its runtime version, memory, environment variables and public web access when it serves HTTP.
Plain java -jar processes
Run a CLI-style worker, scheduled process or another executable JAR with its own entry point and JVM flags. Follow startup output and resource metrics from the dashboard.
Prepare, configure and operate
Java hosting that accounts for JVM memory.
The plan cards below show the current RAM and vCPU allocations. Size the full container allocation for heap, metaspace, threads and native memory.
JVM-aware memory planning
Choose a compatible Java version and size the full container allocation for the JVM and your application.
JARs and application state
Each Java application has a 10 GB persistent disk at /app. Files written there survive application restarts, including generated files and state your Java process needs to retain.
Publish an HTTP service
Every Java application receives a free HTTPS address under *.shardweb.app. Connect a custom domain with the Core plan or higher when Spring Boot, Quarkus or Micronaut serves web traffic.
Use logs and resource metrics
Application logs expose JVM startup and runtime errors. Review RAM and CPU metrics under real traffic before moving to a larger plan.
Automatic restart
Java applications support auto-restart. Manage the process from the dashboard and use logs to investigate configuration or memory failures that cause it to stop.
Deployment setup
How to deploy a Java application on Shard Cloud.
Package an executable JAR, set the Java runtime and memory configuration, then verify the process under its real workload.
Get started01
Prepare your JAR
Package the app with Main-Class set in MANIFEST.MF, and add a .shardcloud file next to it.
02
Configure memory for the JVM
Set MAIN to the JAR and leave headroom beyond the heap. The docs start Spring Boot at 1,536 MB.
03
Check logs and RAM
Read the JVM startup logs, then watch RAM under real traffic before settling on a plan.
From connection to the first decision, in one flow.
Tutorials
Tutorials for your runtime
Open step-by-step Shard Cloud documentation for popular projects in this runtime.
How to Host a Lavalink Server
Create and host a Lavalink music server on Shard Cloud.
Read tutorialFrequently asked questions
Frequently asked questions about Java hosting
Deploy an executable JAR with a main class. Build the artifact locally or in CI, then use the Java deployment guide for the current project configuration.
Set VERSION=LATEST for the newest supported Java release, or VERSION=recommended for the platform's recommended release. Choose the setting compatible with your bytecode and dependencies.
Set MAIN to your executable JAR in .shardcloud, for example MAIN=spring-app.jar. The JAR must define Main-Class in its MANIFEST.MF. A web service must listen on port 80.
Every app needs at least 256 MB. Use 512 MB or more for a public website or API, then increase it based on observed usage.
Yes—but only by using a virtual machine. Minecraft needs a persistent Java process and control over its game port, which the managed Java app flow does not provide. Size the VM's RAM and CPU for the player count and mod pack.
Your server must listen on port 80.
Read the full Java deployment guide
Ready to move forward
Deploy your Java service with room for the JVM.
Bring a Spring Boot, Quarkus, Micronaut or plain Java JAR. Compare the current plan RAM and vCPU allocations below before you deploy.
Guided setup with no commitment
Executable JAR ready
Confirm its main class, JDK compatibility and production configuration before upload.
Memory budget set
Allocate memory for both the JVM heap and its non-heap overhead, then verify the workload under real traffic.
Deploy your Java app
Connect GitHub or upload a ZIP/RAR, select Java and start the executable JAR.
A plan for every stage of your project
Rated 4.9/5 on Trustpilot · Trusted by 50,000+ developers
Basic plan
Perfect for freelancers or individuals who need to host applications and bots.
1-2GB RAM
1-2 vCPU
4-8 projects
5-10GB CDN
Core plan
For small teams and startups that need infrastructure for multiple projects.
4-8GB RAM
4-5 vCPU
16-32 projects
35-100GB CDN
Connect your own custom domain
Pro plan
Built for scaling companies with high project volume and advanced support.
12-24GB RAM
6-10 vCPU
48-96 projects
150-250GB CDN
Load balancers
Automatic backups