Use case · Keep data in-country, in-network
Data residency and sovereignty
Run pipelines, a lakehouse and analytics entirely inside your own network — with no hosted control plane, no telemetry and no outbound dependency — so residency obligations are met by architecture rather than by contract.
- Outbound to vendor
- None required
- Telemetry
- None
- Verify it
- Packet capture; core is Apache-2.0
- Products
- Flow · Catalog · Studio
Who it is for
For security, legal and platform teams whose residency obligation is a hard constraint, not a preference — and who have learned the difference between a vendor's promise and an architecture.
What this looks like from the inside
Residency rules, client contracts and a security team that will not approve production data on a third party's cluster. Most data tooling assumes the opposite: the vendor runs it, your data flows through them, and a data-processing agreement stands in for control.
An agreement is not architecture. If the data leaves, it has left.
Drawn, not described
The one thing the prose cannot do: show the moving parts and where the boundary is.
sources
Postgres · S3 · REST
Flow
bind 127.0.0.1:8001
Catalog
open formats · your object store
Studio
behind your SSO
every arrow starts and ends inside this box
outside
Revoluzen (vendor)
telemetry
license check
control plane
data in transit
Prove it yourself: packet capture shows no traffic to us; the core is Apache-2.0.
Step by step
In the order it actually happens.
- 01
Install inside the boundary
Revoluzen Flow installs on a machine you own and binds to 127.0.0.1:8001 by default — unreachable from the network until you explicitly allow LAN access. There is no hosted control plane to register with.
- 02
Connect only to your own systems
100+ connector types reach your databases, object stores, files and APIs. Every connection is one you configured; the software initiates nothing else.
- 03
Store in open formats on storage you own
Revoluzen Catalog keeps the lakehouse in open table formats on your object storage. Access rules — row-level security, column masking — are enforced at its SQL endpoint, inside the boundary.
- 04
Analyze without exporting
Revoluzen Studio serves dashboards and reports on-premises behind your SSO. Nobody exports the warehouse to a hosted BI tool to look at it.
- 05
Prove the boundary held
Run a packet capture: no traffic to Revoluzen. Read the core: Apache-2.0. Keep the signed receipts: processing is accounted for, inside the boundary, verifiable offline.
What actually changes
| Dimension | Today | With Revoluzen |
|---|---|---|
| Where production data lives | A copy on the vendor's infrastructure, in a region from their list. | Only on infrastructure you own, in the jurisdiction you chose, by construction. |
| What a residency audit relies on | The vendor's data-processing agreement and their word. | The absence of any outbound path, which you can demonstrate yourself. |
| What the vendor can see | Usage telemetry at minimum; often the data in transit. | Nothing. There is no telemetry and no call home. |
Which product does what
Each product is adoptable on its own; together they share one catalog, one permission model and one run history.
Revoluzen Flow
Moves data between your own systems — 100+ connector types — on machines you own, bound to loopback by default.
Product pageRevoluzen Catalog
Holds the governed lakehouse on open table formats on your own object storage, with row-level security and column masking enforced at the SQL endpoint.
Product pageRevoluzen Studio
Serves dashboards and reports on-premises behind your SSO, so analysis does not require exporting data to a hosted BI tool.
Product pageWhere it runs
Everything runs on infrastructure you control. The software requires no outbound connection to function, so it works in networks that permit traffic only to your own sources. Verify it with a packet capture; the core is open source.
What you end up with
- 01No copy of production data on vendor infrastructure, by construction
- 02Jurisdiction decided by where you deploy, not by a vendor's region list
- 03A core you can audit: Apache-2.0, readable by your security team
- 04No telemetry and no license call-home to explain to a regulator
The honest limits
You would find these out eventually. Finding them out now is cheaper for both of us.
Self-hosted means you operate it. That is the point, and it is also a responsibility.
Revoluzen Catalog and Revoluzen Studio are in early access with design partners.
AI features follow the same rule only if you point them at a local model or a provider you have an agreement with; that choice is yours.
Asked about this scenario
Does Revoluzen send any data outside my network?
No. Revoluzen software is self-hosted and makes no outbound connection to Revoluzen: no telemetry, no usage statistics, no license checks. It only reaches the sources and destinations you configure.
Can Revoluzen run in an air-gapped environment?
Yes. Nothing in Revoluzen requires internet access to function; install media aside, it operates entirely within the network it is deployed in, and Evidence receipts verify offline.
Where is my data stored when I use Revoluzen?
Wherever you deploy it: a local SQLite file for a single machine, a Postgres metastore for a shared server, and open table formats on your own object storage for the Revoluzen Catalog lakehouse.
Adjacent scenarios
Audit & compliance
Regulated reporting with verifiable evidence
Produce regulatory and board figures from pipelines that leave a signed, offline-verifiable record of every run — so the evidence behind a number survives longer than a dashboard screenshot.
Move off per-row pricing
Replace hosted ELT with self-hosted pipelines
Move pipelines off a hosted ELT service onto an orchestrator you run yourself — with a visual canvas, SQL and Python steps, resumable runs and per-environment licensing that does not grow with your row count.
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.