License (AGPL-3.0)¶
Stegflow is free and open-source software, released under the GNU Affero General Public License v3.0 (AGPL-3.0). In plain terms: you can run it, study it, modify it, and share it, for any purpose, including commercially, at no cost.
The short version: build whatever you want with it. The only thing the AGPL asks in return is that improvements to Stegflow itself stay open when you share them with others.
What you can do¶
Freely, forever, no fee, no seats, no usage limits:
- Use it commercially, in production, for your business, for clients.
- Self-host anywhere, on-prem, private cloud, or fully air-gapped.
- Run unlimited workflows, executions and users, there is no metering.
- Read, study and modify the complete source code.
- Adapt and extend it, add features, fix bugs, tailor it to your needs.
- Integrate it into your stack and build products on top of it.
- Offer it as a hosted service (SaaS) to your customers.
- Sell support, hosting or consulting around it.
- Distribute copies and your own modified versions.
Your work stays yours. Your workflow definitions (ASL) and any application that talks to Stegflow over its API or CLI are independent works. Using Stegflow does not make your code a derivative, you never have to open-source your business logic, your definitions, or the apps around it. The license only concerns Stegflow's own source code.
What you need to do¶
These conditions apply only when you share Stegflow with others, by distributing it, or by exposing a modified version to users over a network. Pure internal use triggers none of them.
- Keep the license and copyright notices in place.
- Provide the source, if you distribute Stegflow, or run a modified version that users reach over a network, those users must be able to get the complete corresponding source, including your changes, under AGPL-3.0.
- Share modifications to Stegflow under AGPL-3.0 (this is the copyleft).
- State the significant changes you made.
What you can't do¶
- Take Stegflow (or a modified version), give it to others or run it as a service, and keep your changes to it closed.
- Relicense Stegflow under proprietary or incompatible terms.
- Remove or hide the license and copyright notices.
- Hold the authors liable, the software is provided without warranty.
FAQ¶
Can I use Stegflow in my company for free?
Yes. Internal and production use is free, with no per-seat or per-execution fee and no usage caps. Run as many workflows, executions and users as you like.
Can I use it for commercial purposes?
Yes, for any purpose, commercial included. There is no separate "business" tier to buy.
Do I have to open-source my workflows or my own application?
No. Your ASL definitions and any application that calls Stegflow over its API or CLI are independent of Stegflow's code. The AGPL applies to Stegflow's own source (and to modifications of it), not to what you build around it or run on it.
Can I run Stegflow as a hosted service (SaaS) for customers?
Yes. The single condition: the users of that service must be able to obtain the complete source of the Stegflow instance you run, including any modifications you made to Stegflow itself, under AGPL-3.0. If you run it unmodified, simply point them to the public repository.
I modified Stegflow, but only for internal use. Do I owe anything?
Running a modified version purely inside your organization is not distribution and does not, by itself, oblige you to publish anything. The source-sharing obligation kicks in once you distribute that version or expose it to outside users over a network.
Can I sell support, hosting or consulting around Stegflow?
Yes. Building a commercial offering of services around Stegflow is fully allowed.
Can I rebrand or white-label it?
You can customize the branding (per-tenant branding is even a built-in feature). What you can't do is strip the license/notices or present Stegflow as your own proprietary product, if you distribute or host it, the source obligations and notices still apply.
What exactly counts as a 'modification I must share'?
Changes to Stegflow's own source code that you then distribute or expose to network users. Writing workflow definitions, calling the API, configuring deployments, or running Stegflow as-is are not modifications.
AGPL doesn't fit my use case, what are my options?
Talk to us. Open an issue or contact the maintainers on Codeberg to discuss alternatives, such as a separate commercial license.
Not legal advice. This page is a plain-language summary to help you get oriented, it is not a substitute for the license. The full AGPL-3.0 text is the only authoritative source; if you have doubts about a specific situation, consult a lawyer.