How Regixo works, from scratch.
We'll start with the plain-English basics — what a data catalog even is, and what "EU compliance" means — then show you every screen you get, exactly as it looks on your machine. No jargon left unexplained.
Three terms, in plain English.
If you've never run a "data catalog" or dealt with EU privacy law, these are the only three ideas you need. Everything else on this page builds on them.
All your data, in one list
It's spread across databases, payment tools and spreadsheets. A catalog brings it together so you can search it in one place.
Data about a person
Names, emails, phone numbers, card details. It's protected by law — so step one is knowing which of your data is personal.
The proof the law wants
Hold EU personal data and you must record what you keep and why. That record is a RoPA; regulated financial firms keep a similar one called DORA.
Don't need EU compliance? That's fine — the map alone is useful to any team, anywhere. The compliance part simply waits, already drafted, for the day someone asks.
Scattered data in. One clear map out.
Before Regixo, the answer to "where does our customer data live?" is spread across systems and people's heads. One command replaces the guesswork with a single, readable map.
Data everywhere, owned by no one
Nobody can say for sure what's stored, which parts are personal, or who's responsible. Answering an auditor takes weeks of asking around.
One map, personal data flagged
38 datasets across 4 sources, mapped in minutes. 42 columns look like personal data — already flagged. The same answer, from one command instead of a week of asking around.
Say it — or type it. Same command either way.
Have Claude Code, Cursor, Codex — any coding agent with a terminal — open in this project, and tell it what you want. It runs the same regixo commands you would, including the install. There is nothing extra to install and nothing to register. No agent? The terminal is first-class too.
Tell your coding agent
One sentence does it. The agent runs the ordinary command in the same project shell you'd have typed it in, watches the output, and reports back.
“Set Regixo up in this project — scan my sources and build the data map.”
Or run it yourself
Paste this into your project's terminal. Either path, the machine needs Node 22.18 or newer — no Docker, no server, no account.
npx regixo start
Every screen you get, before you install.
Recreations of the real screens, label for label, so you know what to expect before you install. They are static pictures; the live ones run on your own machine. Four steps, start to finish — the first three are free and happen entirely on your own computer.
Install & scan
Regixo finds your sources, connects, and reads only their structure — the table and column names and their types, never the rows inside. It prints exactly what it reached, and exactly what it didn't.
$ npx regixo start Regixo — free to install and use. It maps your data and drafts your compliance record, right here. Nothing leaves this machine. ▸ Looking for your databases… ✓ Found your PostgreSQL database — ready to map (from the DATABASE_URL setting) ▸ scanning your sources — names and types only, never the values inside… ✓ app-db — 12 datasets · 148 columns · 21 with personal data ✓ stripe — 5 datasets · 61 columns · 12 with personal data ✓ warehouse — 21 datasets · 262 columns · 9 with personal data ✓ dbt — 0 datasets · 0 columns · 0 with personal data ✓ done in 4m12s — your data map is ready. To see it, type: regixo open (opens it in your web browser) Bonus, already done: a DRAFT RoPA — your GDPR record of how you use personal data (6 activities found in your real tables).
Open a dataset
Run regixo open and the map opens in your browser at localhost:4319. Click any table and you see what its columns look like, where the data came from, and where it goes next.
warehouse/analytics/customersIn plain words: this dataset looks like it holds 5 kinds of personal data — address, date of birth, email, name, and phone. That's why it feeds your compliance record.
Columns| Column | Type | Personal data |
|---|---|---|
email | STRING | ● Emailby field name |
full_name | STRING | ● Nameby field name |
date_of_birth | DATE | ● Date of birthby field name |
phone | STRING | ● Phoneby field name |
billing_address | STRING | ● Addressby field name |
plan | STRING | not personal |
created_at | TIMESTAMP | not personal |
Regixo reads column names and types only — never the values — so double-check anything that looks wrong.
Comes from2 direct
- users· app-dbvia dbt
- customer· stripeasserted by you
Feeds into1 direct
- revenue_daily· warehousevia dbt
Arrows point the way data moves — down the page, into customers and out of it. Flows inside your warehouse (including your dbt models) are found on each scan; flows between systems you assert yourself. Dataset-level only — Regixo never implies column-level flow.
Notice the honesty: every flag says how Regixo recognised it (“by field name”), and every data flow says who claims it — the scan, or you.
Read the draft record
From the same scan, Regixo writes a draft of the EU compliance record — the RoPA, and a DORA register if you're a regulated financial firm. It's free to read, and stamped DRAFT: useful, but not yet official.
Every field says where it came from. found means Regixo read it from your real tables. suggested means Regixo proposed it and a person still has to agree. needs you means only a person can answer it.
A plain list of every way your company uses people's personal data — drafted from your real schema. EU law (GDPR Art. 30) makes most companies keep one.
Manage customer accounts
| Purpose | Create and run customer accounts and subscriptions so people can use your product or service. suggested |
|---|---|
| Personal data | Date of birth, Email, Financial (card/IBAN), Name, Phone found |
| Data subjects | Customers suggested |
| Recipients | Stripe found |
| Lawful basis | You need it to provide your product or service. Art. 6(1)(b) contract suggested |
| Retention | Account lifetime + statutory minimum suggested |
| Transfers outside the EU | None identified from source regions suggested |
| Security measures | Describe them — or set once in your org profile needs you |
Forward it — only when you need to
If someone needs the official version, regixo invite makes a shareable PDF and a link. This is the only step that leaves your machine, it still carries metadata only, and you see exactly what would be sent before it goes.
Sent by your engineering team from a scan of your real systems. Read-only, metadata only — no customer data, no row values. You need no account to read it.
Still needs a person · 4 items
| Security measures | Describe them — or set once in your org profile needs you |
|---|---|
| Lawful basis | Regixo suggests: you need it to provide your product or service. Art. 6(1)(b) contract suggested — confirm or change |
| Retention | Account lifetime + statutory minimum suggested — confirm or change |
| Transfers outside the EU | None identified from source regions suggested — confirm or change |
From the engineer to the person who signs.
You run the scan once, and two people read it: the engineer, as a live map today; the compliance team, as paperwork later. The handoff is built in — the engineer never has to become a compliance expert, and the compliance team never has to touch a terminal.
Runs the scan
Installs Regixo, gets the map, glances at the draft record. Five minutes, no cost, no sign-up.
does the easy technical partA view-only draft
A shareable link + PDF of the draft record. Read-only, metadata only — safe to forward to anyone who needs to look.
live on day oneMakes it official
Opens the link, reviews it, and — when it's truly needed — unlocks the signed, official version. They hold the budget and the sign-off.
does the legal partYour actual data never leaves your machine.
This is the question everyone asks, so here's the blunt answer. Regixo reads the labels on your data, never the contents. It runs locally, and nothing is uploaded unless you explicitly forward it.
What Regixo reads
The structure — the names and shapes of things, the way a library reads spine labels, not the books.
- ✓Table names — e.g.
users - ✓Column names — e.g.
email - ✓Data types & how tables relate
- ✓Row counts — how many, never which
What it never touches
The contents — the actual values inside your rows. Never read, stored, or sent.
- ✕The real names, emails & addresses
- ✕Card numbers & payment details
- ✕Messages, documents & file contents
- ✕Anything a single customer would recognise as theirs
Quick answers.
?Does my data ever leave my machine?+
?Does my coding agent send my data anywhere?+
regixo command in your project shell — the same one you'd type. Regixo itself makes no cloud call of any kind and has no AI in it. Whatever your agent sends to its own provider is between you and that tool, exactly as it is for every other command it runs for you.?Can I read the code — is this legit?+
?Is it really free, or is this a trial?+
?Do I need to be technical to use it?+
?What if my company isn't in the EU?+
?What does it connect to?+
.env; the config file stores only the variable's name.?How long does it take?+
See it on your own data in five minutes.
One command, on your machine, nothing uploaded. The map is free — read it, and decide for yourself.
npx regixo start