The cleverest thing about BellSoft may be that its product is designed to disappear. When a bank's trading system starts on time, an airline's Java service survives another security update, or a developer pulls a smaller container image, nobody applauds the runtime. They simply get on with the work. BellSoft lives in that invisible layer - beneath the application and above the hardware - where boring is a compliment and a surprise is usually expensive.
The San Jose company was founded in 2017 by Java veterans including CEO Alexander Belokrylov and CTO Aleksei Voitylov. Before BellSoft, both had worked in the Sun Microsystems and Oracle orbit. Their team had helped shape Java for embedded devices, a world where memory, storage and power are treated as scarce goods. The founders noticed that cloud computing had recreated the same constraint with a monthly invoice attached: every oversized container and slow-starting service costs money at scale.
That observation became a product strategy. Start with Liberica JDK, a tested distribution of OpenJDK. Add editions for compact cloud deployments, old enterprise applications, desktop JavaFX software, native executables and faster startup. Build a lightweight Linux underneath it. Then sell engineering support across the stack. In late 2025, BellSoft added hardened container images; in July 2026, it put those images inside a builder for Paketo Buildpacks. The company that began by packaging Java now wants to secure the path from source code to production container.
A JDK is a promise, not a zip file
Liberica JDK is BellSoft's center of gravity. It is free for commercial use, built from OpenJDK and verified with Java's Technology Compatibility Kit. That last point matters because an enterprise changing JDK vendors does not want a migration adventure. It wants the same application to run, the patch calendar to remain predictable and an engineer to answer when something peculiar happens in production.
The range is broad by design. BellSoft publishes builds for current Java, long-term-support releases and even Java 6 and 7 for organizations still carrying old systems. It supports Windows, macOS, Linux and Solaris across architectures including x86, Arm, PowerPC, SPARC and RISC-V. The catalog includes Standard, Full and Lite packages, a Performance Edition for older applications, and builds supporting Coordinated Restore at Checkpoint, or CRaC, which saves a warmed-up application's state and restores it quickly.
“We rely on the Liberica team's experience and expertise to provide timely updates for our customers.”Konstantin Bulenkov, Head of JetBrains Runtime
The buyers are platform teams, software vendors and enterprises with fleets of Java applications. BellSoft names JetBrains, Flow Traders, SoftChalk, QZ Tray and shipping company OOCL among users or customers, alongside government and education deployments. Their problems vary, but the procurement logic rhymes: control licensing expense, keep old software patched, reduce memory use, cover unusual hardware, and have one accountable team when the open-source ingredients interact badly.
The small Linux with a large job
Alpaquita Linux is the strategic hinge. The open-source distribution is available with either musl or glibc, supports x86 and Arm, and is intentionally spare. Its downloadable Stream musl miniroot is listed at about 3.52 MB. The point is not winning a beauty contest for tiny files. A smaller base can mean less disk, faster distribution and fewer components that might produce vulnerability alerts.
More importantly, BellSoft controls both the Java runtime and the operating-system layer. Most OpenJDK vendors hand off the OS problem to somebody else. BellSoft can tune the two together, ship a Liberica Runtime Container, and offer one support path. The arrangement also makes technologies such as CRaC more practical: the runtime and Linux need to cooperate to checkpoint a running service and restore it near its warmed-up state.
Free software, paid certainty
BellSoft's business model is familiar in open-source infrastructure. The binaries and base images create distribution; support creates revenue. Enterprises pay for long maintenance windows, migration help, fixes, 24/7 access to engineers, OEM arrangements and service-level agreements. The new hardened-image plans add deadlines for vulnerability remediation. A partner program extends the route to market through resellers, referrers, implementers and vendors that embed BellSoft technology.
This is not a conventional subscription app. Usage can grow without revenue growing in lockstep, and BellSoft does not disclose annual sales, valuation or outside funding. It did say that its customer count and Liberica JDK revenue each doubled in 2024. For 2025, it reported Liberica downloads up 55 percent, Alpaquita downloads doubling and runtime-container pulls increasing fourfold. These are company figures, useful as signs of momentum rather than audited market share.
A crowded market, a specific wedge
Nobody shopping for OpenJDK lacks options. Oracle sits at one end; Eclipse Temurin, Amazon Corretto, Microsoft, Red Hat, SAP and Azul fill out the field. GraalVM distributions compete in native compilation, while Chainguard and others sell hardened containers. Many alternatives are credible, free and well supported. BellSoft cannot differentiate merely by saying it has Java builds.
Its wedge is completeness at the awkward edges. Liberica covers antique versions and new architectures, JavaFX and embedded devices, native images and standard JVMs. Alpaquita gives the company a Linux layer it can patch and tune. Hardened Images push that control into supply-chain policy with signatures, SBOMs and remediation targets. BellSoft says customer fixes flow back to the wider OpenJDK community where applicable, turning support work into upstream maintenance rather than a permanent private fork.
The strongest proof of expertise sits upstream. BellSoft credits its engineers with work on AArch64 intrinsics, the Alpine Linux port and maintenance of the Arm port. It has participated in the Java Community Process Executive Committee and the GraalVM Advisory Board. Its VMware relationship put Liberica tooling into the Spring Native and Cloud Native Buildpacks story. In an infrastructure market, those affiliations function less like decorative badges than evidence that the vendor can debug the machinery it sells.
A culture of patches and particulars
BellSoft presents itself as an engineering-led, open-source company, and its public output supports the description. Release notes arrive across several Java trains at once. Security advisories sit beside benchmarks, installation guides and explanations of garbage collectors. The company says a bug fixed for one customer is corrected for OpenJDK users more broadly when the change belongs upstream. That is practical community stewardship: commercial urgency pays for work that can improve the shared codebase.
The tone is educational as much as promotional. Engineers publish tests, speak at Java conferences and record webinars on Kubernetes, Spring and native images. BellSoft's 2025 retrospective even lingered on a human artifact: veterans Aleksey, Valery and Peter still have commemorative plaques from the Java 1.0 era. It is a charmingly specific credential. Plenty of companies claim decades of experience; fewer can point to the office shelf where those decades are gathering dust.
That institutional memory can be an advantage and a trap. Deep Java fluency earns trust with conservative buyers, but a company built around one ecosystem must keep proving relevance as deployment practices change. BellSoft's move into multi-language hardened images suggests it understands the tension. Java remains the expertise that opens the door, while container security offers a room with more occupants.
The product is not Java itself. The product is fewer reasons to wake up the person responsible for Java.The BellSoft proposition, in plain English
From runtime vendor to supply-chain vendor
BellSoft's latest moves widen the addressable problem. Hardened Images, launched in 2025, cover Java and GraalVM Native Image but also Python, Go, C/C++ and Node.js. The Paketo builder released in July 2026 adds Ruby and lets teams produce application images without maintaining a hand-written Dockerfile. The company promises minimal components, cryptographic signatures, SBOMs and continuous vulnerability work. It also plainly notes that a hardened base does not absolve customers from configuring containers safely or rebuilding applications when patches arrive.
That realism suits the company. BellSoft is not trying to make Java fashionable. It is betting that decades of installed software, stricter security demands and cloud cost pressure will keep creating tedious problems worth paying specialists to solve. Java 26 sits on the download page beside Java 6. A 3.52 MB Linux root lives beside enterprise support. Old code runs on a newer JVM backend. The portfolio is a museum, workshop and loading dock at once.
For a developer, BellSoft offers free runtimes, containers and native-image tools to test today. For an enterprise, the useful question is narrower: how many vendors currently own the failure domain underneath a Java application? BellSoft's answer is one. Whether that becomes a broad platform business depends on execution, but the positioning is crisp. It does not need to own the glamorous part of software. It needs to make the boring part stay boring.