See what happens at every step
The whole path on one page — and at each step you can see the actual thing you get: the terminal, the map, the record, the signature. Most of it is the free data catalog, which works anywhere; the EU-compliance part is an optional branch you take only if you need it.
Choose a path to light up your route and dim the rest. Each step shows what you do, what you’ll see, and what you get — and links to the full page.
Install & first run
engineerfreeyou do Run one command. Regixo reads the structure of the sources you configure — about five minutes, no Docker.
$ npx regixo start ▸ scanning your sources — names and types only, never the values inside… ✓ app-db — 63 datasets · 398 columns · 170 with personal data ✓ done — your data map is ready → regixo open ✓ draft record generated
you get A searchable map of every dataset and column — built from your real systems — names and types only, never the rows. See it in full →
Connect your sources
engineerfreeyou do Add each database or service you want on the map. Regixo stores the name of the secret, never the secret.
$ regixo add postgres --ref DATABASE_URL ✓ “App DB” connected (only the env-var name is stored)
you get Every database and SaaS — Postgres, MySQL, Stripe, dbt, a CSV — on one map. See it in full →
See the map
engineerAI agentfreeyou do Open the map in your browser. Search it; personal-data columns are flagged. A different surface: an assistant registered against the read-only regixo mcp server can answer questions about the map without opening it — that one is optional, needs a one-time registration, and never changes anything.
you get A clear picture of where personal-data-looking columns live and how they flow — for your team and your AI tools to read. See it in full →
Enrich & keep it current
engineerAI agentfreeoptionalyou do Optional, all of it. Correct a flag, draw a data flow, describe a table, define a term — the flags and the flows change your record; the descriptions and terms do not. Then schedule a re-scan (CI or cron) so the map stays current.
regixo mcp server (a different surface)you ▸ where do we store customer email? regixo ▸ users.email and marketing.contacts.email — both flagged personal data · map scanned today
you get A map that stays true as your data changes — and answers questions in plain language. What you can add → Keep it current →
You have a living data catalog
Free, forever — and you keep it current on a schedule you set. If you don’t need to prove EU compliance, this is your finish line. GDPR and DORA are EU laws — take the next step only if your company must keep those records.
Do you need to prove EU compliance?
A GDPR Article 30 record (a RoPA), or a DORA register — paperwork many EU companies must keep. Not in the EU, or not required to keep one? You’re already done above.
Nothing more to do — the catalog is a complete product on its own. Companies without a GDPR or DORA obligation stop here.
Continue below. This is where your organisation and compliance team get involved — a person makes the legal calls and signs.
Hand it off
engineerDRAFTfreeyou do First answer Your part on the Record page — the three facts only engineering knows — so they travel with the record. Then forward the draft; Regixo shows exactly what leaves before anything is sent. No terminal? The free portal does the same hand-off — an in-portal invitation and the draft-PDF download.
$ regixo invite what leaves: personal-data table names + derived category labels ✓ column names · column types · row values ✗ never ✓ RoPA_DRAFT.pdf + app.regixo.com/claim/clm_7Q…
you get Your compliance team receives a readable PDF and a private link — no install, no account needed to review. See it in full →
Claim & review
compliance teamDRAFTyou do Your compliance team opens the link, signs in with a one-time email link, and reads the record.
you get A finished-looking record built from the real systems — not a blank form to fill from scratch. See it in full →
Fill the legal calls
compliance teamDRAFTyou do A person makes the judgments a machine can’t — the lawful basis, retention, DORA contracts. Regixo suggests; a human confirms.
you get The legal decisions made and recorded by a named person — Regixo never confirms one for you. See it in full →
Unlock & sign
compliance teampaid to signOFFICIALyou do Pay the published price, then a named person signs. Two questions set the price — nothing is guessed from your data.
you get An OFFICIAL record — signed under a real person’s name and sealed, checkable offline. See it in full →
Keep it current
engineercompliance teamOFFICIALyou do Let it re-scan on a schedule. When a signed activity’s core fields change, Regixo asks a person to re-sign — it never re-signs for you.
you get A record that stays in step with reality all year — never quietly out of date. See it in full →
A signed, defensible, always-current official record
The GDPR RoPA (and, for financial firms, the DORA register) — signed by your own officer, sealed, checkable offline, and kept in step with your real systems.
Ready to begin? The whole journey starts with one command on the engineer’s machine — said to their coding agent, or typed.
Start — Install & first run →