License Zero is a game plan for financially sustaining independent work on open software. License Zero lets you make a new deal with users of your software:
Use my software freely for open source or noncommercial work. Otherwise, buy a license online to support me.
It’s the model of GitHub, Travis CI, and other leading developer services, adapted for independent library, framework, and tools developers. Finally.
This model also makes it easy to support developers creating open software you use and rely on at work. License Zero is not a donation platform or a backer-rewards market. If other developers’ work helps you do your job better or more efficiently, supporting them through License Zero ought to be a reimbursable expense.
This is a guide to License Zero, and the project’s primary documentation for developers. If you’re interested in using License Zero, either to support your work or to support others, read this guide. If you find errors or ways to improve it, send a pull request.
This guide describes what License Zero is, and how it works. It is not a substitute for legal advice about whether a particular license fits your needs or work. The License Zero terms of service apply to this guide, too.
def licensing(user, contribution): # See "Public Licenses" below. if user.meets_conditions_of(contribution.public_license): contribution.public_license.permit(user) else: # See "Private Licenses" below. private_license = user.private_license_for(contribution) if ( private_license is not None and user.meets_conditions_of(private_license) ): private_license.permit(user) # See "Waivers" below. else: waiver = user.waiver_for(contribution) if ( waiver is not None and not waiver.expired ): waiver.permit(user) # See "licensezero.com" below. else: license_zero.buy_private_license(user, contribution)
As an independent software developer, you control who can use your software, and under what terms. License Zero
LICENSE terms give everyone broad permission to use and build with your software, as long as they either limit commercial use or share work they build on yours back as open source, depending on your choice of two
LICENSE options. Users who can’t meet those conditions need private licenses.
licensezero.com can sell private licenses on your behalf. A command line interface makes it easy for users to buy all the private licenses they need for a project at once, with a single credit card transaction. Stripe processes payments directly to an account in your name. The same command line interface makes it easy for you to sign up, start offering private licenses for sale, and set pricing.
This “dual licensing” model is not new. MySQL pioneered it decades ago, and important projects like Qt and MongoDB continue it, successfully, today. License Zero evolves the dual licensing model by making it useful for more kinds of software, and by making it practical for independent developers who can’t or don’t want to set up companies.
License Zero starts where you exercise your power as the owner of intellectual property in your work: in your project’s
LICENSE file. You might currently use The MIT License, a BSD license, or a similar open source license there now. License Zero offers you two alternatives:
The Prosperity Public License (Prosperity) works a bit like a Creative Commons NonCommercial license, but for software. Prosperity gives everyone broad permission to use your software, but limits commercial use to a short trial period of 32 days. When a commercial user’s trial runs out, they need to buy a private license or stop using your software.
The Parity Public License (Parity) works a bit like AGPL, but requires users to release more of their own code, in more situations. Parity requires users who change, build on, or use your work to create software to release that software as open source, too. If users can’t or won’t release their work, they need to buy a private license that allows use without sharing back.
LICENSE options are short and readable. You should read them.
LICENSE options aren’t just worded differently. They achieve different results. Abstracting them a bit:
def prosperity_license: if commercial_user: if within_trial_period: return 'free to use' else: return 'need to buy a private license' else: return 'free to use' def parity_license: if building_software: if release_software_as_open_source: return 'free to use' else: return 'need to buy a private license' else: return 'free to use'
Consider a few user scenarios, and how they play out under different
A developer employed at a for-profit company wants to use your library in their company’s closed-source, proprietary web app. They will not release their web app as open source.
If you license the library under The Prosperity Public License, the developer can only use the library for 32 days. Then they need to buy a private license.
If you license the library under The Parity Public License, the developer needs to buy a private license to use your library in their web app at all. They can’t use the library under its public license, because they won’t meet the condition of releasing their web app as open source.
A developer employed at a for-profit company wants to use your library in the data synchronization software their company ships with voice recorders. They plan to release the sync software as open source.
If you license the library under The Prosperity Public License, the developer can only use the library for 32 days. Then they need to buy a private license. The private license allows the developer to “sublicense”, or pass down, their permission to use the library for commercial purposes to their company and its customers.
If you license the library under The Parity Public License, the developer can use the library in their sync software under the public license, as long as they actually release the sync software as open source. The company’s customers can use the sync software, with the library, for any purpose.
A developer employed at a for-profit company wants to use your video player application to show commercials in their office lobby.
If your license the application under The Prosperity Public License, the developer can only use the application for 32 days. Then they need to buy a private license.
If you license the application under The Parity Public License, the developer is free to use the application for as long as they like under the public license.
The Prosperity Public License allows users to build and use closed and proprietary software with your work, as long they use it for noncommercial purposes. The Parity Public License allows users to build and use only open source software with your work, even for very profit-driven purposes. Many noncommercial software users are happy to make their work open source, but many make closed software, too. Many for-profit companies make closed software, but many also make and release open source software, too.
License Zero was inspired by imbalances in the relationship between open source developers and users. Both
LICENSE options represent new deals between developers and users, designed to redress that imbalance. Whether Prosperity or Parity works best depends on how others will use your project, and your goals. Before you pick terms for
LICENSE, make a few notes about how you think users will use and build on your software. Treat those use scenarios as your licensing test suite. Run your test suite examples through the rules in Prosperity and Parity, to see how they will play out, and compare the results. Which results do you prefer?
A key consideration for applications is whether you want to require users to buy private licenses for commercial use. Say you write an image manipulation program. Parity would allow anyone to use your program for any purpose, including commercial purposes, so long as they don’t modify your program or build on it to make closed source. That’s unlikely for an image manipulation program, as compared to a software library or a software development tool. On the other hand, Prosperity would require users to buy a private license after 32 days.
The differences between the public licenses, especially on commercial use, reflect some political differences that you should be aware of.
Prosperity is not an “open source” or “free software” license as nearly any savvy community members define those terms, because it discriminates against commercial use. Source for Prosperity software can still be published and developed online, using many popular services like GitHub and npm. But many in those communities will not accept it as part of their movements, and perhaps criticize you for referring to it as “open source” or “free software”.
Parity, on the other hand, was written to conform to the Open Source Definition, as was its predecessor, a license called The License Zero Reciprocal Public License. The predecessor license was proposed to the Open Source Initiative’s license-review mailing list for approval in September of 2017. Extensive debate eventually focused on the fact that L0‑R goes further than existing licenses in when and what code it requires users to release. When it became clear that debate would not resolve favorably, if at all, Parity was born, as a fork of L0‑R, eschewing the constraints of the OSI process. It’s the author’s position that Parity conforms to the Open Source Definition as written, resembles licenses that OSI has approved in the past, and that software under Parity is therefore open source software. Others will disagree.
Parity is probably not a “free software” license as defined by the Free Software Foundation. FSF’s definition of free software requires granting freedoms to run, copy, distribute, study, change and improve software. It also recognizes that some conditions on those freedoms can enhance software freedom overall by ensuring that others receive source code and freedom to work with it, which is exactly the approach Parity takes. However, FSF’s definition of free software admits only conditions on the freedom to share modified versions with others, along the lines of the GPL licenses that FSF has published, and not conditions on other freedoms. That partially explains why the Open Source Initiative approved RPL‑1.5, a thematic predecessor of Parity, while FSF considers RPL non-free.
In the end, your software is yours to license. These politics may or may not matter to you, and they may or may not matter to your users or potential users.
Users who can’t meet the conditions of the public
LICENSE terms can buy a private license that allows them to use the work without meeting those conditions. License Zero publishes a form private license, and sells private licenses to users on developers’ behalf.
Each private license grants the buyer broad permission under copyright and patent law to use contributions to an open software project, in language a bit more like what a company legal department would expect. Otherwise, the legal effect is much like that of a permissive public license, like MIT or BSD, except the private license applies only to the person who bought it, from the date they bought it.
Private licenses give the buyer limited ability to pass their licenses on, or sublicense, others. Generally speaking, buyers can pass their licenses on to others if they build software with significant additional functionality over and above that of the License Zero code they use. They can pass on only the right to use the License Zero as part of the new program they’ve created, and to maintain it. They can’t pass on their license to make changes or build other programs with the software. In other words, buyers can sublicense the “user” parts of their private licenses, but not the “developer” parts of their private licenses. Other developers who want to develop new programs, commercially or as closed source, need to buy their own private licenses.
Private licenses last forever, and cover the set of contributions to an open software project that a developer tags with the same identifier listed in the private license. To use an open software project without following the rules of its public licenses, users need other licenses, like private licenses from licensezero.com, that cover every contribution to the project.
Once a developer publishes contributions to a project tagged with a particular identifier, those contributions become forever linked to that identifier. Developers can’t take those contributions back, so that private licenses sold for for that identifier no longer cover them. That means users can buy the private licenses required for a particular version of a project, and rest assured that they will always have the rights they need for that version.
Apart from this rule against taking contributions back, developers retain total control over what work is covered by a particular identifier. If a developer embarks on a rewrite, or adds significant new functionality in a major release, they can create a new identifier for that new work, and charge for it separately. If the new work builds on the old work, users will need private licenses for both identifiers to use the combined project.
In general, there is only one situation where License Zero ever signs any agreement that requires a developer to do work in the future: When a customer sponsors relicensing of a set of contributions, the developer must implement the change, according to instructions in the relicense agreement. Otherwise, License Zero terms only cover work that has already been done. Developers can choose to make additional contributions tagged with old identifiers. But they can always choose to use a new identifier instead.
Many companies sell proprietary software on subscription. Customers pay a license fee, usually monthly or annually, as long as they use the software. Subscriptions create recurring revenue for sellers. Customers continue to pay, month after month, year after year, even if the seller doesn’t release any changes to the software.
License Zero does not support subscriptions. Customers pay for private licenses just once, and those licenses last forever. That design decisions reflects the complexity of subscription licensing, on the one hand, and License Zero’s overarching goal of zero friction, on the other.
Subscription license sellers have to charge their customers repeatedly. Each payment can go wrong. Payment methods expire. Delays and errors abound. Customers go out of business, or decide not to renew. To cope, sellers pay payment processing and invoice companies, hire billing managers, and even sell debts to collection agencies.
From the customer point of view, sellers go out of business, retire products and services, or let contracts expire to renegotiate price. To avoid getting stranded, customers demand source code escrow, transition services, and other protections against getting stuck without critical software. They push for long price commitments, or rules limiting how much prices can go up each year.
All of that complicates subscription license agreements. But even the best subscription license agreement eventually ends. When a subscription ends, for whatever reason, the customer’s license for the software ends with it. Looking at an old proprietary software license, it’s rarely clear if the license is still good. Did one side or the other stop it from renewing? Did the payment for this year’s renewal actually go through?
That uncertainty makes anything like a single form for private license, or a single command to find what licenses are missing, impossible. One-time payments and forever licenses are simpler, both at the time of sale and over the long term.
That doesn’t mean developers can’t use License Zero to get paid for work over time. As mentioned above, developers have complete control over whether to make new contributions under an existing licensing identifier, or create a new one. Developers can create new identifiers for each new major release of a project, or even for each new month. It’s up to developers to communicate those choices to users, if they like, so users know what to expect. As a baseline, License Zero’s licenses and terms only grant licenses for the software developers have already made, in the past. But licenses for past work don’t expire in the future.
Waivers work a bit like freebie private licenses. Developers can use the command line interface to generate signed waivers, for specific people, that let them out of
LICENSE conditions limiting commercial use or require open source release. Developers can generate waivers that last only a set number of days, or that last forever. The command line interface treats waivers just like private licenses for purposes of figuring out which private licenses a user is missing for a project.
You might like to issue waivers to reward other contributors to your project who make their work available under a permissive license, for parallel licensing, extend the free trial period for projects under Prosperity, or to resolve a question about whether a particular use will trigger the commercial-use time limit. It’s entirely up to you.
License Zero allows developers to set a price for changing the
LICENSE terms for their contributions to a project to those of The Charity Public License (Charity). This is called “relicensing”.
Charity is a highly permissive open source software license, much like The MIT License and the two-clause BSD license, but easier to read and more legally complete. It gives everyone who receives a copy of your software permission under copyright and patent law to use it and built with it in any way they like, as long as they preserve your license information in copies they give to others and refrain from suing users of your project for violating patents on it.
Relicensing contributions to a project under Charity removes any reason for users to buy private licenses for those contributions through licensezero.com. Under the agency terms that you must agree to in order to offer private licenses through License Zero, you must retract an identifier from sale through the API if you relicense it.
The relicense agreement sets out the terms of agreement between a contributor and a sponsor paying to relicense their contributions. When a sponsor pays the price, Artless Devices signs the relicense agreement with the sponsor on the contributor’s behalf, as their agent.
The contributor’s obligations are set out in the “Relicensing” section of the agreement. Once the contributor receives payment, they’re obligated to take the steps listed there.
licensezero.com is a website and API for selling private licenses, closing relicense deals, and generating waivers.
You can think of licensezero.com as a kind of Internet vending machine. As a contributor, you can make a deal with the operator of the vending machine to stock it with private licenses and relicense deals for sale. The vending machine then handles taking payment and spitting out licenses on your behalf.
You could also think of licensezero.com as a kind of e-commerce platform service-izing the back-office operations of a dual licensing business: negotiation, communication, payment processing, records management. Rather than start a company and hire people to handle those tasks, or take time away from development to do them yourself, you can use licensezero.com to run your licensing business 24/7. It works just a well for expensive licenses priced in the thousands of dollars and relatively cheap licenses costing just a few bucks.
You can create an account to sell private licenses through License Zero by linking a standard Stripe payment processing account, via Stripe Connect. Stripe Connect enables licensezero.com to connect its Stripe account to yours, then generate access keys to initiate payment processing requests directly on your account. Stripe assesses its fee, and any commission for licensezero.com, on the transaction.
licensezero.com generates unique identifiers for each developer and each set of contributions. The identifiers are version 4 UUIDs like:
When you connect a Stripe account to licensezero.com, the site creates a unique UUID for you, as well as a NaCl-style Ed25519 cryptographic signing keypair. licensezero.com signs most kind of licensing information, from package metadata to
LICENSE files, private licenses, waivers, and relicensing agreements, with the keypair created for your account, as well as its own keypair.
licensezero.com publishes the public signing key generated for you on your web store pages, and via the API. Users can leverage the command line interface to verify signatures on private licenses and other documents against the public key.
licensezero.com will not share the secret signing key generated for you with you or anyone else. But using the API, through the command line interface, you can have licensezero.com sign waivers and package metadata using the key, on your behalf.
licensezero.com serves a page with information and purchase forms for each identifier. For example:
The URL pattern is:
licensezero.com serves SVG graphics with private-license pricing information that you can include in your project’s
README file or other documentation. For example:
The URL pattern is:
The Markdown syntax is:
Artless Devices LLC is a California limited liability company. It serves as the legal counterpart to licensezero.com. As a developer offering private licenses for sale through licensezero.com, you will have three legal relationships with Artless Devices:
To use licensezero.com and its API, you must agree to terms of service with Artless Devices. The terms were written to be read, and you should read them. They set important rules about responsibility and liability, and make very explicit that Artless Devices isn’t going to provide, or be responsible for, any legal advice about whether License Zero is right for you or your work.
To offer private licenses for sale through licensezero.com, you agree to the agency terms with Artless Devices. You should definitely read that agreement, and again, it was written to be read, not to glaze your eyes over. But there are a few especially important aspects, from Artless Devices’ point of view.
First and foremost, you appoint Artless Devices as your agent to sign license agreements, waivers, and relicense agreements on your behalf. That means that Artless Devices can do the deals you authorize through the API, via licensezero.com, with the same effect as if you’d signed them yourself.
Second, Artless Devices earns commission on private license sales. The amount is set out in the agency terms when you offer your work for private licensing.
Third, you guarantee that you have the rights to offer the software you offer to license through License Zero, and to keep your projects’ metadata in line with what the command line interface generates. The guarantee helps protect Artless Devices from those trying to take license fees for others’ work. Your promise about metadata helps ensure that the command line interface works as intended for users buying licenses.
Fourth, the relationship isn’t exclusive, and with the exception of work for which you lock availability, either side can end it at any time. You can sell private licenses through other services, or on your own.
Finally, neither the terms of service nor the agency terms change ownership of any intellectual property in your work. You own your rights, and you keep them. Artless Devices doesn’t receive a license from you. Rather, you license users and agree to relicense your work directly. Artless Devices merely acts as your agent, signing on your behalf, as you’ve directed via the API.
Artless Devices owns and licenses the intellectual property in the command line interface that you will use to register and offer licenses for sale, as well as forms and other software tools published online.
The command line interface is the primary way developers interact with licensezero.com.
Install the CLI by downloading a prebuilt binary for your platform and installing in your
To use the CLI as a contributor, user, or both, first run
licensezero identify \ --name "Jane Dev" \ --jurisdiction "US-CA" \ --email "email@example.com"
Provide your exact legal name, an ISO 3166-2 code for your tax jurisdiction, and your e-mail address.
A few example tax jurisdictions:
BR-SPfor São Paulo, Brazil
DE-HHfor Hamburg, Germany
GB-LNDfor the City of London
JP-13for Tokyo, Japan
NG-LAfor Lagos, Nigeria
US-TXfor Texas, United States
To offer private licenses for sale via licensezero.com, you need to identify yourself with
licensezero identify, then register as a licensor and connect a standard Stripe account:
licensezero register will open a page in your browser where you can log into Stripe, or create an account and connect it. Once you’ve connected a Stripe account, licensezero.com will provide you a licensor identifier and an access token that you can use to create a licensor profile:
licensezero token --licensor $YOU_NEW_ID
The command will then prompt for your access token, and save it for future use.
To offer private licenses:
licensezero offer \ --price 300 \ --no-relicense \ --homepage "http://example.com" \ --description "an example project"
If you like, you can also set a relicensing price:
licensezero offer \ --price 300 \ --relicense 200000 \ --homepage "http://example.com" \ --description "an example project"
You can run the
reprice subcommand to update pricing.
Once you’ve offered your work, use the CLI to set licensing metadata and
cd your-package licensezero license --id $ID --prosperity # or licensezero license --id $ID --parity git add licensezero.json LICENSE git commit -m "License Zero" git push
These commands will write cryptographically signed
licensezero.json files. The data in
licensezero.json allow the CLI to identify the package for users quoting and buying private licenses.
By default, you can change pricing for private licenses at any time. You could offer private licenses for $5 today, and $5,000 tomorrow.
In order to provide a publicly verifiable guarantee of license availability and pricing, either to users or others who want to build on your work, you can lock private-license pricing for your work to no more than the current price for a term of days, months, or even years.
licensezero lock --id $ID --unlock $YOUR_UNLOCK_DATE
The unlock date must be a date at least seven calendar days in the future.
Locking pricing prevents you from increasing pricing or withdrawing your offer of private licenses. For specifics, see the agency terms.
Please note that locks are irrevocable. Artless Devices will not unlock early under any circumstances.
To generate a waiver, provide a legal name, a jurisdiction code, and either a term in calendar days or
licensezero waive \ --id $ID \ --beneficiary "Eve Able" \ --jurisdiction "US-NY" \ --days 90 \ > waiver.json
You can also issue waivers that don’t expire:
licensezero waive \ --id $ID \ --beneficiary "Eve Able" \ --jurisdiction "US-NY" \ --forever \ > waiver.json
Unless you’ve locked pricing, you can stop offering private licenses through licensezero.com at any time:
licensezero retract --id $ID
Please note that under the agency terms, Artless Devices can complete private license and relicensing transactions that began before you retracted the project, but can’t start new transactions.
You can generate quotes for License Zero software within the
node_modules directories of your projects:
cd your-project licensezero quote
To buy missing licenses for dependencies of a project:
cd you-project licensezero buy
licensezero buy will open a webpage in your browser listing the licenses to buy and taking credit card payment. On successful purchase, licensezero.com will provide the address of a purchase bundle that you can use to import all of the licenses you’ve just purchased at once:
licensezero import --bundle $URL
To import a license you bought on licensezero.com, or a waiver you received from a contributor:
licensezero import license.json licensezero import waiver.json
To sponsor relicensing of a project onto permissive terms:
licensezero sponsor --id $ID
The command will open a payment page in your web browser.
To back up all your License Zero data, including your identity, access token, waivers, and licenses:
The command will create a tar archive in your current directory.
Any open developer can choose one of the public license options, add its text to
LICENSE, offer private licenses through the API, and link to their web store page in
README or on a website. Users can buy private licenses directly from the web store page, and download their signed license file. But the process becomes much simpler—much closer to zero friction, for both contributors and users—when the command line interface can find, read, and write package metadata showing which packages correspond to which licensezero.com IDs.
The command line interface finds package metadata by recursing the current working directory, as well as paths provided by queries to dependency-management tools, like
bundler show for RubyGems. When the command line interface finds a
licensezero.json file, it inventories the packages listed within it. It then looks for package-manager metadata files, like
pom.xml, and tries to query them for package scope, name, and version information.
LANGUAGES file in the CLI repository describes current language and packaging support. If you’re interested in expanding first-class tooling support to your language or package format of choice, reach out in the GitHub repository for the Go port of the CLI. Even if you can’t contribute code, pointers to documentation, examples of conventions, and answers to questions will be very helpful.
As a independent software maintainer, you can license your work under both a public
LICENSE terms and private licenses at the same time because you own the intellectual property in your work that others needs licenses for. In other words, you can dual license your work because you own it.
When others contribute to your work, they will own the intellectual property in their contributions, not you. As a result, users of your combined work will need licenses from you and from other contributors. There are two straightforward ways to achieve that.
You can choose to take contributions to your project only from those who license their contributions under permissive open source terms. For example, you might license your contributions to a project under Parity terms, but ask contributors to license their work under Charity, and append the text of that license to your project’s
LICENSE file with a note that others’ contributions come under that license.
Users of the combined project would then receive a license from you on Parity terms, for your contributions, and licenses from other contributors on the terms of Charity, for their contributions. Would-be users who won’t abide by the open source release conditions of your license can still buy a private license from you, for your contributions. The private license for your work, plus the permissive license for others’ contributions, cover all contributions.
In that kind of situation, you can sell private licenses for your contributions to the project, but others cannot. Perhaps that feels completely fair. If it doesn’t, you may like to offer special credit, payment, or a free waiver to contributors, to convince them to license their contributions under permissive terms.
License Zero also supports projects that require multiple private licenses, for contributions from different developers. If you publish contributions under The Parity Public License, and another developer forks, licensing their own work under The Parity Public License, too, they can append
licensezero.json metadata for a separate License Zero identifier. Users who run the command line interface will see that they need a private license from each of you to use the project as a whole. The same could happen with two contributors using The Prosperity Public License, or contributors using a mix of
Note that as a contributor, you control pricing only for your own contributions, not anyone else’s contributions, even if their work builds on yours. Contributors building on top of work you license under The Prosperity Public License will need to purchase private licenses from you to use and build on your work for the purpose of making money through licensezero.com, but otherwise, licensezero.com doesn’t say anything about any relationship between you.
Packages, tools, and projects depend on other packages, tools, and projects in turn. These relationships create webs of dependencies, or dependency graphs, within software projects.
Users need licenses for all intellectual property within their software projects, including its dependencies. And they must follow the rules of each of those licenses. That means each project tree has not just a dependency graph, but a license graph, as well. The License Zero command line interface traverses the license graph automatically, seeking out License Zero packages.
Consider this dependency graph:
Package A depends on Package B and Package C. Package C depends on Package D in turn.
When all contributions to each package in the graph are licensed under the same terms, users must follow the rules of that license for all code in the graph:
In this case, all the packages in the dependency graph are licensed under Parity terms. Parity allows this, as long as source code for all the packages gets released, and each package preserves the license terms and notices of its dependencies.
However, the licenses for packages in a dependency graph need not be the same:
A user of package A needs to follow the rules of both Charity and Prosperity, in order to use package A. That means both limiting commercial use to 32 days and releasing source code for software built with package D, including for software built with package C or Package A.
Note that the authors of package A and package C are free to license work on their own packages under MIT and Charity terms, respectively. The Parity license of package D requires release of source code and licensing on terms at least as permissive as Parity. Both MIT and Charity are more permissive than Parity, with fewer rules about releasing source code.
The author of package A must mind the license rules for the Prosperity license for package B, too. If the author of package A wrote that package primarily as a hobby, or as academic research, they’re free to continue using package B indefinitely. If the author of package A instead wrote package A primarily to make money, they need a private license for contributions to package B, so as not to exceed the 32-day trial period.
The bad news is that license graphs can be even more complex, where packages also used stacked licensing:
This kind of complexity shows up even in existing open software projects that don’t use any License Zero licenses, with mixes of GPL, BSD, MIT, LGPL, and other licenses.
The good news is that tools like the license zero command line interface can traverse even complex license graphs automatically, compile a list of every identifier mentioned in metadata, and compare those results against the licenses and waivers that the user already has. The License Zero command line interface merely evolves, and specializes, existing tools for analyzing open source license graphs.
License Zero isn’t the only way to financially support your work on open software, and it strives for maximum compatibility with other methods.
Ask people and companies for money, and hope they give it to you. Set up a payment link in your
README file. Set yourself up on Patreon. Form a foundation and solicit donations.
Sell books, stickers, shirts, and other physical goods with your project’s name or logo.
Sell or exchange the right to put company advertising, branding, or support acknowledgments in your project’s documentation, on your project’s website or social media accounts, or even in your software itself.
Give paying customers early access to your work ahead of its release as open source, some time later.
Require others to support you financially in order to use a trademark to identify themselves as providers of related products or services. Trademark licensing for service providers is often coupled with advertising, in the form of a listing among service providers on the project’s website.
Charge companies, conferences, or other venues to train others in the use of your project, in person or remotely.
Charge for access to and use of your time to assist users in using your work.
Apply to grant-making institutions and government entities for financial support, if it aligns with their objectives.
Charge others to install, configure, and run your project on their behalf.
Charge others to integrate your work into their applications or services.
Charge others for work they would like to do, such as bug fixes, feature adds, and other changes.
Sell proprietary software relating to or enhancing your open project. For example, many open source database companies license proprietary optimizations, monitoring tools, and replication features.