You think you know who runs Java. Oracle, obviously. Maybe Red Hat. Maybe Amazon now. You’d be wrong about the most interesting player.
SAP has been quietly shaping the OpenJDK for 15 straight years. Not as a marketing exercise. Not as a checkbox on a corporate social responsibility slide. As a sustained, deep-engineering commitment that has made it one of the most influential forces in the Java ecosystem—while almost nobody outside the inner circle noticed.
A company famous for lock-in is building the foundation that lets everyone walk free. That’s not irony. That’s strategy.
Here’s the paradox that should make you rethink everything you assume about enterprise open source. SAP is a proprietary software giant. Its entire business model rests on customers staying inside its walls. And yet, for a decade and a half, SAP engineers have been committing code to the most critical open-source runtime on Earth—a runtime that empowers its competitors, reduces its lock-in advantages, and gives customers one less reason to stay.
Why? Because SAP understood something most companies still don’t: controlling the platform your applications run on is worth far more than controlling the applications themselves.
When SAP contributes to OpenJDK, it isn’t being generous. It’s ensuring the runtime evolves in directions that matter to enterprise workloads—the exact workloads SAP’s customers depend on. Every garbage collector improvement, every memory management fix, every performance patch that SAP pushes upstream shapes the Java that everyone uses. Including competitors.
You don’t need to own the river if you can shape where it flows.
Most observers still see SAP as a passive consumer of Java. A giant that builds on top of the platform but doesn’t really move it. That’s a fundamental misread. SAP’s OpenJDK team has been one of the quiet pillars holding up the entire project—contributing maintainers, fixing deep bugs, and participating in the governance structures that decide what gets into the JDK and what doesn’t.
This matters for you if you’re a Java developer or an enterprise architect making build-vs-buy decisions. The health of OpenJDK isn’t guaranteed by some abstract community spirit. It’s maintained by real companies with real engineering budgets. Knowing who those companies are—and why they’re investing—tells you whether your platform has a future or a cliff.
SAP’s 15-year bet says the future is solid. Not because SAP is altruistic, but because SAP is smart enough to know that the runtime is the battlefield, and they intend to be on the winning side of it.
The companies that shape infrastructure don’t need to shout about it. They just need to keep showing up—year after year, commit after commit—until the platform bends toward them.
So the next time someone tells you open source is about generosity, point them to SAP. It’s about something far more durable: the recognition that the most powerful position in technology isn’t owning the product. It’s owning the ground the product stands on.
FAQ
Q: If SAP is so influential in OpenJDK, why hasn't anyone heard about it?
A: Because SAP doesn't need the press. Influence over infrastructure is exercised through commits and maintainer roles, not press releases. The quiet contributors are the ones who actually move the platform.
Q: What does this mean for my build-vs-buy decisions in enterprise Java?
A: It means OpenJDK isn't going anywhere. With companies like SAP, Oracle, and Red Hat all financially invested in its survival, the platform has deep structural support. You can build on it with confidence that the runtime will be maintained for decades.
Q: Isn't SAP just contributing to open source for good PR?
A: No. PR-driven open source contributions are shallow, time-limited, and abandoned when marketing moves on. 15 years of sustained engineering commitment is a strategic investment in platform control, not a brand campaign. SAP is shaping the runtime its competitors rely on—that's power, not charity.