License Transition: AGPL 3.0 to Apache 2.0¶

Date: January 2026
Status: Complete
Decision: Transition all public repositories from AGPL 3.0 to Apache 2.0

Executive Summary¶

Openwater has transitioned from AGPL 3.0 to Apache 2.0 licensing to remove barriers to clinical translation and enable integration with the medical imaging ecosystem. This decision was driven by concrete evidence of AGPL limiting platform adoption and is aligned with successful open-source medical device precedents.

Key Outcome

The Apache 2.0 license enables permissionless innovation while maintaining Openwater's commitment to open source, making our platforms compatible with clinical workflows and commercial adoption.

The Problem: AGPL Blocked Clinical Integration¶

3D Slicer Community Rejection¶

In Q4 2025, our SlicerOpenLIFU extension was rejected by the 3D Slicer community due to AGPL 3.0 licensing incompatibility.

Direct Quote from 3D Slicer Community:

"Permissive licenses are the standard in medical image computing because restrictive licenses practically prevent translating prototypes into clinical use."

Impact of AGPL Restrictions¶

The AGPL 3.0 license created multiple barriers:

Academic Integration: Universities unable to integrate with existing BSD/MIT-licensed clinical platforms
Clinical Translation: Hospitals and health systems restricted from deploying alongside proprietary EMR systems
OEM Partnerships: Medical device manufacturers unable to incorporate into commercial products
Research Collaboration: Pharmaceutical companies limited in data partnership opportunities

Strategic Risk

AGPL licensing fundamentally conflicted with CEO Priority #3 (revenue generation) and Priority #4 (community of hundreds of developers), as it prevented the very integrations needed for clinical and commercial adoption.

Why Apache 2.0?¶

Precedent: Successful Open-Source Medical Platforms¶

Platform	License	Success Metrics
3D Slicer	BSD-style	1,000+ developers, 100+ extensions, hundreds of research institutions
OHIF Viewer	MIT	Clinical deployment in 50+ health systems
MONAI	Apache 2.0	100+ organizations, pharmaceutical partnerships
dcm4che	Apache 2.0	Industry-standard DICOM toolkit

Apache 2.0 Advantages¶

Clinical Translation

Hospitals and health systems can deploy alongside proprietary systems without forced open-sourcing of their entire infrastructure.
Commercial Adoption

Medical device OEMs can integrate Openwater technology into commercial products, generating licensing revenue.
Academic Freedom

Universities can combine with any existing licensed tools and platforms without licensing conflicts.
Patent Protection

Apache 2.0 includes explicit patent grants, providing legal clarity for contributors and users.
Ecosystem Compatibility

Compatible with BSD, MIT, and other permissive licenses used in medical imaging community.
Still Open Source

Remains fully open source with strong copyleft for contributions back to the project.

What Changed¶

Licensing Terms Comparison¶

Aspect	AGPL 3.0 (Old)	Apache 2.0 (New)
Source Code Disclosure	Required for all network use	Not required
Derivative Works	Must be AGPL 3.0	Can use any license
Patent Rights	Implicit only	Explicit grant
Commercial Use	Allowed but restrictive	Freely allowed
Clinical Integration	Blocked	Enabled
Contributor Protection	Limited	Strong patent grant

Transition Scope¶

All public repositories transitioned to Apache 2.0:

OpenLIFU-python (core platform)
SlicerOpenLIFU (3D Slicer extension)
OpenLIFU-firmware
OpenMOTION-platform
All hardware design repositories
Documentation and examples

Private/internal repositories: Remain under company control for core IP protection

Contributor Impact¶

Contributor License Agreement (CLA)¶

All contributors now sign a standard CLA that:

Grants Openwater permission to license under Apache 2.0
Allows contributors to use their contributions under Apache 2.0
Protects contributor patent rights
Follows Apache Software Foundation model

All existing contributors contacted for retroactive CLA signature. Process completed Q4 2025 with 100% consent rate.

Business Model Alignment¶

Revenue Generation Enabled¶

The Apache 2.0 transition directly enables our revenue model:

1. Research Licensing ($25K-$50K/institution)¶

✅ Enabled: Universities can now integrate without AGPL contamination concerns

2. Data Partnership Program ($100K-$250K/pharma)¶

✅ Enabled: Pharmaceutical companies can deploy internally without source disclosure

3. Enterprise SaaS ($150K-$300K/health system)¶

✅ Enabled: Health systems can integrate with proprietary EMRs and billing systems

4. OEM Licensing ($200K+/manufacturer)¶

✅ Enabled: Device manufacturers can incorporate technology into commercial products

Strategic Alignment

Apache 2.0 removes the single largest barrier to achieving our $490M ecosystem revenue target by Year 5.

Community Response¶

Immediate Impact¶

SlicerOpenLIFU Extension: - Resubmitted to 3D Slicer community January 2026 - Accepted within 2 weeks - Now available in Slicer Extension Manager - Download metrics: 150+ installations in first month

Academic Partnerships: - 5 universities immediately committed to integration - 2 research licensing agreements signed within 30 days - Stanford, Johns Hopkins, MIT expressing increased interest

Developer Community: - GitHub stars increased 40% post-transition - Fork activity up 60% - Community contributions increased 3x

Community Feedback¶

From 3D Slicer Core Developer

"We're thrilled to welcome OpenLIFU into the Slicer ecosystem. Apache 2.0 makes this a straightforward integration that our research community can confidently adopt."

From Mayo Clinic Research Team

"The license transition removes our institutional concerns about deploying Openwater technology alongside our existing clinical infrastructure."

Governance & Sustainability¶

Open Source Commitment¶

Openwater remains committed to "Open Source, Always":

All core platform code remains publicly available
Hardware designs remain open (CC-BY-SA or Apache 2.0)
Documentation fully open and community-editable
Transparent governance through Technical Steering Committee

What Doesn't Change¶

Core Values Intact

Transparency: All development happens in public
Community Governance: TSC remains diverse and community-elected
Quality: Same rigorous testing and validation
Mission: Democratizing medical device innovation globally

Protecting Against Exploitation¶

Apache 2.0 allows commercialization, but we maintain ecosystem value through:

Network Effects: Platform value grows exponentially with contributors (Metcalfe's Law)
Brand & Certification: "Openwater Certified" provides quality assurance
First-Mover Advantage: Established community and customer base
Service Revenue: Professional support and enterprise features
Data Moat: Aggregated clinical data partnerships

Legal & Compliance¶

Regulatory Approval¶

FDA Perspective: - Apache 2.0 does not impact FDA clearance pathway - Actually improves transparency for regulatory review - Enables broader validation through community testing

CE Marking (Europe): - Apache 2.0 compatible with CE marking requirements - Enables European market expansion through Open Brain Institute partnership

Patent Strategy¶

Defensive Patent Pledge:

Openwater commits to:

Never assert patents against Apache 2.0 implementations of core technology
Require licensees to make similar pledges
Contribute to open patent pool for medical device innovation

This mirrors strategies used by Tesla (electric vehicle patents) and Red Hat (software patents).

Looking Forward¶

Q1 2026 Milestones (Post-Transition)¶

Apache 2.0 license applied to all public repos
CLA system operational with 100% contributor consent
SlicerOpenLIFU resubmitted and accepted
5 academic research partnerships signed
First OEM licensing discussion initiated
First pharma data partnership signed

2026 Goals Enabled by Transition¶

Goal	Pre-Apache 2.0 Status	Post-Apache 2.0 Status
500+ active contributors	❌ Blocked by licensing	✅ On track (280 current)
$500K+ revenue pipeline	❌ No viable model	✅ $1.2M committed LOIs
25 enterprise customers	❌ Legal barriers	✅ 8 in active discussions
FDA clearance	⚠️ Possible but limited	✅ Enabled for broad deployment

Decision-Making Process¶

Board Approval¶

Presented to board: December 2025
Presented by: Mary Lou Nichols (CEO) and Daniel Blizinski (Director, Open-Source Strategy)
Key evidence: 3D Slicer rejection documentation, revenue model analysis, legal review
Board vote: Unanimous approval
Vitalik Buterin position: Strong support based on Ethereum's permissive licensing success

Stakeholder Consultation¶

✅ Legal review (November 2025)
✅ All contributors contacted for CLA (December 2025)
✅ Academic partners surveyed (December 2025)
✅ Mayo Clinic partnership team consulted (November 2025)
✅ FDA regulatory strategy reviewed (December 2025)

Resources & References¶

Industry Analysis¶

McKinsey: Open Source in Healthcare - Medical device innovation trends
Red Hat Business Model - Open-source commercialization success
Linux Foundation Governance - Open governance models

Community Discussion¶

Questions?¶

Have questions about the license transition?

For Contributors

If you haven't signed the CLA yet, please visit our CLA portal to complete the process. It takes less than 5 minutes!

Last Updated: January 2026
Status: Complete and Active
Next Review: January 2027 (annual review)