Last updated: 9 March 2026
Envault is licensed under the Functional Source License (FSL), Version 1.1-MIT. This source-available license allows you to read, audit, and self-host the code while protecting our ability to offer competing commercial services.
After 24 months from each release date, the code automatically converts to the permissive MIT License, giving you complete freedom.
The Functional Source License (FSL) is a source-available license that bridges open source and proprietary software. It allows anyone to:
Unlike traditional open-source licenses, FSL restricts commercial competitors from offering Envault as a service without permission.
Deploy Envault on your own infrastructure for your team's use.
Review the source code, conduct security audits, and verify encryption implementations.
Use Envault for your organization's internal secret management needs.
Customize the code to integrate with your specific systems and workflows.
Freely use and distribute the Envault CLI with your applications.
You cannot use Envault's code to offer a competing SaaS, managed service, or commercial product that competes directly with Envault.
You cannot remove or alter copyright notices, license text, or proprietary markings.
You cannot sublicense, transfer, or commercialize the Licensed Work to third parties.
Before the 24-month conversion date, you cannot use Envault's code for any commercial competing service.
Envault's source code is not permanently proprietary. Each version automatically converts to the fully permissive MIT License after 24 months from its release date.
This conversion is automatic-you don't need to do anything. We believe in the long-term openness of Envault while protecting it during its initial growth phase.
You are explicitly welcome and encouraged to self-host Envault for your organization. Self-hosting is one of the core use cases FSL enables.
If your product directly competes with Envault's secret management service, you cannot use Envault's code under FSL. If your SaaS uses Envault internally or as a component of a non-competing service, you may need a commercial license. Contact us at dashdinanath056@gmail.com to discuss licensing options.
Each released version converts to MIT automatically 24 months after its release date. The conversion happens retroactively, so you can use older versions under MIT terms after the conversion date passes.
Yes, absolutely. You can fork, modify, and customize Envault for your internal needs. You cannot redistribute your modified version as a commercial service, but using it internally is fully allowed.
We offer commercial licenses for partners who want to embed or offer Envault. Please contact us at dashdinanath056@gmail.com to discuss partnership and commercial licensing opportunities.
Yes, security auditing is explicitly encouraged. We believe in the security-through-publicity model, and you're welcome to review the code, run security scans, and report vulnerabilities. Please responsibly disclose any security issues to our team.
FSL is source-available, not "open source" as defined by the Open Source Initiative. The source is public and you have significant rights, but commercial restrictions apply. After the 24-month conversion, it becomes fully open source (MIT).
We welcome community contributions, suggestions, and feedback. Please reach out to us for collaboration opportunities. Note that contributions will be licensed under the FSL.
If you have specific questions about licensing, commercial arrangements, or need clarification on what you can use Envault for, please don't hesitate to reach out.
Contact Us