Open source
Run it today. Pay us never, if that suits you.
Revoluzen Flow is the whole orchestrator under Apache-2.0: canvas, scheduler, run history, reliability checks and Copilot. It is not a trial, a demo, or a crippled edition of something better.
- License
- Apache-2.0
- Version
- v1.0.1
- Package
- revoluzen-flow on PyPI
- Telemetry
- None
From nothing to a running pipeline
No account, no license key, no cloud project. The second command opens the canvas in your browser against a server bound to loopback.
pip install revoluzen-flowrevoluzen openServes 127.0.0.1:8001 — loopback only until you opt in to LAN access
What you get
0+
Connector types
0
Starter templates
0
Steward finding kinds
0
Copilot tools
What it does on your machine
- Listens on
- 127.0.0.1:8001, loopback only
- Stores state in
- A local SQLite file
- Encrypts secrets
- Yes, at rest, always
- Phones home
- No
- Needs an account
- No
- Needs internet
- Only to reach your own sources
What we will and will not do
Open-core goes wrong when the boundary moves. Here is ours, written down, so you can hold us to it.
- The orchestrator core stays Apache-2.0. We are not relicensing it later.
- You can run it in production, commercially, without paying or telling us.
- You can fork it, modify it and ship it inside your own product, per the license.
- The open build has no artificial limits — no row caps, no connector throttle, no expiry.
- We do not collect telemetry from the open-source build. There is nothing to opt out of.
- We do not gate bug fixes behind a commercial tier.
- We do not require an account, a license key or a network call to run it.
What is commercial, and why
We are a company, so some things are paid. These are the ones, and the reasoning behind each — not a feature matrix designed to make the free tier annoying.
| Capability | Edition | Why it sits there |
|---|---|---|
| Canvas, scheduler, run history, Steward, Copilot | Open | This is the product. Gating it would make the open build a demo. |
| 100+ open-ecosystem connectors | Open | Databases, object stores and REST sources — the things a team can reasonably maintain themselves. |
| Single-node deployment, SQLite storage | Open | Enough to run real production work on one machine. |
| Change data capture (Debezium) | Commercial | Expensive to build and keep correct across source databases and their log formats. |
| SAP, Oracle, Teradata, DB2, Salesforce, Workday, NetSuite, ServiceNow | Commercial | Carry licensing and support obligations, and break whenever a vendor changes an API. |
| Workspaces, promotion, approval gates | Commercial | Only matter once a platform team owns the system — which is also when there is a budget. |
| Postgres metastore, execution providers, HA | Commercial | Multi-user and multi-node operation is where our support costs actually land. |
It is version 1, not version 10
The software is published, licensed and usable. It is also young, and you should evaluate it on that basis.
Connector maturity is published per connector. Most are SDK-validated, some are integration-verified, and none are yet marked production-ready. Check the specific one you need.
The open build targets a single node with SQLite. That is genuinely enough for a lot of real work, and genuinely not enough for a shared production platform.
The company behind it is early. If that is a procurement problem for you, say so at the start and we will talk about escrow, support terms and what happens if we are not here.
Install it before you talk to us.
We would rather have the second conversation — the one where you have already run a pipeline and have specific questions.