Servers
Cloud Servers Cloud VPS Dedicated VPS Windows VPS Windows Dedicated VPS Managed Cloud Servers Managed Cloud Dedicated Servers GPU Dedicated Servers Forex VPS Forex Dedicated Server
Hosting
cPanel Hosting WordPress Hosting WooCommerce Hosting cPanel Dedicated cPanel Reseller Nextcloud Hosting Sovereign Workspaces
Platform & Containers
Platform as a Service PaaS Marketplace Red Hat OpenShift Docker Hosting Kubernetes n8n Hosting Dokploy Hosting Coolify Hosting Magento in PaaS WordPress in PaaS
Private Cloud
Private Cloud Hosting Virtual Private Cloud Dedicated Private Cloud HA Private Cloud White-Label Cloud Platform Colocation
Solutions
eCommerce Hosting Fintech Hosting Gaming Hosting Disaster Recovery Digital & Data Sovereignty VMware Replacement Sovereign Government Suite National Digital Identity For Developers For Enterprises AI Infrastructure Blockchain Hosting
Cyber Security
Security Overview DDoS Protection SSL Certificates HSM Decanus Terminal Backup Services Domains SOC Services Aramco CCC SABIC CyberTrust SAMA CSF NCA CCC NCA CSCC CITC CRF Saudi PDPL Qatar Cybersecurity UAE Cybersecurity GCC Cybersecurity CMMC NIS2 DORA TISAX HIPAA
Support
Support Plans DevOps Support Nextcloud Support Proxmox Support VMware Replacement NOC Services
Resources
Technology Data Centers Network High Availability Storage Blog Forex VPS Guides Windows VPS Guides Dokploy Guides Coolify Guides About Us Compare Contact
Browse All Industries →
Login Get Started
Clusters & Containers Application

Tomcat/TomEE Cluster Hosting on MassiveGRID PaaS

The Tomcat/TomEE Cluster with High Availability deploys several Apache Tomcat or TomEE nodes with HTTP session replication behind an NGINX load balancer on MassiveGRID PaaS. Java web applications gain failover and horizontal scaling without code changes, and nodes are added automatically under load.

Tomcat/TomEE Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $44.28 a month for the Starter configuration, a NGINX load balancer (256 MiB) and 2 × Application node (1 GiB each), and starts with a 14-day free trial. See the sizing table.

Both buttons open the MassiveGRID PaaS dashboard with Tomcat/TomEE Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.

4
Regions
100%
Uptime SLA
14 days
Free trial

Tomcat/TomEE Cluster Package Facts

AttributeValue
PackageTomcat/TomEE cluster with High Availability
TypeApplication (installs a complete environment)
CategoryClusters & Containers
Software vendor / projectApache Software Foundation
LicenceApache License 2.0 (open source)
Runtime / stackApache Tomcat or TomEE nodes with session replication behind an NGINX load balancer
RegionsNew York, London, Frankfurt, Singapore
BillingPay-per-use, about $44.28/month for the Starter configuration (18 cloudlets at $0.003372 per cloudlet-hour), no licence fee
Free trial14 days, no credit card
Uptime SLA100%

What is Tomcat/TomEE Cluster?

Apache Tomcat is the most widely used Java servlet container, and TomEE is Tomcat extended into a certified Jakarta EE web-profile server. Both run the vast majority of Java web applications, including Spring MVC and Spring Boot WARs. Clustering them means putting a load balancer in front of several instances and replicating sessions so a user is not logged out when a node fails or is removed.

The package configures Tomcat's cluster membership and session replication, deploys the NGINX balancer with sticky sessions and health checks, and enables horizontal auto-scaling. New nodes join the cluster and the balancer automatically. You deploy the same WAR to every node from the dashboard or through Git.

What the Tomcat/TomEE Cluster Package Deploys

Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.

  • Tomcat or TomEE nodes: Two or more Java application server containers with clustering and session replication enabled, your choice of Tomcat or TomEE.
  • NGINX load balancer: A balancer distributing requests with sticky sessions and health checks, terminating SSL.
  • Auto-scaling triggers: Rules that add and remove application nodes on CPU or memory load and update the balancer.
  • Synchronised deployment: Applications deployed via the dashboard or Git are pushed to every node in the cluster.

What Tomcat/TomEE Cluster Costs to Run

Three starting configurations for the Tomcat/TomEE Cluster package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month.

ConfigurationTopologyCloudletsEst. per month
StarterDevelopment NGINX load balancer (2 cloudlets, 256 MiB), 2 × Application node (8 cloudlets, 1 GiB each) 18 $44.28
StandardProduction NGINX load balancer (4 cloudlets, 512 MiB), 2 × Application node (16 cloudlets, 2 GiB each) 36 $88.56
ProductionHigh traffic NGINX load balancer (4 cloudlets, 512 MiB), 4 × Application node (16 cloudlets, 2 GiB each) 68 $167.28

Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.

Why Teams Choose Tomcat/TomEE Cluster

Session failover

Replicated sessions keep users logged in when a node fails or is scaled away.

Zero-code scaling

Existing WAR files run unchanged; the cluster handles distribution.

Tomcat or TomEE

Choose plain Tomcat for servlet and Spring applications or TomEE for Jakarta EE web profile features.

Lightweight

Tomcat nodes start in seconds and run well on small cloudlet allocations, keeping the cluster economical.

How to Install Tomcat/TomEE Cluster on MassiveGRID PaaS

Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.

The Tomcat/TomEE Cluster installer dialog in the MassiveGRID PaaS dashboard, with the environment name, display name and region fields above the Install button
What the Install button opens: the Tomcat/TomEE Cluster installer. Keep or change the environment name, pick a region, and click Install. Screenshot of the MassiveGRID PaaS dashboard, 2 November 2026.
01

Open the installer

Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Tomcat/TomEE Cluster package pre-selected, so nothing has to be copied or pasted.

02

Sign up or sign in

New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.

03

Choose region and deploy

Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Tomcat/TomEE Cluster node, wires them together and hands you the live URL and credentials.

Who Runs Tomcat/TomEE Cluster on PaaS

Spring and servlet applications

Java web apps packaged as WARs that need high availability.

Customer-facing portals

Applications with login sessions that must survive node failures.

Replacing single-server Tomcat

Teams whose one Tomcat box has become a risk or a bottleneck.

Why Run Tomcat/TomEE Cluster on MassiveGRID PaaS

Built for uptime. Tomcat/TomEE Cluster runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.

Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Tomcat/TomEE Cluster environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.

Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 27001 and ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.

No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.

Related on massivegrid.com: Platform as a Service.

Tomcat/TomEE Cluster Questions

Tomcat's built-in clustering replicates HTTP sessions between nodes over the environment's internal network. Sticky sessions on the balancer keep users on one node normally; replication makes failover seamless.
Yes, as WAR files to Tomcat. For executable JARs, see the Spring Boot Cluster package which runs them on Java Engine nodes.
Current stable Tomcat or TomEE releases with a matching LTS JDK. Both can be changed from the dashboard to match your application's requirements.
About $44.28 a month for the Starter configuration (18 cloudlets: a NGINX load balancer (256 MiB) and 2 × Application node (1 GiB each)), $88.56 for Standard and $167.28 for Production, at the published rate of $0.003372 per cloudlet-hour ($2.46 per cloudlet-month), before volume discounts. Disk and external traffic are billed per gigabyte on top. There is no licence fee for the package, and vertical auto-scaling means a quiet environment uses fewer cloudlets than the table assumes. The sizing table above shows each configuration.
Updates follow the project's own procedure. You have root access to every container over SSH or the dashboard's web terminal, and a container can be redeployed to a newer image tag with its data volumes kept. Clone the environment first and rehearse the upgrade on the copy, which is billed only for the hours it exists, then repeat the steps on production.
Backups are add-ons you attach from the same marketplace: the Database Backup/Restore add-on dumps MySQL, MariaDB, Percona or PostgreSQL on a schedule, the Backup Storage package holds the archives on a separate node, and restores are a dashboard action. Environment cloning gives you a full copy for upgrades and testing. Schedule, retention and off-platform copies are yours to set.
Yes. Every environment gets a platform subdomain with a valid certificate from the first minute. Point your own domain at the environment (a CNAME, or an A record to a public IP you attach), then install the Let's Encrypt SSL add-on, which issues the certificate and renews it automatically.
Yes. New accounts get a 14-day free trial with no credit card required. Click Install with free trial above, sign up, and the installer opens with Tomcat/TomEE Cluster already selected. Trial environments can be scaled, tested and deleted freely, and they convert to pay-per-use billing only when you add a payment method.

Packages that are often deployed alongside Tomcat/TomEE Cluster, or that solve the same problem a different way. Browse all 83 packages.

Deploy Tomcat/TomEE Cluster Today

Start the free 14-day trial and have Tomcat/TomEE Cluster running in minutes. No credit card required.

One-Click Install
14-Day Free Trial
Pay-Per-Use
100% Uptime SLA
Install Tomcat/TomEE Cluster Free