Research · Open interfaces
Businesses and institutions that kept an interface open
Shipping containers, the web, Linux, Creative Commons, and other widely used systems grew around interfaces that many organizations could adopt. Their builders used different business, legal, and governance arrangements. This page asks what stayed open, how the work was funded, and where control later returned.
Published 9 August 2026 · Updated 22 August 2026
A separate question from market disruption
Market strategy
A company may win customers by lowering costs, improving a product, or reaching a market that established firms overlooked. It may protect that position through patents, proprietary data, distribution, or switching costs. Those choices vary by company, and market disruption alone says little about who will control a successful interface.
Open-interface test
This page applies another test. After a project succeeds, can customers, competitors, or contributors implement the interface, verify important claims, and leave with their work? A profitable company can meet those conditions. A nonprofit can fail them.
The two questions can overlap. This page focuses on the end state: who controls the interface, what a participant can take when leaving, and whether outsiders can verify the rules that matter.
What counts as a win
- Published interface: other organizations can implement the standard or protocol under clear terms and without discretionary approval.
- Independent verification: participants can check the facts that determine access, payment, or compliance.
- Practical adoption: joining fits the budgets, contracts, procurement rules, and deadlines facing the decision-maker.
- Portability: customers and contributors can leave with usable data, reputation, rights, and records.
- Explicit control: the governance documents state who can change the rules, inspect decisions, hear appeals, and revoke access.
Past examples worth studying
These examples are not all companies. They include standards, licenses, nonprofits, and member-governed networks. Each opened one layer of a system; several later developed new points of control. The useful questions are which interface opened, who paid for the work, and what became difficult to move later.
Shared infrastructure
Shipping container standardization
Malcom McLean invested in ships, containers, chassis, terminals, and schedules. Later ISO standards specified dimensions and fittings that independent carriers and equipment makers could implement. Freight could move between ships, trucks, and terminals without redesigning the equipment at every handoff. McLean earned through Sea-Land rather than a permanent license on every standardized container.
Sources: Levinson, The Box (Princeton UP); League profile with primary sources.
Open protocols
TCP/IP and the open web
TCP/IP and web standards let networks, servers, browsers, and publishers interoperate without approval from one vendor. Companies built proprietary products on top of those protocols. Later platforms concentrated user identity, audience relationships, and data at the application layer, showing that an open protocol does not prevent control from returning higher in the system.
Sources: Cerf & Kahn, “A Protocol for Packet Network Intercommunication” (IEEE, 1974); Internet Society, “Brief History of the Internet”; League profile: Berners-Lee.
Software that stays open
Linux and copyleft open source
GNU GPLv2 allows commercial use and distribution of the Linux kernel while requiring distributors of covered modified versions to provide corresponding source code under the license’s terms. Companies compete through distributions, hardware, hosting, support, and cloud services built on the shared kernel.
Sources: GNU GPLv2 (the kernel’s license); League profile: Torvalds.
Shared knowledge
Wikipedia
Wikipedia opened encyclopedia production to a large contributor base through public revision histories and editing rules. The cited 2005 Nature study compared science entries with Encyclopaedia Britannica and found a similar number of serious errors in the sampled articles. That study does not establish Wikipedia’s accuracy in every field, and its editing and governance remain contested.
Source: Giles, “Internet encyclopaedias go head to head” (Nature, 2005).
Portable rights
Creative Commons
Creative Commons licenses give creators a standard way to grant permissions for sharing and reuse. A creator chooses the license, and a user can read the permissions without negotiating a custom agreement or accepting a platform’s private contract.
Sources: Creative Commons, mission and license suite; League profile with primary sources.
Cooperative infrastructure
Early Visa (Dee Hock)
Visa’s early network was owned by member banks. Competing banks used common operating rules and payment infrastructure while participating in the network’s governance. Visa Inc. later became a public shareholder corporation, so the founding structure and the current company should be evaluated separately.
Sources: Visa Inc. Form 10-Q, quarter ended March 31, 2008 (SEC); League profile: Hock, with primary sources.
Rules made by users
Ostrom-style resource institutions
Elinor Ostrom documented common-pool resources governed by users through local rules, monitoring, and graduated sanctions. Her research shows that such arrangements can work under identifiable conditions. It does not show that every shared resource can be governed the same way.
Sources: Ostrom, Governing the Commons (Cambridge UP, 1990); 2009 Nobel press release.
Portable work records
Open standards for documents, mail, and syndication
Email, HTML, and Atom define formats that multiple vendors can implement. They make messages, documents, and feeds portable at the protocol layer. They do not automatically make a platform-specific follower list, ranking, or reputation portable.
Sources: RFC 5322 (Internet Message Format); WHATWG HTML Living Standard; RFC 4287 (Atom).
A proposed launcher partnership
Further development · 14 September 2026. How to defeat Moloch: an investment strategy develops the global selection criteria and order of investment. It also broadens the accountability approach: ownership and contractual requirements can constrain abuses of power while preserving the venture’s ability to succeed.
Accelerators commonly help companies with product development, hiring, fundraising, and distribution. A League launcher partnership would add tests for portability, governance, and independent verification. It remains a proposal.
The current draft asks:
- Which rule, ownership right, switching cost, or information gap keeps people in the current system?
- Can customers or counterparties leave with their work, reputation, and options intact?
- Do financing, board, and governance terms preserve stated commitments to safety, provenance, and rights through later rounds?
- If the venture operates inside a race, can independent audits or public measures show whether participants follow agreed limits? Changing the incentive to break those limits may still require regulators, insurers, or treaty-makers, as the three-reasons note explains.
- Can customers adopt the product under the budgets, contracts, procurement rules, and distribution channels they face now?
The proposal combines venture support with legal or technical standards and independent verification. Its scope, funding, governance, and services remain to be defined.
A project can remove one source of lock-in and create another. The tests above put exit rights, auditability, and governance terms into the design before growth makes them expensive to change.
Live League example
x4me2 is a current League prototype. It helps people recover reviews they wrote, prove authorship, and host the reviews independently. The project is working toward direct machine payments when AI systems use those reviews. Its relevance here is portability: the author’s work remains usable outside the platform where it was written.
This page is a working research note. Useful suggestions include stronger historical examples, failed open interfaces, and companies that began with easy exit and later restricted it.