Regixo

Free, local-first data catalog. One command, about 5 minutes, no Docker, no signup. Raw data never leaves your machine — the scanner reads names and types, never the values.

Run Regixo by talking to your coding agent, or type the commands yourself — same commands, your choice. Nothing to install or register for that. Once your data is mapped, your agent can read the map too — register the local, read-only regixo mcp server once.

From that same scan it drafts your EU compliance evidence — a GDPR Article 30 RoPA and a DORA register. The DRAFT is free; signing and OFFICIAL export are the paid layer.

npx regixo start

Regixo finds the sources you configure (from DATABASE_URL and friends), reads metadata only (table/column names, types, owners — never row values), flags the columns that hold personal data and shows how it recognised each one, and writes a DRAFT of the GDPR Article 30 record. Then:

npx regixo open      # the free portal: map · record (+ DORA register, if in scope) — localhost:4319
npx regixo invite    # a forwardable DRAFT PDF + claim link for your compliance team — uploads a metadata snapshot; --no-upload keeps it local
npx regixo add       # connect more sources — SQL, warehouses, Stripe, dbt, CSV
npx regixo watch     # re-scan on a schedule; append-only change log; re-sign flags

Process data on a client's behalf? Declare it (actsAs in regixo.yml) and Regixo drafts the GDPR Article 30(2) processor record as well — its own record, organised per client, carrying no purpose, lawful basis or retention, because those are your client's calls on their own record. Nothing about the scope is inferred, and signing that record is not built yet.

Connectors: Postgres · MySQL · SQL Server · Redshift · Snowflake · BigQuery · Stripe · dbt · CSV. How far each one is proven:

• Verified end-to-end against real databases — Postgres, MySQL, SQL Server.
• Fixture-tested, never run against a live account — Snowflake, BigQuery, Stripe.
• Reuses the Postgres driver, never pointed at real Redshift — Redshift.
• CI does not yet run the remote connectors, so they are unguarded against regressions.

Need another source? Your coding agent can author a connector for it — regixo connectors.

Every command runs headless with --json and coded errors — scripts and coding agents can drive it without a human at a prompt. Node ≥ 22.18 is the only prerequisite.

The honest split

• Mechanical facts (what data exists, where it flows) are auto-filled and traced to the schema they came from.
• Legal judgments (purpose, lawful basis, retention) are suggested and marked needs you — no code path can confirm a legal field. A human always signs.
• Who has to keep it. GDPR Article 30 requires this record, and Art. 30(5) exempts firms under 250 persons unless any one of these is true: the processing is likely to result in a risk to people's rights and freedoms, it is not occasional, or it involves special-category or criminal-offence data.

The free product is complete and free forever. Paid (published pricing: €6k / €12k / from €18k per year) adds only defensibility: the signed, offline-verifiable OFFICIAL record and the validated DORA xBRL-CSV export.

Pre-1.0, and not yet on sale. The hosted portal has not launched and nothing is purchasable — the price is published because it will never be "contact us", not because you can buy today. The links below go live when the repository is made public.

• Source & issues: https://github.com/regixo/regixo
• Security policy: https://github.com/regixo/regixo/blob/main/SECURITY.md
• License: AGPL-3.0-only