We create and maintain a number of packages that span testing, AI, general-purpose CLI and build tools, application architecture, and more. Some are well established, others niche, some large and some small:

To support us, rather than per-project licensing (which can become costly or annoying to keep track of), we offer the Open Source Maintenance Fee, which covers all current and future libraries and tools from Devlooped.

If a particular software/package does NOT include the OSMF EULA, then you're not bound by it at all.

Devlooped Open Source Maintenance Fee

Open Source Software is free, but maintaining an Open Source Project is expensive. A lot is asked of the maintainers of this project, including:

• Triage issues
• Keep build scripts working
• Update software dependencies
• Track security reports
• Produce new releases
• Tackle spam in the discussion forums and issue trackers
• Maintain signing certificates
• And many, many other chores

The Open Source Maintenance Fee is a simple and sensible way to pay for the time and effort they spend sustaining a project.

If you, your organization, or your project makes money, select the monthly payment tier that applies to the size of your organization. If not, a personal sponsorship of your chosen amount to support @kzu's favorite activity is also welcomed!

Stats

Here's a quick peek at the open source work we do on GitHub:

FAQ

Q: Who pays the fee?

All individuals and organizations that generate revenue and all government agencies that use an Open Source Project which requires a Maintenance Fee must pay the fee. Also, Open Source Projects that require a Maintenance Fee, must pay any fees required by their dependencies.

Q: Do I have to pay the fee for each product in my organization?

No. An organization only needs to pay the fee once and all of its products are covered.

Q: Do I have to pay the fee for each Devlooped project my organization uses?

No. One fee covers all of Devlooped projects.

Q: Do I have to pay the fee if my organization makes money but our product that uses the project is offered for free?

Yes. The requirement to pay the Maintenance Fee is based on whether the organization generates revenue, not whether the products they offer are free or not.

Q: Can I pay by yearly invoice?

Yes. See the GitHub invoice documentation for its requirements.

Q: Do I have to pay additional for newer versions of the project?

No. As long as you pay the fee, you are entitled to all available versions.

You can find more frequently asked questions on the Open Source Maintenance Fee site.