Licensing

Overview

Envault source code is distributed under a proprietary, all-rights-reserved inspection license.

Most of this repository is not open source. You may inspect the code for transparency and security auditing, but you may not run, modify, redistribute, or deploy proprietary portions unless you have prior written permission from the copyright holder.

Scope exception: the mcp-server/ and src/lib/sdk/ directories are distributed under the MIT License. The repository root LICENSE applies to all other paths.

What You Can Do

Read the Code

View, read, and inspect the repository for transparency, educational reference, and architecture understanding.

Audit Security Practices

Analyze the source code to verify security controls or identify vulnerabilities.

What You Cannot Do

Execute, Compile, Run, or Deploy

You may not execute, compile, run, or deploy proprietary repository components in any environment.

Copy, Modify, Fork, or Derive

You may not copy, modify, fork, or create derivative works.

Redistribute or Commercialize

You may not distribute, publish, sublicense, share, sell, or use the Licensed Work to provide any commercial or non-commercial service.

Remove Notices

You may not remove or alter copyright, proprietary, or license notices.

Frequently Asked Questions

Is Envault open source?

No. Envault is source-visible for inspection and security auditing, but it is not licensed as open-source software.

Can I self-host or run Envault locally?

Proprietary parts of the repository require prior explicit written permission. The mcp-server/ and src/lib/sdk/ directories are MIT-licensed exceptions.

Can I fork or modify this repository?

Proprietary repository sections cannot be forked or modified without written permission. MIT-licensed subdirectories follow their own license terms.

Can I audit the code for security?

Yes. Security review and vulnerability analysis are explicitly permitted.

Full License Text

Read the complete legal terms in the LICENSE.txt file, or in the repository root LICENSE.

Questions About Licensing?

For written permissions or licensing clarifications, contact us.