Executive Summary
Some conferences are about product launches. Others are about roadmaps, buzzwords, or market positioning. OCX 2026 felt more grounded in real industry challenges and practical collaboration.
Held in Brussels, Belgium, the political and symbolic heart of Europe, this year’s Open Community Experience (OCX) felt like an event arriving at exactly the right moment. Across three days of sessions, conversations, and keynotes, one theme became clear: open source is no longer simply a development model. It is becoming strategic infrastructure.
That message surfaced through discussions on digital sovereignty, compliance readiness, Java modernization, AI governance, software-defined vehicles, embedded systems, and the future of developer tooling. Beyond the talk of technological advancements, what also stood out was the human energy of the event itself.
The locals were warm and welcoming. The Eclipse Foundation team carried the kind of hospitality that makes a big event feel personal. Speakers were thoughtful, approachable, and genuinely engaged. Even the setting helped. The Egg Brussels, with its open floor plan, natural flow, and calming design, created a space that encouraged conversation rather than chaos.
And perhaps Brussels wanted to participate too. Known for gray skies and cool drizzle, the city instead gave attendees sunshine and comfortable spring temperatures all week. There was something deeply fitting about discussing openness, trust, and collaboration while standing in one of Europe’s most important crossroads.
Brussels Was the Right Backdrop
Brussels is more than a host city. It is the capital of Belgium and the center of European governance. EU institutions, multinational organizations, policy leaders, and technology stakeholders all intersect there.
The relevance of the conference’s location cannot be overlooked. Many of the most important conversations at OCX were not just about code. They were about how code shapes economies, industries, regulation, trust, and sovereignty.
Hosting OCX in Brussels made the event feel grounded in reality. Open source is no longer outside the system. It is increasingly part of how systems get built.
Open Source as Strategic Sovereignty
One of the strongest themes of the week was digital sovereignty. In a standout keynote, Thibaut Kleiner of the European Commission described open source as deeply aligned with European values: sharing, transparency, and honest collaboration. He noted that Europe may not have the largest technology giants, but it has strong communities capable of building together through standards and open source.
That framing is increasingly important because sovereignty is no longer an abstract policy debate. It is becoming an operational concern. For years, these discussions often centered on semiconductor fabs, hyperscale cloud providers, or geopolitical strategy. At OCX, the conversation became more practical: who controls critical platforms, who can inspect software, who can sustain ecosystems over time, and who can collaborate without becoming locked into a single vendor or jurisdiction.
That shift matters for enterprises. Sovereignty is not just about replacing one vendor with another. It is about creating optionality, portability, and transparency in systems that organizations increasingly depend on. Open source does not solve every sovereignty challenge, but it gives buyers more leverage and more visibility than closed ecosystems often allow.
The Commission’s “open money, open source” philosophy, where publicly funded software should ideally become reusable public assets, was one of the more compelling policy messages of the event. It suggests a future where government technology investment creates reusable digital infrastructure rather than one-off procurements. If adopted more broadly, that approach could materially change how public-sector innovation is funded and scaled across Europe.
Data Spaces Move from Theory to Infrastructure
Dataspaces were another important signal. The conversation in Europe has evolved well beyond simple data sharing. The emerging model is trusted, governed, interoperable exchange across industries and institutions. That means enabling collaboration without surrendering control.
At OCX, dataspaces felt less like a policy concept and more like an implementation layer for the next generation of digital economies. The practical challenge many industries face is straightforward: valuable data exists across suppliers, governments, manufacturers, and institutions, but legal, technical, and governance barriers often prevent it from being used collaboratively.
Dataspaces attempt to solve that by combining policy enforcement, identity frameworks, metadata controls, and interoperable standards. In practice, that can support use cases such as supply chain coordination, industrial optimization, mobility ecosystems, sustainability reporting, and cross-border public services.
For developers and platform teams, that creates opportunities around APIs, federated identity, metadata governance, portability, and privacy-preserving collaboration. It also raises the importance of neutral technical foundations. This is where open source often wins: shared control planes tend to outperform closed silos when multiple stakeholders need to participate without ceding ownership.
If AI is fueled by data, then dataspaces may become one of the more important structural enablers for trusted enterprise AI in Europe.
CRA and Compliance Become Real Work
The Cyber Resilience Act (CRA) was not treated as distant legislation. It was treated as an operational reality.
Mike Milinkovich noted that if manufacturers have not yet begun preparing for CRA obligations, they are already late. He also emphasized the Eclipse Foundation’s Open Regulatory Compliance Working Group, where more than twenty open source foundations are collaborating on implementation guidance, FAQs, and training resources.
That may have been one of the most practically important developments of the week. Too often, compliance is framed as a legal or procurement issue that gets addressed near launch dates. CRA changes that dynamic by pushing accountability deeper into engineering processes, software supply chains, disclosure models, and lifecycle maintenance. In short, it moves compliance upstream.
OCX showed a healthier model for responding: community-driven readiness, shared standards, reusable guidance, and open collaboration around common burdens. That is far more efficient than every organization independently reinventing compliance workflows.
It also creates competitive separation. Vendors that can demonstrate secure development practices, transparent dependency management, and clear evidence trails will likely move faster through enterprise procurement cycles than those treating compliance as last-minute paperwork.
Java and Jakarta EE Quietly Remain Essential
Not every trend at a conference needs to be flashy. Java and Jakarta EE conversations at OCX reinforced something many enterprises already know: foundational platforms still matter. While headlines chase the newest frameworks and AI copilots, critical systems across banking, government, manufacturing, and telecom still run on mature, trusted stacks.
The tone around Java was less nostalgia and more modernization. That distinction is important. Mature platforms are often dismissed as legacy until organizations attempt to replace them and rediscover how much institutional knowledge, operational reliability, and ecosystem support they actually provide.
Stability, portability, and ecosystem depth still carry enormous value. That is especially relevant in Europe, where regulatory environments, long lifecycle systems, and operational resilience are often central buying criteria.
Jakarta EE’s continued evolution also reflects a broader truth about enterprise software: many organizations do not need constant reinvention. They need predictable modernization paths that allow them to adopt new capabilities without destabilizing critical workloads.
In that sense, Jakarta’s value proposition is not excitement. It is trust, continuity, and incremental progress. These are qualities that remain highly underrated in technology markets.
IoT, Embedded, ThreadX, and RISC-V Gain Momentum
Another major takeaway was how serious Eclipse has become in embedded and intelligent systems. Frederic Desbiens highlighted Eclipse ThreadX v6.5.0, describing it as the first and only community-led, permissively licensed open source RTOS that has been safety certified, with additional certifications planned.
He also pointed to expanding RISC-V momentum through Eclipse’s Open Hardware ecosystem and new processor initiatives. These are not niche conversations anymore. As AI extends to edge environments, industrial systems modernize, vehicles become software-defined, and robotics adoption grows, the software stack below the application layer becomes strategically important again. That means real-time operating systems, silicon architectures, firmware security, and deterministic performance are returning to the center of technology strategy.
ThreadX is notable because it combines open source governance with certification requirements that matter in automotive, industrial, and medical contexts. RISC-V is notable because it introduces more openness and flexibility at the processor layer. Together, they suggest a broader market shift: organizations increasingly want control not only over applications, but over the full technology stack beneath them.
Trust Was the Real Keyword of the Week
If one word tied everything together, it was trust. Trust in software supply chains. Trust in governance. Trust in compliance evidence. Trust in AI systems. Trust in infrastructure that society depends on.
One quote that captured this perfectly came from John Ellis: “Would you sleep under the software you built?”
That line lingered because it cuts through industry jargon. It reframes software quality in human terms. Not uptime percentages. Not sprint velocity. Not vanity metrics. Would you trust it with your safety? Your family? Your future?
That question becomes even more relevant as software expands into vehicles, hospitals, factories, utilities, public systems, and AI-driven decision environments. The more software touches the physical world, the less tolerance there will be for casual engineering practices. Trust, increasingly, will be earned through evidence, governance, and design discipline.
Final Thoughts
OCX 2026 was not the loudest event on the calendar, and that may be exactly why it mattered. There was substance here. Serious people discussing serious infrastructure issues with a collaborative spirit that felt increasingly rare in tech.
The Eclipse Foundation is positioning itself at an interesting intersection: open source governance, enterprise operations, regulatory readiness, industrial platforms, and next-generation developer ecosystems.
That combination matters more in 2026 than it did even two years ago because the market has changed. AI is accelerating faster than governance models. Governments are regulating more directly. Enterprises are reassessing supply chain concentration risk. Critical industries are becoming software-defined.
Those trends create demand for neutral institutions, open standards, and trusted operational ecosystems. Open source, in that context, moves from optional philosophy to strategic necessity. And in Brussels, under unusually sunny skies, that future felt a little closer.
SAP and S3NS Bring Sovereign Cloud ERP to France
OCX 2026 Wrap-Up: Open Source Finds Its Moment in the Heart of Europe
Eclipse ThreadX and RISC-V Advance the Open Embedded Stack
CRA Compliance and Trustable Software: What OCX 2026 Revealed
Jakarta EE AI Integration: What’s Coming in EE 12 and 13
