Apache 2.0, no strings.
Here is what that actually means, without making you read a legal document. The legal document is the thing that governs, and it is one click away.
You may
- Use it, for anything, including commercially.
- Read every line of it.
- Change it, and run your changed version.
- Redistribute it, changed or not.
- Fork it and keep going without asking us.
- Use it inside a company, on private data, forever, for free.
You must
- Keep the licence and copyright notice with the code you redistribute.
- State what you changed, if you ship a modified version.
You may not
- Use the Inflexa name or logo to brand your fork, or imply we endorse it.
- Offer a hosted service under the Inflexa name.
The code is licensed. The name is not.
This is the one thing people get surprised by, so it is worth being blunt about. Apache 2.0 gives you the software. It does not give you the Inflexa name or logo.
Fork the project and ship it, and you are entirely within your rights. Call it something else. Say your product is “built on Inflexa” and that is fine too; describing what you built on is normal and we are not going to chase you for it. What you cannot do is ship your fork as Inflexa, because then nobody can tell whose bugs they are looking at.
The carve-out exists so the name stays a reliable signal, not so we have leverage over you. The licence already gave that away, on purpose.
What about the website?
This site’s source is not part of the Apache 2.0 release. It is marketing, not science, and nothing about your ability to use, inspect, or fork Inflexa depends on it.
The software, the orchestrator, the harness, the skills, the sandbox, and the provenance substrate, is the thing that is open, and it is open under Apache 2.0.