Apache TomEE
Jakarta EE server built on Tomcat, in four distributions. Our application servers ranking puts Apache TomEE at #5 of 14.
Paid placement exists here and is disclosed. Whatever the arrangement, the Apache TomEE link carries the same marker as all others (details).
Visit Apache TomEE See it in the application servers ranking
At a glance
| Headquarters | Not stated by the vendor |
|---|---|
| Free plan | No free tier on record |
| Deployment | Unclear from the vendor pages |
| Best for | Teams wanting CDI, EJB Lite and JPA on top of a familiar Tomcat base |
| API | Unknown from our sources |
| Pricing model | Archive downloads under the Apache Licence 2.0; the site lists no prices |
What is Apache TomEE?
Apache TomEE is a Jakarta EE application server built on Apache Tomcat, according to its home page. The project is governed by the Apache Software Foundation, and the licence in the page footer is the Apache License, Version 2.0. Downloads come as ZIP and TAR.GZ archives in four distributions called WebProfile, MicroProfile, Plus and Plume, and the comparison page advises that when in doubt you should choose Plume.
The current release line, 10.3.0, implements Jakarta EE 10 with MicroProfile 6.1, and the 11.0.0-M2 milestone implements Jakarta EE 11 with MicroProfile 7.1 but is marked as not for production. The download page says the project is developed and maintained by unpaid volunteers. The site lists no prices and offers downloads only.
Apache TomEE key features
- Four distributions. WebProfile, MicroProfile, Plus and Plume let a team choose how much of the platform to install. Archives for release 10.3.0 range from about 59 MiB for WebProfile to 81 MiB for Plume.
- Web Profile coverage. The Web Profile covers Servlets, JSP, JSF, JTA, JPA, CDI, Bean Validation and EJB Lite. Plus and Plume add JMS and JAX-WS, which matters for applications that use messaging or SOAP services.
- Built on Tomcat. TomEE 10.x is built on Tomcat 10.1.x and TomEE 9.x on Tomcat 10.0.x. A team that already knows Tomcat's layout will recognise the directory structure and configuration style.
- Named component implementations. The comparison page names Apache OpenWebBeans for CDI, Apache OpenEJB for EJB, Geronimo Transaction Manager for JTA, Apache BVal for Bean Validation and Apache CXF for web services. Knowing the parts helps when debugging.
- MicroProfile support. Release 10.3.0 carries MicroProfile 6.1 and the 11.0.0-M2 milestone carries 7.1. A MicroProfile distribution exists, so services written to that standard have a matching download.
- Verified downloads. Each download has a PGP signature and a SHA512 checksum, and the page tells users they must verify file integrity. A Project Source Release ZIP is also offered for those who build themselves.
- Documentation and examples. Documentation covers configuration, directory structure, testing and clustering, with examples for CDI interceptors, REST with CDI, EJB and JSF with managed beans. The pages read do not show a tutorial for first-time setup.
Who Apache TomEE suits
- A Tomcat user who needs EJB or JPA. The comparison page says Tomcat supports only a subset of Jakarta EE while TomEE is fully compliant, so a team that has outgrown plain servlets can stay on a familiar base.
- A team building MicroProfile services. With a dedicated MicroProfile distribution at 6.1 in the stable line, a group writing services to that standard can download a matching package instead of assembling one.
- A project with no budget for licences. The site lists no prices and the licence is Apache 2.0, so a volunteer project or small company can run it without a purchase. Paid support is not described on the pages we read.
Getting started with Apache TomEE
The pages we read describe the distributions and downloads rather than a numbered setup tutorial. Begin on the download page. It states that TomEE requires Java 17 or higher for both release lines, so check the runtime first. Pick a distribution: the comparison page advises Plume when in doubt, while WebProfile suits applications that only need the web-tier specifications.
Download the ZIP or TAR.GZ archive, together with its PGP signature and SHA512 checksum, and verify the file, because the page says users must verify integrity. Use 10.3.0 for production, since the 11.0.0-M2 milestone for Jakarta EE 11 does not yet pass the full TCK and the page says it should not be used in production. The documentation then covers configuration, directory structure, testing and clustering, with examples for CDI, REST, EJB and JSF.
What we make of Apache TomEE
Apache TomEE is a Jakarta EE application server built on Tomcat, and its comparison page says Tomcat covers only a subset of Jakarta EE while TomEE is fully compliant.
Releases come in four distributions, with Plume advised when in doubt. The download page says unpaid volunteers maintain it, the pages read list no paid support, and the Jakarta EE 11 milestone is marked not for production.
In our application servers ranking Apache TomEE stands at #5 of 14: it follows Payara Server and comes before Apache Tomcat. From place 4 the established names follow in their ranked order; we publish no numeric score.
The vendor states no country of establishment, so Apache TomEE is left out of the regional count for this list.
The case for and against Apache TomEE
- Apache TomEE is a Jakarta EE application server built on Tomcat, and its comparison page says Tomcat covers only a subset of Jakarta EE while TomEE is fully compliant.
- Best for: Teams wanting CDI, EJB Lite and JPA on top of a familiar Tomcat base.
- Apache TomEE is tagged Built on Tomcat in our records.
- Marked in our records as four distributions.
- Catalogue tag: Volunteer-run.
- Look elsewhere if you are Buyers needing a support contract or Jakarta EE 11 in production.
- The only Jakarta EE 11 build is the 11.0.0-M2 milestone, which does not yet pass the full TCK.
- The project is maintained by unpaid volunteers, and the pages read show no commercial support offer.
Apache TomEE pros and cons in practice
- The Apache License, Version 2.0 is stated in the page footer.
- Four distributions let a team pick the amount of platform it installs.
- The comparison page says TomEE is fully compliant with Jakarta EE, while Tomcat supports a subset.
- Downloads carry PGP signatures and SHA512 checksums.
- The download page says the project is maintained by unpaid volunteers, and the pages read list no paid support.
- The Jakarta EE 11 milestone is marked not for production and has not passed the full TCK.
- Java 17 or higher is required for both release lines.
- Choosing among four distributions takes reading, since the advice offered is only 'when in doubt, choose Plume'.
What Apache TomEE costs
In the catalogue: Archive downloads under the Apache Licence 2.0; the site lists no prices.
The project site lists no prices and offers downloads only. The download page does not say whether the software costs money, and the footer names the Apache License, Version 2.0, so the licence terms are the only commercial statement on the pages we read. The download page states that the project is developed and maintained by unpaid volunteers, and the pages read describe no paid support, subscription or vendor contract. A company that needs guaranteed response times would therefore have to find a support arrangement elsewhere, and none is named on the pages read. Budgeting should count hosting, staff time to verify and update downloads, and any outside support, none of which is priced by the project. The distribution sizes of about 59 MiB to 81 MiB for release 10.3.0 are the only cost-related figures given.
We took this from tomee.apache.org, the vendor’s own site, when we reviewed Best Application Servers in 2026; that review is dated 15 November 2026.
Living with Apache TomEE: setup and exit
TomEE 10.3.0 implements Jakarta EE 10 with MicroProfile 6.1 and requires Java 17 or higher.
Distributions weigh roughly 59 MiB for Webprofile up to 81 MiB for Plume.
The Web Profile covers Servlets, JSP, JSF, JTA, JPA, CDI, Bean Validation and EJB Lite, while Plus and Plume add JMS and JAX-WS.
The stack combines OpenWebBeans, OpenEJB, Geronimo Transaction Manager, BVal and CXF.
Each download carries a PGP signature and a SHA512 checksum.
Apache TomEE: data and security
TomEE is downloaded and run by the customer, so data stays wherever the server is installed. The download page gives each file a PGP signature and a SHA512 checksum and tells users they must verify the integrity of downloaded files, which protects against tampered archives. The pages we read list no certifications, audit reports or a described vulnerability reporting procedure.
The project is governed by the Apache Software Foundation, named in the copyright notice, and developed by unpaid volunteers according to the download page. The 11.0.0-M2 milestone does not yet pass the full Jakarta EE TCK and is marked not for production, so it should stay out of any system holding live data. No country of establishment is stated on the pages read.
Integrations and ecosystem
Integrations the vendor names (9):
- Apache Tomcat
- Apache OpenWebBeans
- Apache OpenEJB
- Geronimo Transaction Manager
- Apache BVal
- Apache CXF
- MicroProfile
- JMS
- JAX-WS
Fact sheet: Apache TomEE
| Product | Apache TomEE |
|---|---|
| Vendor website | tomee.apache.org |
| Catalogue tags | Built on Tomcat, Four distributions, Volunteer-run |
| Head-to-head pages | No comparison written |
| Headquarters | Not stated by the vendor |
| Not in our data | company size and funding |
| Alternatives page | None yet |
| Rank there | #5 of 14 |
| Price visibility | Model recorded, no figure |
| Primary guide | Best Application Servers in 2026 |
Close alternatives to Apache TomEE
These are the nearest neighbours of Apache TomEE in the same list, picked on shared traits and price model.
- WildFly (#7 of 14): Modular Java application server with Galleon provisioning and a Kubernetes operator. Watch out: the pages read do not state who develops WildFly day to day or where it is based.
- Uvicorn (#10 of 14): Not for: synchronous WSGI applications or buyers wanting commercial support. ASGI web server for Python async frameworks, run with one command.
- Red Hat JBoss EAP (#12 of 14): Not for: buyers wanting prices on the page before talking to sales. Red Hat's supported Jakarta EE platform for on-premise and cloud.
- Oracle WebLogic Server (#13 of 14): Oracle's Jakarta EE server in three editions, with 30-day cloud access. Watch out: the Standard Edition page names Jakarta EE 8 and 9.1, behind the Jakarta EE 11 targets of other servers in this category.
- IBM WebSphere Application Server (#14 of 14): IBM's Java EE server family with Liberty, z/OS and hybrid editions. Best for: Established IBM estates running mixed on-premises and private-cloud Java workloads.
Every guide that lists Apache TomEE
| Guide | Position |
|---|---|
| Best Application Servers in 2026 | #5 of 14 |
Apache TomEE FAQ
9 answersHow much does Apache TomEE cost?
Our catalogue records Apache TomEE’s pricing as: Archive downloads under the Apache Licence 2.0; the site lists no prices. On free access, we recorded no free plan.
Which country is Apache TomEE from?
The vendor pages we reviewed state no country of establishment for Apache TomEE, so we do not give one.
Is Apache TomEE one of the top application servers?
Position 5 of 14 is where Apache TomEE sits among application servers.
Is Apache TomEE the right fit for me?
Teams wanting CDI, EJB Lite and JPA on top of a familiar Tomcat base. It is a weaker match for the following: buyers needing a support contract or Jakarta EE 11 in production.
What are the main alternatives to Apache TomEE?
The nearest neighbours in our ranking are WildFly, Uvicorn, Red Hat JBoss EAP, Oracle WebLogic Server and IBM WebSphere Application Server. Each of them has its own entry in the same guide.
Does TomEE have a price?
The project site lists no prices and offers downloads only. The download page does not say whether the software costs money, and the licence is Apache 2.0.
Which distribution should I choose?
The comparison page advises that when in doubt you should choose Plume. WebProfile, MicroProfile and Plus are the other three.
Can I run the Jakarta EE 11 version?
The 11.0.0-M2 milestone implements Jakarta EE 11 but does not yet pass the full TCK and is marked not for production. Release 10.3.0 implements Jakarta EE 10.
Which Java version is needed?
The download page states TomEE requires Java 17 or higher for both release lines.
Apache TomEE: sources
Read from the vendor’s own pages on 14 November 2026.
- tomee.apache.org: Description, licence, governance, distributions and Web Profile coverage
- tomee.apache.org/download.html: Release lines, Java requirement, archive sizes, signatures and volunteer statement
- tomee.apache.org/comparison.html: Distribution advice, Tomcat base, component implementations and documentation examples
How we rank
Feature lists tell little, so positions rest on setup effort, the true price, portability and fit. Apache TomEE ends up at #5 among 14. How vendor facts are sourced, and how money can and cannot influence a page, is in the editorial process.