AI Buyer Insights:

Moog, an UKG AutoTime customer evaluated Workday Time and Attendance

Swedbank, a Temenos T24 customer evaluated Oracle Flexcube

Wayfair, a Korber HighJump WMS customer just evaluated Manhattan WMS

Michelin, an e2open customer evaluated Oracle Transportation Management

Cantor Fitzgerald, a Kyriba Treasury customer evaluated GTreasury

Citigroup, a VestmarkONE customer evaluated BlackRock Aladdin Wealth

Westpac NZ, an Infosys Finacle customer evaluated nCino Bank OS

Moog, an UKG AutoTime customer evaluated Workday Time and Attendance

Swedbank, a Temenos T24 customer evaluated Oracle Flexcube

Wayfair, a Korber HighJump WMS customer just evaluated Manhattan WMS

Michelin, an e2open customer evaluated Oracle Transportation Management

Cantor Fitzgerald, a Kyriba Treasury customer evaluated GTreasury

Citigroup, a VestmarkONE customer evaluated BlackRock Aladdin Wealth

Westpac NZ, an Infosys Finacle customer evaluated nCino Bank OS

List of Eclipse Jetty Customers

Apply Filters For Customers

Logo Customer Industry Empl. Revenue Country Vendor Application Category When SI Insight Insight Source
Apache Software Foundation Non Profit 10 $2M United States Eclipse Foundation Eclipse Jetty Apps Development 2007 n/a In 2007, Apache Software Foundation embedded Eclipse Jetty to host Apache ActiveMQ's Web Console and REST endpoints for messaging administration and monitoring. This use of Eclipse Jetty is categorized as Apps Development and supports messaging and operations business functions for ActiveMQ. Eclipse Jetty is deployed as an embedded HTTP servlet container within the ActiveMQ process, started by importing conf/jetty.xml that configures connectors, context handlers, and servlet mappings to expose the admin UI and web APIs. The ActiveMQ distribution explicitly imports conf/jetty.xml to provision the Jetty container and its servlet configuration at broker startup. The architecture co-locates web hosting with the broker process rather than a separate web tier, so the Web Console and REST endpoints are served in process with ActiveMQ. Operational coverage centers on messaging administration, monitoring endpoints, and web based operations for deployments maintained by the Apache community in the United States. Configuration and governance are handled through the conf/jetty.xml file distributed with ActiveMQ, enabling declarative control over servlets, security realms, and resource handlers used by the admin UI. Eclipse Jetty provides an in process web hosting model for ActiveMQ within Apps Development, aligning runtime hosting, configuration, and administrative tooling.
Google Communications 190820 $402.8B United States Eclipse Foundation Eclipse Jetty Apps Development 2008 n/a In 2008, Google integrated Eclipse Jetty into Google App Engine as the default servlet container for its Java runtimes, aligning with Apps Development needs for hosted Java execution. Eclipse Jetty runs as the embedded servlet and HTTP engine that powers request handling and manages servlet lifecycle for App Engine Java applications. Google App Engine uses Jetty to provide the local development runtime and to mirror production request handling behavior. The deployment embeds Eclipse Jetty within App Engine Java runtimes across Google Cloud regions in the United States and globally, making Eclipse Jetty the core runtime component for hosting and testing Java workloads. Functionally this implementation covers servlet container responsibilities, HTTP request processing, and local development tooling integration, supporting developer platform and application hosting functions on App Engine. Google Cloud documentation indicates the Jetty-based runtime has been used to improve performance and scalability of Java applications on App Engine.
Zimbra Professional Services 200 $20M United States Eclipse Foundation Eclipse Jetty Apps Development 2007 n/a In 2007, Zimbra implemented Eclipse Jetty to gain scalable Comet and Bayeux protocol support for real-time push notifications and low-latency web UI updates in its email and collaboration web client in the United States. Eclipse Jetty was adopted as a core component of Zimbra's Apps Development footprint to enable event driven HTTP connection handling and more efficient push delivery for web services. The implementation focused on addressing long-polling delivery patterns and connection management to reduce server-side thread usage for client facing services. Deployment leveraged Jetty's event driven connector model to handle long lived HTTP connections and Bayeux messaging, enabling server push and low-latency UI update orchestration within Zimbra's web client. Functional capabilities implemented included Comet style handling, Bayeux protocol message routing, long-polling scalability improvements, and integration of server push into email and collaboration workflows. The adoption explicitly improved long-polling scalability and reduced server-side thread usage for Zimbra's web services.
Showing 1 to 3 of 3 entries

Buyer Intent: Companies Evaluating Eclipse Jetty

ARTW Buyer Intent uncovers actionable customer signals, identifying software buyers actively evaluating Eclipse Jetty. Gain ongoing access to real-time prospects and uncover hidden opportunities.

Discover Software Buyers actively Evaluating Enterprise Applications

Logo Company Industry Employees Revenue Country Evaluated
No data found