JavaFolk
Java hosting. Nothing else.

Hosting run by the folks who actually read your stack traces.

JavaFolk runs servlets, EJBs, and Jakarta EE apps on isolated JVM containers, tuned by a small crew of people who have shipped Java in production for a living. No shared PHP box pretending to run Tomcat, no support queue that starts with "have you tried restarting it."

See the plans Support: 24/7 · ~30 min avg response
7
runtimes supported
Java 8-25
LTS builds
99.95%
uptime SLA
 deploy-log.txt
0%
Uptime SLA, credited automatically
0
Servlet & app server runtimes
0
Avg. priority support response
0%
Java. No shared PHP boxes, ever
Why Java only

We picked a lane and stayed in it.

General hosts treat Java as an afterthought bolted onto a PHP stack. JavaFolk was built around the JVM from line one, so the defaults are actually right for your app.

Real JVM containers, not shared PHP boxes

Every account gets its own container with dedicated heap, GC settings you can actually tune, and no noisy neighbor stealing your CPU cycles at 3am.

Deploys that finish in under a minute

Push a WAR, EAR, or JAR and watch the log. No mystery build queue.

Every LTS build, current and old

Java 8 through 25, so the legacy WebLogic app and the new Spring Boot service both fit.

Backups that restore, not just exist

Automated snapshots, tested restores, and a real recovery runbook, not a cron job nobody has verified.

Support tickets answered by engineers

Not a tier-one script reader. Whoever picks up your ticket can read a thread dump.

Runtimes

Pick your runtime, we already run it.

Tomcat 9 / 10 / 11Stable, most popular
Jetty 11 / 12Lightweight, embeddable
TomEE 9 / 10MicroProfile ready
GlassFish 7Full Jakarta EE 10
WildFly 30+Clustering built in
Payara Server / MicroMicroProfile + cloud native
Spring Boot (embedded)Executable JAR deploys
QuarkusFast boot, low memory
MicronautReflection-free DI

See every supported runtime →

Under the hood

The infrastructure ledger.

No hand-waving about "the cloud." Here's what's actually running under your app.

ComputeDedicated vCPU cores, NVMe local storage
JVMOpenJDK / Temurin builds, per-container heap tuning
NetworkingFree TLS, DDoS-filtered edge, dedicated IP on request
DataManaged PostgreSQL, MySQL, and Redis add-ons
MonitoringJMX metrics, GC logs, and heap dumps on demand
BackupsNightly snapshots, 14-day retention, tested restores
Features

Built for people who ship Java, not just talk about it.

One-click WAR/EAR deploys

Drag, drop, done. Or push straight from your CI pipeline.

Horizontal & vertical scaling

Add containers or resize the ones you have, no re-architecture required.

Full JMX & thread-dump access

Real diagnostics, not a dashboard that only shows CPU percentage. Pull heap and thread dumps whenever you need them.

Staging that mirrors production

Same runtime, same JVM flags, so "works on staging" actually means something.

See the full feature list →

Plans

Straightforward pricing, no surprise line items.

Sprout

$8/mo

One small app, tinkering and side projects.

  • 1 JVM container, 1 GB heap
  • Tomcat, Jetty, or TomEE
  • Free TLS & nightly backups
Get started
Popular

Homestead

$26/mo

A real production app with room to grow.

  • 1 JVM container, 4 GB heap
  • Any servlet container or app server
  • Priority support queue
Get started

Gathering

$72/mo

Clustered, dedicated, ready for real traffic.

  • 3 clustered JVM containers
  • Dedicated IP included
  • 24/7 live-chat support
Get started

Guild

Custom

Multi-app fleets, compliance needs, dedicated hardware.

  • Custom container sizing
  • Dedicated account engineer
  • Custom SLA & onboarding
Talk to sales

Compare every plan in detail →

FAQ

Questions folks actually ask.

Yes. Every plan gives you a configuration panel for heap size, GC algorithm, and common JVM flags. Homestead and above can request custom flags through support.
We don't host WebLogic or WebSphere directly, but our migration guides on the Runtimes page walk through moving those workloads to WildFly or Payara with minimal code changes.
Yes. Send us your WAR/EAR and current runtime and we'll help size a plan and handle the cutover, usually with a maintenance window under an hour.
We'll flag it before it becomes an outage and suggest the next plan up. We don't silently throttle or suspend without warning you first.

Ready to hand your JVM to people who get it?

Spin up a container in minutes. Support's available 24/7, with an average response time of about 30 minutes.

See the plans