Features
Maven & Gradle
We detect pom.xml or build.gradle, download dependencies, and build a production JAR automatically.
Java 17 & 21 LTS
Run on the latest LTS JVMs (Eclipse Temurin) with tuned GC settings. Kotlin fully supported alongside Java.
Git Push Deploy
Push to your repo and we build, test, package, and deploy your Spring Boot app with zero downtime.
Managed Databases
Add PostgreSQL, MySQL, or Redis with one click. Spring datasource properties set automatically.
How it works
- 01Run dock deployRun
dock deployin your project folder, or connect a GitHub repository. - 02We build itWe detect Spring Boot from
pom.xml · build.gradle, install dependencies and build an image. - 03It goes liveYour app gets a container, free SSL and a live https://….dockhosting.cloud URL.
$ dock deploy→ Detecting framework… Spring Boot→ Found pom.xml · build.gradle→ Maven / Gradle build → executable JAR→ Building image→ Provisioning container + SSL✓ Live at https://my-app.dockhosting.cloud
Supported
- Java 17
- Java 21
- Spring Boot 3
- Maven
- Gradle
- Kotlin
- PostgreSQL
- MySQL
- Redis
Specifications
- Java versions
- 17, 21 LTS (Eclipse Temurin)
- Build tools
- Maven 3.9+, Gradle 8.x
- Spring Boot
- 2.7.x, 3.x
- Kotlin
- Fully supported
- Max memory
- Up to 4 GB per app
- Custom domains
- 3 on Pro, 10 on Team - auto SSL
Overview
Updated 1 November 2026
Spring Boot apps carry more moving parts than a typical script: a build tool that resolves dependencies, a JVM that wants tuned memory settings, and usually a database, a cache, and a scheduler talking to each other. DockHosting reads pom.xml or build.gradle, runs your Maven or Gradle build, and ships the executable JAR - no hand-written Dockerfile, no Tomcat to install, no server to patch.
Configuration lands where Spring expects it. Attach a managed PostgreSQL or MySQL database and the connection properties are injected as environment variables; add Redis and Spring Cache or sessions work over the private network without exposing anything publicly. Scheduler tasks, Quartz jobs, and background workers run alongside the web server the same way queue workers do on other stacks.
Compared with a traditional VPS, you skip the whole provisioning ritual - installing a JDK, setting up a process supervisor, wiring TLS, and writing deployment scripts. Compared with shared hosting, you get a real JVM process with up to 4 GB of memory instead of a PHP-only plan that cannot run a Java app at all. The Free plan is enough to run a small Spring Boot service with one database; Hobby ($4/mo) keeps it always-on with your own domain.
Compare
Spring Boot ships a fat JAR with Tomcat embedded - no server install needed, but someone still has to run it. A VPS means maintaining JVMs and process supervisors yourself. DockHosting builds the JAR with your build tool and runs it on a managed JVM runtime.
| Feature | DockHosting | Tomcat on a self-managed VPS |
|---|---|---|
| Build | Maven/Gradle detected, executable JAR built on deploy | Build locally or script CI, then deploy the artifact |
| Runtime | Managed container on Java 17/21 LTS, restart on crash | Your JVM, systemd units and monitoring |
| Java version | LTS picked from pom.xml/build.gradle | Whatever is installed on the server |
| HTTPS | Automatic Let's Encrypt | Manual or paid certificates |
| Database | Managed PostgreSQL/MySQL/Redis, credentials injected as spring.datasource vars | Install and back up your own stack |
| Cost | Flat $0 / $4 / $9 / $19 | VPS + the hours to operate a Java server |
The bottom lineSpring Boot was built to be deployed as a JAR; DockHosting just automates the boring part of running it - no Tomcat, no JDK setup, no deploy scripts.
Everything you need to know before you deploy your first Spring Boot app.
Yes - the Free plan covers a Spring Boot app with Maven/Gradle builds, auto SSL, and a managed database. No credit card required.
