Skip to content

Revoluzen Flow v1.0.1 — Apache-2.0

Move · Enterprise edition

Revoluzen Flow Enterprise

The same orchestrator, with the capabilities a platform team needs before it will put a pipeline in front of the business: live replication, the enterprise sources, and a release process with a gate in it.

Revoluzen Flow Enterpriseworkspaces / promote / ingest_orders_daily v14 → prod
ingest_orders_dailydevprod · mumbaiapproved · r.menon
diff · v13 → v14+2 · ~1
  steps:+   - id: assert_contract+     kind: steward      - id: load_gold~       merge_key: [order_id, line_no]      retry_policy: 3x · backoff 30s
pre-flight
  • contract checkpassed
  • dry run against prod schemapassed
  • policy · prod requires 1 approversatisfied
  • rollback targetv13 retained
Promote to prodrollback → v13
cdc · orders · postgres wallag 1.2 s · 412 ops/s

Nothing lands in production without a diff somebody read; nothing streams without a record of what changed.

License
Commercial
Basis
Per environment
Deployment
Your infrastructure
Includes
All of Revoluzen Flow

Who it is for

For the team that has already run Flow, likes it, and now has to make it survive an audit, a second environment and a SAP extract.

01Where it sits

The move plane

Each product is adoptable on its own; together they share one catalog, one permission model and one run history.

01

Move

  • Flow
  • Flow Enterprise

02

Govern

  • Catalog

03

Answer

  • Studio

04

Operate

  • Console
  • Mobile

05

Prove

  • Evidence
How the planes connect
02Capability

Change data capture, not nightly guessing

Debezium-based CDC turns a source database into a stream of changes, so downstream tables track reality instead of last night's snapshot.

capability · 02Flow Enterprise
  1. 01Log-based capture from supported relational sources
  2. 02Replication that survives schema change rather than breaking silently on it
  3. 03The same run history and receipts as every other pipeline
03Capability

The systems the business actually runs on

The connectors that are genuinely hard to build and maintain, and that almost nobody open-sources, because they carry licensing and support obligations.

capability · 03Flow Enterprise
  1. 01ERP and warehouse: SAP, SAP HANA, Oracle, Teradata, IBM DB2, Informix
  2. 02SaaS systems of record: Salesforce, Workday, NetSuite, ServiceNow, Dynamics 365
  3. 03Maintained against vendor API changes as part of the license
04Capability

A release process, not a save button

Workspaces separate what someone is building from what is running. Promotion moves a change between environments, and a gate means somebody signed off.

capability · 04Flow Enterprise
  1. 01Workspaces with versioning, so edits do not land straight in production
  2. 02Dev-to-prod promotion with a reviewable diff
  3. 03Approval gates before a release takes effect
  4. 04Rollback to a previous version of a pipeline
05Capability

Built to be operated

The parts that only matter once the system is somebody's responsibility at three in the morning.

capability · 05Flow Enterprise
  1. 01Postgres metastore for concurrent, multi-user operation
  2. 02External execution providers, so heavy work runs off the control node
  3. 03High-availability topologies for single-site and active-active deployments
  4. 04License enforcement that is per environment, not per row of data
06Specification

The details, in one table

The facts a technical evaluator checks first, without having to read a datasheet.

LicenseCommercial, per environment
IncludesEverything in Revoluzen Flow (Apache-2.0)
MetastorePostgres, or SQLite for small installs
CDCDebezium-based, on supported sources
DeploymentSelf-hosted — your servers, your network
IdentityYour identity provider in front

Evaluating

Start with the open-source core

The fastest way to judge whether this platform suits you is to run Revoluzen Flow first. It is the same engineering, under Apache-2.0.

Open source
07Before you commit

What this does not do yet

You would find these out eventually. Finding them out now is cheaper for both of us.

01

This is self-hosted software under a commercial license, not a managed service. You run it; we support it.

02

High-availability topologies are deployment patterns we help you implement, not a one-click toggle.

03

CDC availability depends on the source database and its log configuration — we will confirm your specific sources during evaluation.

Run it yourself, then decide.

Revoluzen Flow is Apache-2.0 and installs in one command. If it fits, we can talk about the parts that are not open source.