Skip to main content

License terms

sol2flow is source-available under the Elastic License 2.0 (ELv2). The code is public: you can read it, run it and change it, with two main limits. It is not an open-source license in the OSI sense. This page sums up what that means for people who run their own instance.

note

This is a plain-language summary, not legal advice. The license text in the sol2flow repository is what counts.

What you can do​

  • Self-host sol2flow on your own server or cloud account, free of charge.
  • Use it at work: a company can run it for its employees, contractors and projects, including for commercial work.
  • Change it: adapt the code to your needs and run your modified version. If you pass a modified copy on, keep the license and copyright notices and say that you changed it.
  • Fork it: under the same license, with a new name and logo (see below).

What you can't do​

  • Offer sol2flow to others as a hosted or managed service, for example selling sol2flow hosting or running it as a SaaS for your customers. Hosting it for your own organization is fine. If you'd like to offer it as a service, contact us about a commercial license.
  • Remove or work around license-key checks, or unlock features a license key protects. (sol2flow has no license-key checks today; this applies once there are any.)
  • Remove the license, copyright or other notices.

The license covers the code, not the sol2flow name and logo. You may self-host sol2flow under its name and talk about the project. A fork, another product or a hosted service must use its own name and logo and must not suggest that we endorse it.

Contributing​

Contributions are welcome. On your first pull request you are asked to sign the Contributor License Agreement (CLA) once, by replying with a comment.

Third-party components​

sol2flow uses open-source components that keep their own licenses. See License.