> ## Documentation Index > Fetch the complete documentation index at: https://docs.neobank.proofof.tech/llms.txt > Use this file to discover all available pages before exploring further. # License > The Perflo neobank platform is released under the Apache License 2.0 and what that means for users and partners. # License Perflo Neobank is released under the Apache License 2.0 (SPDX identifier `Apache-2.0`). The full license text lives at the repository root in [`LICENSE`](https://github.com/gcharang/neobank-wrapper/blob/master/LICENSE). ## What the license permits Apache-2.0 is a permissive license. You may use, copy, modify, merge, publish, distribute, and sublicense the software — commercially or otherwise — and you may sell copies. The license also grants a patent license from each contributor for the patent claims their contribution necessarily infringes, so downstream users receive both a copyright license and a patent license for the code they use. ## What the license requires If you redistribute the software, in source or binary form, you must: * Preserve the copyright, patent, trademark, and attribution notices in the source you distribute. * Include a copy of the Apache License 2.0 with the distribution. * State, prominently, any changes you have made to the files you distribute. ## Why Apache-2.0 and not MIT The explicit patent grant and patent-retaliation clause are why this platform uses Apache-2.0 rather than a permissive-as-MIT license. Self-hosting banks and partners extend this platform, integrate it into their own products, and ship derived services. Apache-2.0 gives every contributor and downstream user a clear, written patent license for the code they receive and a defined recourse if a contributor initiates patent litigation over the Work. That matters here precisely because the platform is meant to be extended, not just run. ## Contributing under the license Inbound contributions are licensed under the same Apache-2.0 terms as the project — Section 5 of the license makes that automatic unless you state otherwise. See [Contribute](contributing/setup) for the development setup and [CI & review lanes](contributing/ci-and-reviews) for the gate every change passes before merge.