What Java teams usually need
JVM apps can run well in containers, but they need enough headroom and stable runtime behavior. This page is for teams that prefer simple deployment over hand-managing VPS routines.
- Always-on runtime option for services that should stay warm
- Predictable monthly pricing instead of request-based billing
- Straightforward Git and CI deployment workflow
- Managed PostgreSQL or MariaDB in the same resource pool
First win path
- Start the trial and get a live app endpoint.
- Push one code change to your trial repo.
- Watch the deployment workflow in Gitea Actions.
- Refresh your URL and confirm your update is live.
Goal: first live update in roughly 15 minutes.
Plan fit for Java workloads
Starter (S$5/mo)
0.5 vCPU, 512MB RAM, 4GB storage
Good for lightweight or experimental services. For JVM workloads, this is usually for narrow workloads or non-production experimentation.
Pro (S$15/mo)
2 vCPU, 2GB RAM, 16GB storage
Recommended for always-on Java services, worker processes, and app+database setups that need more stable runtime headroom.
If your Java service and PostgreSQL run together, plan for Pro or equivalent capacity.