Operate · Companion app
Revoluzen Mobile
A phone app for the people who own the platform but are not at a desk: see what is running, get told when something breaks, and approve a release with the change in front of you — against a backend you run, inside your own network.
42
runs today
1
failed
2
awaiting you
recent runs
- ingest_orders_daily02:14 · 1.26M rows
- cdc_customersrunning · step 3 of 5
- refunds_syncretry 1 · 41K rows
plant-03 · version drift
v1.0.0 behind fleet · 09:12 · push + teams
- version
- v13 → v14
- built by
- a.rao · staging
- gates
- validation ✓uat ✓
diff
- +assert · steward 37 checks
- ~schedule 02:00 → 01:30
- =4 steps unchanged
The phone talks to a backend you run, inside your network. Decisions are recorded; credentials never leave the server.
- License
- Commercial
- Status
- Early access
- Platforms
- iOS and Android
- Backend
- Yours, inside your network
Who it is for
For the platform owner on call, the manager who signs off on releases, and the analyst who wants this morning's numbers without opening a laptop.
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 what is running, right now
The run list and the run detail from Revoluzen Flow, on the phone: which step is executing, which failed, and how long it took — without a VPN session into a laptop.
- 01Live run list with per-step status and timings, refreshed while a run is in progress
- 02The pipeline's DAG, so a failure is read in context rather than as a line of text
- 03Cancel a run as an operator, with the action recorded
- 04Run detail is redacted by default — connection secrets never reach the phone
Approve with the change in front of you
An approval is not a yes/no button with a title. The app shows the diff, the versions, the DAG of what changes and who built it, and records the decision with a name, a time and a note.
- 01Diff, version comparison and before/after of the change being approved
- 02Multi-step approval chains: a named approver or a role, with admin-set alternates for time away
- 03Every decision recorded with who, when and the note they left
- 04Decision-only by design: the app never holds credentials that could act on its own
The alert that matters, on the channel you chose
Failed runs, unreachable instances, unhealthy connections and version drift become notifications — de-duplicated, so a condition that persists alerts once rather than every minute.
- 01Push notifications on the phone, routed per category
- 02The same alerts to Slack, Teams, email or a webhook, configured by your admin
- 03Each person chooses which categories reach them, and where
- 04No cloud relay of your alert content: your backend sends to your channels
Reports and answers, governed
Revoluzen Studio dashboards on the phone, and a governed Ask over your model — with the citations and confidence of the answer shown, and the permissions of the person asking applied.
- 01Dashboards from Studio, with the access rules of the signed-in user
- 02Ask in text or by voice, transcribed by a speech model you host, never a cloud one
- 03See who can see a dataset: masks, row rules and surfaces, from Revoluzen Catalog
- 04Share a dashboard and the recipient sees only what their own access allows
The details, in one table
The facts a technical evaluator checks first, without having to read a datasheet.
| License | Commercial, with the products it connects to |
| Platforms | iOS and Android (one React Native codebase) |
| Backend | A mobile backend you run, inside your network |
| Connects to | Flow, Catalog, Studio and Console |
| Identity | Your identity provider (OIDC), or local accounts; every call carries the signed-in user |
| Transport | TLS to your own backend; no Revoluzen relay |
| Distribution | Your device management or enterprise distribution |
| 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. It has run on devices against live products; it has not been through an app-store review or a public release, and it is distributed through your own device management for now.
It needs its backend. The mobile backend runs inside your network and talks to Flow, Catalog, Studio and Console; phones need a TLS route to it, over your VPN or a published endpoint you control.
Push notifications leave your network: the push service and Apple or Google deliver them. The content is minimal, and an air-gapped deployment uses polling, Slack, Teams or email instead.
It is a companion, not a mobile editor. You cannot build a pipeline or design a report on the phone, and that is deliberate.
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.