Operate · Control plane
Revoluzen Console
One control plane across every instance you run. Inventory, health, run history, alerting, and a promotion path between development and production with a review gate.
fleet run success · 24 h
98.6%
| instance | health | |||
|---|---|---|---|---|
| prod · mumbai | v1.0.1 | 14 | 99.8% | healthy |
| prod · pune | v1.0.1 | 9 | 100% | healthy |
| staging | v1.0.1 | 14 | 98.1% | healthy |
| plant-03 | v1.0.0 | 6 | 97.4% | drift |
| laptop · a.rao | v1.0.1 | 2 | 50% | 1 failed |
One view across every environment. Promotion is a reviewed operation with a record, not a file copy.
- License
- Commercial
- Status
- Early access
- Scope
- Fleet-wide
- Deployment
- Your infrastructure
Who it is for
For whoever ends up owning 'the data platform' once there is more than one install — and for anyone deploying Revoluzen into many sites or many customers.
The operate 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
See the fleet
Every environment, every version, every instance, with health in one view instead of a spreadsheet of hostnames.
- 01Inventory across environments, sites and versions
- 02Health and version drift visible before it becomes an incident
- 03Central run history across instances
Promote with a gate
Moving a pipeline, a model or a report from development to production should be a reviewed operation with a record, not a file copy at the end of a Friday.
- 01Reviewable diff of what is about to change
- 02Approval before the change takes effect
- 03Content promotion across pipelines, models and reports
- 04Rollback to the previous released version
Operate by exception
Alerting and triage designed around the question an operator actually has: what is broken, since when, and what did it affect.
- 01Failure alerting with the failing step attached
- 02Triage from the alert into the run and its inputs
- 03Patterns across instances, so a systemic failure reads as one problem
The details, in one table
The facts a technical evaluator checks first, without having to read a datasheet.
| License | Commercial |
| Scope | Multiple instances and environments |
| Deployment | Self-hosted alongside your instances |
| Status | Early access |
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 sourceWhat this does not do yet
You would find these out eventually. Finding them out now is cheaper for both of us.
Early access, and the newest part of the platform. If fleet management is the reason you are evaluating us, tell us early so we can be straight about timing.
It manages Revoluzen instances. It is not a general-purpose infrastructure monitoring tool and does not try to replace one.
Related products
Pipeline orchestrator
Revoluzen Flow
Build data pipelines on a visual canvas or in code, run them on your own machine, and see exactly what every step did.
Read moreEnterprise edition
Revoluzen Flow Enterprise
Everything in Flow, plus the parts an enterprise platform team asks for on day one: CDC, enterprise sources, workspaces and release control.
Read moreGoverned lakehouse
Revoluzen Catalog
A sovereign lakehouse and catalog: medallion layers, dimensional models, lineage and a governed SQL endpoint over open table formats.
Read moreRun 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.