Quarkus
Quarkus is an open-source, Kubernetes-native full-stack Java framework that helps developers build cloud-native, reactive and containerized applications with fast startup and low memory usage. Stewarded under the Commonhaus Foundation, it is used by enterprises and developers, with commercial support sold by Red Hat, IBM and HeroDevs.
- Company typePrivate
- Founded2019
- Headquarters—
- Headcount5,001–10,000
- GTM typeB2B
- OfferingSoftware
What Quarkus does
Quarkus is an open-source, container-first, Kubernetes-native full-stack Java framework (marketed as "Supersonic Subatomic Java") that provides application developers and engineering teams with fast startup, low memory footprint and efficient containerized deployment. It originated at Red Hat around 2018–2019 (earliest recorded release 0.2 on December 19, 2018; Quarkus 1.0 on November 25, 2019) and is now stewarded under the Commonhaus Foundation, a non-profit that provides neutral governance, legal aid and infrastructure. The project serves Java developers building cloud-native microservices and reactive applications, Spring Boot teams migrating to a Kubernetes-native runtime, AI application developers building agentic and RAG-based services, and enterprises requiring commercially supported, longer-lifecycle builds.
Technically, Quarkus performs build-time augmentation — precomputing application metadata and optimizing class loading at build time to remove runtime reflection and reduce runtime dependencies — using a technique the project calls "compile time boot." It targets both GraalVM native binaries and HotSpot JVM deployments, emphasizing low RSS memory (not just heap) for high-density Kubernetes orchestration. The core is built on a reactive backbone of over fifty standards-based community libraries, including Eclipse Vert.x (reactive core), SmallRye, Hibernate, Netty, RESTEasy (now Quarkus REST), Apache Camel and Eclipse MicroProfile. Around that core sit an extension ecosystem distributed as Maven artifacts through Maven Central and the registry.quarkus.io registry, the Quarkiverse community hub, developer tooling (Quarkus CLI, Dev UI, Dev Assistant, Dev MCP), the Quarkus Extension Catalog, and a data layer now consolidated in the experimental "Hibernate with Panache" (Panache Next) extension. Quarkus-owned technical assets include the Gizmo 2 bytecode generation library and ArC, Quarkus's CDI Lite implementation, both of which migrated to Gizmo 2 in the Quarkus 3.30 release.
Commercially, Quarkus generates no direct revenue: the core framework and its dependencies are free under the Apache Software License 2.0 or a compatible license. Monetization is indirect and executed by third parties — Red Hat and IBM (Enterprise Build of Quarkus) sell commercially supported, longer-lifecycle enterprise offerings, and HeroDevs provides Never-Ending Support with on-demand patches and compliance support for end-of-life community versions; no pricing is publicly disclosed. The wider Quarkiverse extension ecosystem runs on a decentralized sponsorship model in which individual extensions are backed by their own benefactors (companies or community initiatives) through developer time, financial backing or infrastructure contributions, with no central licensing fees. Go-to-market is product-led and community-led: self-serve adoption via code.quarkus.io, the CLI and the Maven/Gradle plugins; demand generation through a content hub, a monthly newsletter (70 issues), the Quarkus Insights video podcast (255 episodes) and conference presence at KubeCon Japan and China, JavaZone, Riviera Dev, Open Source Summit Korea and MCP Dev Summit Seoul. Named enterprise users include Lufthansa Aviatar, Banco do Brasil, AXA, Capgemini, SNCF, Vodafone, Scientific Games, Keycloak and Adoptium. The project reports 5,001–10,000 employees in the firmographic data, though no headcount, funding, revenue or cap-table detail is disclosed for the project itself.
Quarkus firmographics
Firmographics- Name
- Quarkus
- Legal name
- Quarkus
- Website
- https://quarkus.io
- Company type
- Private
- Founded year
- 2019
- Operating status
- Operating
- Headcount range
- 5,001–10,000 employees
- Short description
- Quarkus is an open-source, Kubernetes-native full-stack Java framework that helps developers build cloud-native, reactive and containerized applications with fast startup and low memory usage. Stewarded under the Commonhaus Foundation, it is used by enterprises and developers, with commercial support sold by Red Hat, IBM and HeroDevs.
- Ownership category
- akta.pro rank
Quarkus industry classification
Industry- Product category
- Application Framework / Developer Platform (Cloud-Native Java)
- NAICS
- Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services (51821), Custom Computer Programming Services (541511)
- SIC
- Services-Prepackaged Software (7372), Services-Computer Programming, Data Processing, Etc. (7370)
- akta.pro industry
- Cloud-Native Application Development (Containers/Kubernetes/Serverless)Business & Public Services/IT & Digital Services (Managed Services, Systems Integration)/Application Development & ModernizationEnterprise Application Lifecycle Management (ALM) PlatformsHardware, Technology & Telecom/Enterprise Platforms & Databases/Enterprise Application Development Platforms (Low-Code/No-Code & PaaS)Cloud-Native/Kubernetes ObservabilityHardware, Technology & Telecom/Cloud & Data Center Infrastructure/Observability, Monitoring & AIOps for Cloud
Keywords
Quarkus business model
Business model- GTM type
- B2B
- Offering type
- Software
- Cost components
- Personnel, Technology or R&D, Infrastructure, Marketing or Sales
Revenue model
- Open-source framework (no direct revenue): Quarkus itself is a free, open-source project whose dependencies are available under the Apache Software License 2.0 or a compatible license, with the source code hosted on GitHub; it generates no direct revenue for the project, which is hosted under the Commonhaus Foundation.
- Enterprise support offerings: Enterprise offerings of Quarkus are actively maintained with longer lifecycles than community releases and are sold commercially by Red Hat, IBM (IBM Enterprise Build of Quarkus) and HeroDevs (Never-Ending Support), which provide on-demand security patches and compliance support for end-of-life community versions.
- Ecosystem extension ecosystem (Quarkiverse): Individual extensions in the Quarkiverse are often supported by their own benefactors, ranging from companies to community initiatives, through developer time, financial backing or infrastructure contributions; this decentralized sponsorship model sustains the broader extension ecosystem without central licensing fees.
Go-to-market motion4 records
Distribution channels7 records
Marketing channels9 records
Quarkus product offering
Product offeringCore offering
Quarkus is a free, open-source (Apache Software License 2.0) full-stack Java application framework that is container-first and Kubernetes-native. It performs build-time augmentation — extending and pre-computing application metadata at build time to eliminate runtime reflection and reduce runtime dependencies — producing fast startup and low memory usage for both JVM and GraalVM native binary deployments. It is built on a reactive core and a backbone of standards-based libraries (Eclipse Vert.x, SmallRye, Hibernate, Netty, RESTEasy, Apache Camel, Eclipse MicroProfile), and is extended through a large catalog of build-time integrated extensions distributed via the Quarkus Extension Registry and Maven Central.
Product overview
Quarkus is a single open-source Java application platform ("Supersonic Subatomic Java") that is delivered as a core framework plus an extension/module ecosystem rather than one monolithic product. The core platform (Quarkus) provides a Kubernetes-native, container-first full-stack framework on a standard backbone of over fifty best-of-breed libraries (Eclipse Vert.x, SmallRye, Hibernate, Netty, RESTEasy, Apache Camel, Eclipse MicroProfile), with unified configuration, live reload, fast startup and GraalVM/HotSpot native executable generation. Around that core sit named offerings: the AI-oriented portfolio (Quarkus for AI, AI Blueprints such as Frozen RAG, Contextual RAG and Chain of Thought), the developer tooling layer (Quarkus Dev UI, Quarkus Dev Assistant provided via the Quarkiverse Chappie extension, Quarkus Dev MCP, Quarkus CLI), the discovery/distribution layer (Quarkus Extension Registry at registry.quarkus.io and the Quarkus Extension Catalog/Quarkiverse Hub), the data layer (Quarkus Data / the new experimental Hibernate with Panache extension) and underlying platform libraries such as Gizmo 2 and Roq static site generation. Enterprise and community users additionally obtain commercial support, on-demand patches for end-of-life versions and migration tooling (including Spring migration support) from Red Hat, IBM, HeroDevs and other supporters of the Commonhaus Foundation.
Differentiator
Problem solved
Functional benefit
Brands
- Quarkiverse: Community extension hub (hub.quarkiverse.io) hosting third-party Quarkus extensions, each with its own community benefactors and support model, distributed via the Quarkus extension registry at registry.quarkus.io.
Products and services
- Quarkus Supersonic Subatomic Java: a full-stack, container-first, Kubernetes-native Java framework built on a growing list of over fifty best-of-breed libraries (Eclipse Vert.x, SmallRye, Hibernate, Netty, RESTEasy, Apache Camel, Eclipse MicroProfile) on a standard backbone. It offers unified configuration, zero-config, live reload, native executable generation and fast startup for JVM and native binary deployments via a compile-time boot technique. Free and open source under the Apache Software License 2.0 or a compatible license.
- Quarkus for AI Umbrella offering for building next-generation AI applications on Quarkus, with dedicated sub-pages for AI Overview, Java for AI, Why Quarkus for AI and AI Blueprints.
- AI Blueprints (Frozen RAG, Contextual RAG, Chain of Thought) Collection of AI application patterns and blueprints published by the Quarkus project, including Frozen RAG (Retrieval-Augmented Generation), Contextual RAG and the Chain of Thought pattern, intended as templates for AI workloads built on Quarkus.
- Quarkus Dev Assistant (Chappie) AI-powered helper built into Quarkus Dev Mode that troubleshoots exceptions and stack traces, generates client code, javadoc, test code and test data, and completes TODO sections; enabled by adding the io.quarkiverse.chappie:quarkus-chappie extension and configured for OpenAI-compatible providers (OpenAI, OpenShift AI, Podman AI Lab) or Ollama local models. Interfaces live in Quarkus core while the default implementation resides in Quarkiverse.
- Quarkus Dev MCP Model Context Protocol server integration for Quarkus dev mode enabling AI-powered developer assistance via MCP.
- Quarkus Dev UI Development-mode user interface hosting the Dev Assistant, extension pages, workspace actions and a JSON-RPC bridge to the runtime and deployment classpaths.
- Quarkus CLI Command-line dev tool for creating projects, adding extensions (e.g. "quarkus ext add io.quarkus:quarkus-config-yaml") and listing/searching the Quarkus extension ecosystem via the extension registries.
- Quarkus Extension Registry (registry.quarkus.io) Default community extension registry, a Maven snapshot repository serving platform and extension catalogs as Maven JSON artifacts to the Quarkus CLI, Maven and Gradle plugins and code.quarkus.io; it supports multiple registries, offering-scoped catalogs and configurable update policies.
- Quarkus Data / Hibernate with Panache (Panache Next) New experimental data-access extension unifying Hibernate ORM with Panache and Hibernate Reactive with Panache into one module, supporting blocking or reactive drivers, managed or stateless entities, type-safe @Find/@HQL queries and Jakarta Data type-safe queries.
- Gizmo 2 Simplified bytecode generation library used across Quarkus, rewritten from Gizmo 1 (ASM-based) on top of the ClassFile API backport that supports Java 17; ArC (Quarkus's CDI Lite implementation) has migrated to it, with breaking changes confined to build-time extension APIs.
- Spring migration support for Quarkus Guides and compatibility layers helping Spring developers adopt Quarkus, including "Leverage your Spring expertise on Quarkus" and "Migrate to Quarkus", supported by the Spring-Style Testing working group providing compatibility layers for common Spring testing patterns.
- Roq (Quarkus SSG) Static Site Generation capability for Quarkus (Roq :: Quarkus SSG working group completed November 18, 2024); the working group to convert the quarkus.io website from Jekyll to Roq was completed July 21, 2026.
- Quarkus Insights Video podcast hosted by Quarkus developers covering things moving in and around the Quarkus ecosystem, with more than 250 episodes including topics such as Quarkus 4 planning, observability, agentic AI with LangChain4j and MCP, Quarkus Data and the 3.33 LTS update.
Quantifiable outcome
- Leverages a growing list of over fifty best-of-breed libraries wired on a standards backbone
- +2 more outcomes
Companies that use Quarkus
Customer profileNamed customers10 records
Segments4 records
Ideal customer profiles4 records
Quarkus technology and API
TechnologyTechnology focussed Yes
API detail
- Has API
- Yes
- API docs
- API detail
Core technology
AI maturity
App detail
Integration15 records
AI capability7 records
Feature8 records
Quarkus partnerships and signals
Strategic signalPartnerships
13 partnerships are on record, tiered foundational, core and minor.
- Commonhaus FoundationfoundationalQuarkus is a proud member of the Commonhaus Foundation, a non-profit dedicated to the enduring viability of open-source projects. The foundation offers a neutral environment, a governing structure and assistance to projects, furnishing resources such as legal aid, infrastructure and financial avenues while honoring each project's governance and culture. The move was made to address the perception that Quarkus was overly dependent on a single vendor (Red Hat).
- Red HatcoreQuarkus originated at Red Hat, which ensured ongoing development and stability by employing many of its principal engineers and cultivating a strong ecosystem for cloud-native application development. Red Hat is also listed among Quarkus Enterprise Supporters and provides commercial, longer-lifecycle enterprise offerings. Red Hat's dedication to open-source was a key reason for Quarkus's transition to the Commonhaus Foundation.
- IBMcoreIBM strengthened its Java and Quarkus commitment by moving the Red Hat engineers working on Quarkus into IBM, ensuring dedicated resources for Quarkus's growth and deepening IBM's open-source involvement and focus on cloud-native Java for enterprises. IBM is also listed as a Quarkus Enterprise Supporter and distributes the IBM Enterprise Build of Quarkus.
- HeroDevscoreHeroDevs provides Never-Ending Support (NES) for Quarkus, including security fixes and compliance patches for end-of-life versions, and is also listed among Quarkus Enterprise Supporters. It bridges the gap for organizations not yet ready to upgrade from an EOL version.
- AWSminorAWS aids Quarkus by donating credits, enabling developers to use AWS services for testing, CI and feature development. This support is described as accelerating Quarkus innovation and enhancing the cloud-native experience on AWS.
- Eclipse Vert.xcoreQuarkus is made of community projects, and Eclipse Vert.x is the reactive core underlying Quarkus, with HTTP/3 support and related APIs tracked in the Vert.x 5.1 roadmap and discussed in Quarkus Insights.
- SmallRyecoreSmallRye is one of the community projects Quarkus is built from, contributing the MicroProfile and Quarkus extension implementations (e.g., SmallRye Context Propagation is a dependency of core extensions such as quarkus-rest).
- HibernatecoreHibernate (ORM) is one of the community projects Quarkus is built from and is integrated with Panache APIs, Hibernate Search, and the new unified 'Hibernate with Panache' (Panache Next) experimental extension, with the Quarkus Data working group developing the next version of Panache.
- NettycoreNetty is listed among the community projects Quarkus is made from and is a direct dependency of core Quarkus extensions such as quarkus-vertx and quarkus-rest.
- RESTEasycoreRESTEasy (now Quarkus REST) is one of the community projects Quarkus is built from; the Quarkus REST extension is a Jakarta REST implementation utilizing build time processing and Vert.x.
- Apache CamelcoreApache Camel is one of the community projects Quarkus is built from, with Camel integration provided through the Quarkiverse, including AI-focused Camel capabilities discussed in Quarkus Insights.
- Eclipse MicroProfilecoreEclipse MicroProfile is one of the community projects Quarkus is built from, providing the standards backbone (for example MicroProfile Fault Tolerance API, MicroProfile LRA and OpenAPI) implemented by Quarkus extensions.
- QuarkiversecoreThe Quarkiverse is the community home for Quarkus extensions hosted on the Quarkiverse Hub and included in the default community extension registry. Individual extensions benefit from their own benefactors, from companies to community initiatives, providing developer time, financial backing or infrastructure under a decentralized sponsorship model.
Scale indicators8 records
Recent moves7 records
Expansion highlights7 records
Quarkus competitors and assessment
Company assessmentDirect peers
- Micronaut: Compile-time dependency-injection JVM framework with GraalVM native-image support, sold into the same cloud-native microservices use case. Like Quarkus it targets fast startup and low memory footprint on Kubernetes, and is the most frequently compared alternative to Quarkus for greenfield JVM cloud work.
- Eclipse Helidon: Oracle-led, Eclipse-hosted Java microservices framework with first-class GraalVM native compilation and a MicroProfile-based standards stack. It competes head-on with Quarkus for enterprise Java cloud-native workloads and is typically named in the same vendor evaluations.
- Ktor: JetBrains' Kotlin coroutine-based server framework for cloud-native microservices with lightweight, plugin-based deployment. It addresses the same developer need (fast-starting, small-footprint containerised backend services) in a different JVM language.
- Eclipse Vert.x: Reactive toolkit that forms the reactive core underpinning Quarkus itself, with HTTP/3 and related APIs tracked in the Vert.x 5.1 roadmap. It is the closest architectural analogue and a direct competitor for reactive JVM service development.
- Payara: Jakarta EE application server focused on cloud-native deployment, with GraalVM native-image support and MicroProfile compatibility. It targets the same "standards-compliant enterprise Java in containers" buyer as Quarkus but from the application-server rather than framework-first model.
- Dropwizard: Convention-over-configuration Java framework for building production-grade microservices with fat-jar deployment. It occupies the same developer-tooling and self-serve adoption motion as Quarkus, albeit without Quarkus's build-time augmentation or native-binary story.
Broad incumbents
- Spring Boot: The dominant Java application framework, against which Quarkus benchmarks itself and whose installed base is Quarkus's primary migration source. It offers overlapping cloud-native, native-image and AI-adjacent capabilities as part of a much broader Spring portfolio.
- WildFly: Red Hat's long-established Jakarta EE application server and the enterprise Java runtime Quarkus's originators also maintain. It represents the incumbent, full-stack runtime alternative for organisations standardising enterprise Java on containers.
Emerging players
- JHipster: Generator-driven platform that scaffolds full-stack Java applications on Spring Boot and Quarkus. It sits in the same developer self-serve funnel as code.quarkus.io and can accelerate or shape Quarkus adoption among new projects.
Others
- GraalVM: Oracle's JVM toolchain providing the native-image technology Quarkus targets for its GraalVM native binary deployments and that its AOT working group leverages via Project Leyden and JLink. It is an enabling dependency of Quarkus's core performance differentiation rather than a competing framework.
Market position
Strengths5 records
Weaknesses5 records
Competitive moat6 records
Key risks7 records
Key highlights7 records
Customer concentration
Quarkus social profiles
Digital presenceQuarkus financial estimates
Financial estimateRevenue estimate
Valuation estimate
Quarkus leadership team
Management profileNumber of profiles
Profiles14 records
Quarkus funding detail
Funding detailFunding overview
Funding rounds
Investors
Funding detail is available on the Subscription and Enterprise plan.Contact sales →
Quarkus M&A and investment
M&A and investmentM&A
Investments
M&A and investment is available on the Subscription and Enterprise plan.Contact sales →
Frequently asked questions about Quarkus
What does Quarkus do?
Quarkus is a free, open-source (Apache Software License 2.0) full-stack Java application framework that is container-first and Kubernetes-native. It performs build-time augmentation — extending and pre-computing application metadata at build time to eliminate runtime reflection and reduce runtime dependencies — producing fast startup and low memory usage for both JVM and GraalVM native binary deployments. It is built on a reactive core and a backbone of standards-based libraries (Eclipse Vert.x, SmallRye, Hibernate, Netty, RESTEasy, Apache Camel, Eclipse MicroProfile), and is extended through a large catalog of build-time integrated extensions distributed via the Quarkus Extension Registry and Maven Central.
Is Quarkus a public or private company?
Quarkus is a private company. It is classified as nonprofit foundation owned and is currently operating.
When was Quarkus founded?
Quarkus was founded in 2019. It employs 5,001 to 10,000 people.
How does Quarkus make money?
Three revenue lines are on record. Open-source framework (no direct revenue) is the primary driver. The others are enterprise support offerings and ecosystem extension ecosystem (Quarkiverse).
Who are Quarkus's main competitors?
Direct peers on record are Micronaut, Eclipse Helidon, Ktor, Eclipse Vert.x, Payara and Dropwizard. Broad incumbents are Spring Boot and WildFly. JHipster is listed as an emerging player. GraalVM is listed as an others.
Does Quarkus have an API?
Yes. Quarkus is a developer framework rather than a single hosted SaaS API, but it exposes several developer-facing APIs and programmatic surfaces. Applications built on Quarkus expose HTTP APIs via the Quarkus REST extension (formerly RESTEasy Reactive, a Jakarta REST implementation using build-time processing and Vert.x), and the ecosystem includes GraphQL, gRPC, WebSocket (WebSockets Next), and OpenAPI/Swagger UI guides, plus MicroProfile and Jakarta Data programmatic APIs. The Quarkus Extension Registry at registry.quarkus.io exposes a Maven snapshot repository API that serves platform and extension catalogs as Maven JSON artifacts, consumed by the Quarkus CLI, Maven and Gradle plugins, and code.quarkus.io; the registry client can be configured via YAML config files, the QUARKUS_REGISTRIES and QUARKUS_REGISTRY_* environment variables, and can be proxied through Nexus 2.x/3.x. The Quarkus Dev UI also exposes a JSON-RPC API for extension and Dev Assistant actions (runtime and deployment classpaths). Availability is open source under Apache License 2.0, with the registry checked for catalog updates daily by default (configurable to always, interval:X, or never). Developer documentation is at quarkus.io/guides/extension-registry-user.
What industry is Quarkus in?
Quarkus's product category is Application Framework / Developer Platform (Cloud-Native Java). Its primary akta.pro industry code is BPAEAFAE, Cloud-Native Application Development (Containers/Kubernetes/Serverless), with a secondary code of HDAEAKAJ, Enterprise Application Lifecycle Management (ALM) Platforms. Its NAICS code is 51821 and its SIC code is 7372.