The whole journey
Start with the data catalog — map your data, connect your sources, keep it fresh. That is a complete product on its own, and it is where everyone begins. If your company is in the EU and must keep a GDPR RoPA or DORA record, an optional compliance module continues from the same map. Each stage below links to a walkthrough that walks it, screen by screen.
Every step you run comes two ways: the sentence you say to your own coding agent — Claude Code, Cursor, Codex, already open in this project — and the command it runs.
Your agent runs the same regixo command in the same shell. No second path,
nothing extra to install. The switch at the top right chooses which one leads, on every page.
Steps 7–9 belong to your compliance team, and signing carries no sentence at all — that one is a person's.
1 · Get your data mapped
You need Node ≥ 22.18 — nothing else. One command scans your sources’ structure into a local catalog and drafts your record. It asks at most two questions.
“Set Regixo up in this project — scan my sources and build the data map.”
Show the commandHide the commandShow the sentenceHide the sentence
$ npx regixo startYour agent runs the scan — it reads Regixo’s own manifest first, so it is not guessing at commands, then reads names and types only, never a row value. Whether you are a regulated financial firm is yours to declare: Regixo cannot infer it, and it decides whether a DORA register is drafted.
Check it worked: a dataset count, a count of columns that look like personal data,
and a DRAFT record. Then read regixo status’ coverage line: a source it
could not reach is missing from the map, the counts are quietly too low, and the coverage
line names it.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
Regixo — maps your data, drafts your record. Nothing leaves this machine. ▸ Detecting data sources… ✓ Postgres DATABASE_URL reachable ? Connect & scan this source? [Y/n] y ? Is your organisation a regulated financial entity? [y/N] n ▸ scanning metadata… 63 tables · 55 with personal data ✓ your data map is ready → regixo open ✓ draft record generated → RoPA_DRAFT.html
Full detail, the two questions, and every state: Install & first run →
2 · Connect your sources
If nothing was auto-detected, connect a source by hand. Regixo stores only the name of the env var that holds your secret — never the secret itself.
“Add my Postgres database to Regixo.”
Your agent fills in everything except the token — you put that in .env yourself.
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo add postgres --ref DATABASE_URL --label "App DB"
Every connector (Postgres, MySQL, SQL Server, Redshift, Snowflake, BigQuery, Stripe,
dbt, CSV) — Snowflake and BigQuery ship natively, but have not yet been run against a live account —
plus your own connector for anything else (regixo connectors new / regixo add
script), the real connection strings, and how to reach a locked-down database:
Connect your sources →
3 · See the map
Open the catalog in your browser. Search it, filter to the personal data, see why each column was flagged and where data flows.
“Open the Regixo dashboard in my browser.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo openWhat the scanner reads vs refuses, and how the classifier decides: Read the map →
— or in the dashboard: regixo open is the web portal — browse and
correct the map by pointing and clicking, no commands. Tour it: The free portal →
The two agent surfaces — don’t confuse them
An agent works with Regixo two ways, and they are separate. You have been using the first one since step 1.
1 · Operating Regixo — you are already doing it
Say the sentence to the coding agent that is open in this project, and it runs the
regixo command for you. There is nothing to install and nothing to register. It is
the same command in the same shell — that is why every step on this page shows you both.
To hand over the whole job at once, give it the playbook. It teaches the setup order, the guardrails, and where the agent must stop and hand back to you:
“Read Regixo’s operating playbook, then set it up for this project.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo skill2 · Reading the catalog — a real, one-time setup
The other surface is an assistant that reads your catalog and answers questions about it — "which columns look like email addresses?" — over MCP, the protocol Claude Desktop, Claude Code and Cursor already speak. It is read-only by construction: there is no write tool at all, so it can never scan, correct a flag, or change the record. Unlike surface 1, it takes a registration:
$ regixo mcp --print-configIt prints a JSON block you paste into your assistant’s MCP settings, once.
regixo classify set, because that
is an ordinary command and a flag is a mechanical fact. What neither may ever do is make a
legal call — confirming a purpose, a lawful basis or a retention period, or signing the record.
Those carry no sentence anywhere in these docs, on purpose.Both surfaces — the eight read tools, the tasks-to-commands table, and what a session looks like: Use an AI agent →
4 · Keep your map current
Your schema changes, so re-scan on a schedule. regixo watch refreshes the map and logs
exactly what changed — added, removed, reclassified — so your catalog never drifts. Run it from CI and
you are done.
“Schedule Regixo to re-scan my data automatically and tell me when something changes.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo watch --ciThe CI recipe and the change log: Keep it current →
That is the whole data catalog — a complete product on its own. Everything below is optional.
5 · The draft record EU · optional
The same first scan already drafted your GDPR Article 30 record. It is honest about what it can’t know: the data categories are filled in, but the legal calls are marked needs you.
What the record contains, field by field: Understand the record →
6 · Hand it off EU · optional
Forward the draft to your compliance team. Before anything leaves, Regixo shows you exactly what will be sent — metadata only — and asks you to confirm.
“Forward my Regixo draft record to our compliance team. Show me what would be uploaded before you send it.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo inviteThis one asks before it sends. It previews exactly what leaves the machine — table and column names, types, owners; never a row value — and waits for a yes.
Check it worked: you get a DRAFT PDF and a claim link your compliance team opens with no account. Your agent must show you that preview and get your word first — the playbook tells it never to assume consent. If it sent without asking, say so.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
▸ this will upload a metadata-only snapshot. What leaves: · table & column names, types, owners ✓ leaves · your row values ✗ never ? Send this snapshot? [y/N] y ✓ RoPA_DRAFT.pdf written — forward it to your compliance team ✓ claim link: https://app.regixo.com/claim/clm_7Q…
Read it before you send it — regixo serve-claim
The draft is built from your table and column names, and you are about to put it in front of your
compliance team. It is worth reading first — a table name can say more than you expect, and this is
the moment to notice. regixo serve-claim opens the record they will read, on the
hosted portal’s own page, from your machine, with nothing sent:
“Show me the record my compliance team will read, before I send it.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo invite --no-upload # draft it — send nothing $ regixo serve-claim # read what they'll read
The order is the point. regixo invite on its own uploads (it asks you
first, but a preview you run after sending is not a preview). --no-upload builds
the very same draft and sends nothing — so you read it, and then decide.
Check it worked: a browser opens on the record. Read the Your privacy
line: it tells your compliance team, in their own words, that only names and types left your machine
and no row values, ever. Read and expand anything — but nothing can be saved, signed or
sent from here, and clicking a control says so. When it reads right, run regixo invite
to send it.
Show what it prints in the terminalHide the terminal outputShow what your agent reportsHide what your agent reports
▸ starting the claim preview on port 4320… press Ctrl+C to stop.
✓ Claim preview serving at http://localhost:4320/claim/clm_7Q… (the record they will read)
↳ read and expand anything. Nothing can be saved, signed or sent from here.
↳ the record is what they will read; the sign-in and unlock steps belong to the hosted portal.
↳ reads right? send it with `regixo invite`.What the hand-off sends, and what your compliance team receives: Claim & review →
7 · Claim & fill the legal calls compliance team
Your compliance team opens the claim link, signs in with a one-time email link, and the record opens. They make the calls only a human can: a lawful basis for each activity, retention, special-category grounds, and any DORA contract data. Regixo suggests; a person decides and confirms.
Every legal field, the real Art. 6/9/10 options, and how to choose: Fill the RoPA → · financial firms: The DORA register →
— in the dashboard: this all happens in the browser, no install. The full screen-by-screen tour: The compliance portal →
8 · Unlock & sign compliance team
When the calls are made, unlock to turn the draft into a signed, defensible official record. The price is published and worked out from two answers.
What signing does, the seal, and re-signing when things change: Unlock, sign & maintain →
— in the dashboard: Unlock & pay then Sign & seal are portal screens. See them: The compliance portal →
9 · Re-sign when things change compliance team
The same regixo watch that keeps your map fresh also flags any signed activity
whose core fields moved — so your compliance team can re-sign and the record stays defensible. The
team’s fills also come home to the engineer’s machine.
Re-signing, the change log, and the fills coming home: Unlock, sign & maintain →