Open-Source Infrastructure Patents: Top Companies & Trends 2026
Open-Source Software Infrastructure Patents: Who Holds the Ground
29.6% sits with five companies. The top five assignees combined account for 1,298 of the 4,381 records in scope — a concentrated head with a long tail behind it. Filings rose from 299 in 2017 to a peak of 469 in 2021, then fell 28% to 336 by 2024 — the most recent year the data can be read as complete, since publication typically lags filing by around 18 months and 2025-2026 figures will still fill in.
- 1MICROSOFT TECHNOLOGY LICENSING LLC13.8%
- 2INTERNATIONAL BUSINESS MACHINE CORPORATION8.1%
- 3AMAZON TECH INC2.8%
- 4PALANTIR TECHNOLOGIES INC2.5%
- 5SALESFORCE INC2.5%
See the full open-source software infrastructure patent landscape analysis in Eureka
- The complete ranking, not just the top five
- Every IPC branch with its share of the corpus
- The most-cited records, and where claim space is still thin
Common questions on this landscape
Who holds the most patents in open-source software infrastructure?
One assignee leads clearly with 603 of the 4,381 records in scope, more than five times the fifth-ranked company’s 109. The top five combined hold 29.6% of all records, and the top ten hold 38.8%, so while there is a concentrated head, the majority of filing activity is spread across a long tail of smaller filers. The ranked list covers 100 companies total, not just the largest names, so smaller players with focused portfolios are also visible in the data.
Is patent filing in this space growing or shrinking?
Filing rose from 299 records in 2017 to a peak of 469 in 2021, then declined 28% to 336 by 2024, which is the most recent year that can be treated as complete. Publication typically lags filing by around 18 months, so 2025 and 2026 figures in any dataset will understate real activity and should not yet be read as a continued decline. The honest read is a post-peak pull-back through 2024, not a confirmed long-term slowdown.
What does US20170060575A1 actually cover?
It claims a repository control computer that checks source code out to a developer’s local machine, then repetitively checks in intermediate versions whenever a rule-defined condition is met, before a final check-in on the developer’s explicit command. The key mechanism is the automated, rule-triggered intermediate check-in step rather than manual version control. Anyone building automated commit or snapshot behaviour into a source-code-repository tool should read the claim scope closely rather than assuming manual check-in/check-out prior art clears it.
Disclaimer. This analysis is based on Patsnap Eureka data drawn from a limited snapshot of global patent records and is provided for general information and reference only. Patent data carries inherent limitations — recent filings are under-counted because of publication lag, counts may be on a record or family basis, classification and applicant-name data may contain errors or duplicates, and the underlying search query defines the scope shown — so the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.
Nothing here is an exhaustive prior-art, novelty, freedom-to-operate or validity search, nor does it constitute legal, financial or professional advice, and it should not be relied upon as such. Verify independently and review with qualified patent and legal professionals before acting on it.
Method: Filing trend and technology composition. Derived from a Patsnap search on Open-Source Software Infrastructure Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish. Every share divides by all records in scope. Data: Patsnap Eureka. See the full landscape report.