At a glance
| License | FSL-1.1-ALv2 |
| Internal use | Free for any organization, any size |
| Modification | Permitted |
| Redistribution | Permitted under the same license |
| Future open source | Auto-converts to Apache-2.0 two years after each release |
| Questions / consultations | diego.perez@quasarops.com |
What the FSL permits
The examples below are illustrative, not exhaustive. Many real-world uses fall under “Permitted Purpose” in the LICENSE; the examples below are common patterns that almost always qualify. You can use Fracta freely under the FSL in any of the following situations:- Internal use, any organization size. Run Fracta on your own infrastructure to support your own work — security operations, knowledge management, internal automation, research, threat hunting, anything. This is true regardless of whether your organization is a charity, a startup, a Fortune 500 enterprise, or anything in between.
- Modifying Fracta for your own use. Patch bugs, customize the configuration, build internal extensions or strategies. Your modifications remain subject to the FSL.
- Building strategies, plugins, and integrations on top of Fracta. These are derivative works and are also covered by the FSL by default.
- Using Fracta to do your own work for clients, internally. For example, a consultancy may run Fracta on its own laptops or servers to investigate data and produce reports for clients, provided that the deliverable to the client is the analysis, report, or recommendations — not Fracta itself.
- Helping a client deploy Fracta in their own environment, where the client uses Fracta directly and is themselves an FSL licensee in compliance with these terms. This is the “professional services to a licensee” carve-out in the FSL.
- Non-commercial education and research.
This list is illustrative, not exhaustive. Any use of Fracta that is not a “Competing Use” as defined in the LICENSE is permitted. If your situation isn’t covered by the examples above, the LICENSE text still controls.