OpenNovations: Our Journey with Open Source and (Some) Lessons Learned

For over two decades, OpenNovations has embraced open source as a core philosophy in building innovative solutions for complex data challenges. From our early days in government projects to leading advancements in the pharmaceutical and healthcare sectors, we’ve continuously evolved how we approach open-source technologies. Here’s a look back at our journey and the lessons we’ve learned along the way.

Where It All Began

In 2002, OpenNovations was born out of a mission to simplify data integration and governance. Starting with projects for the Dutch government, we expanded into the pharmaceutical sector, applying these same principles to laboratory and clinical trial data.

By 2014, it became clear: we were solving the same problem repeatedly for different clients. This realization led us to create Aranei —a modular, open-source platform designed to streamline data management, governance, and analytics.

The Power and Pain of Open Source

Our commitment to open source and open standards runs deep:

• Flexibility & Collaboration: We integrate leading standards like HL7 FHIR, openEHR, and oneM2M, making it easier for organizations to adopt and innovate.
• Giving Back: Each year, we contribute 10% of our revenue to the open-source projects we rely on.
• Empowering Clients: While Aranei’s core generator engine is proprietary, the code and the tools it generates are open source, giving clients the freedom to adapt and extend.

But open source comes with its challenges:

1. Community Expectations: Open-source users often assume that because the tool is free, support is also free, which can strain resources. Clear boundaries, and clear communication, on what is supported—and what isn’t—are essential.
2. End User at the Table: The person implementing the software and providing feedback on bugs or suggesting improvements is often a system administrator or developer, not the actual End User.
3. Herding Cats: Open-source contributors often have diverse goals, so aligning efforts can feel like managing chaos. Regular community engagement, like quarterly calls and conferences, is key to enabling and nurturing collaboration.
4. Misaligned Perceptions: Many businesses prioritize problem-solving over caring that much about open-source ownership. While open-source reduces vendor lock-in concerns, it’s often not the selling point we initially expected it to be.

Some Lessons Learned

1. Start Small and Iterative: Building modular, reusable tools works better than trying to deliver comprehensive solutions upfront.
2. Open Source Isn’t Everything: Open source is a fantastic enabler, but it’s not a complete business model. Combining open source with proprietary offerings creates a sustainable balance.
3. Community is About Connection: Conferences like FOSDEM, DrupalCon Europe and openSUSE Conference (which we co-organized in 2015) helped us build relationships—not just contributors. Open source is about creating opportunities for connection, not control.
4. Feedback Loops Matter: Direct communication with users—both developers and end-users—is invaluable. Quarterly open calls with our clients help us keep improving.

The Road Ahead

Today, we’re focused on building bridges between innovation and adoption. Through sharing our experience and the mistakes we've made and recovered from, we aim to help other companies navigate the tricky waters of launching open-source products and building sustainable businesses.

Open source is not just a philosophy for us—it’s a way of working, innovating, and growing together. As we reflect on our journey, we remain committed to transparency, collaboration, and making meaningful impact!