Skip to Content
Open-source data governance platform

Find it.Protect it.Use it.

Classifyre finds personal data and secrets across the systems you already run, masks them automatically, and lets your team query everything with SQL, Excel and Power BI. Every read is logged. Nothing leaves your servers.

No signup. One Docker command. Your data stays with you.
Classifyre
SELECT * FROM crm.customers
Person · 0.97nameredacted
IBAN · 0.99ibanlast four
Email · 0.98emailhashed
Secret · 0.96api_tokenhidden
Anna BergerredactedAT61 1904 3002 3457 3201••••3201anna@example.at5fc7613cacc41469tok_7Qe2x9
Lukas HoferredactedAT48 3200 0000 1234 5864••••5864lukas@example.at8169dd18e1635846tok_m81Kp3
Marie NovakredactedDE89 3704 0044 0532 0130 00••••3000marie@example.de8a84971c7a971d8atok_x0Pd5a
Jonas WeberredactedAT02 2011 1000 0123 4567••••4567jonas@example.org2f122056582e0a94tok_Zt4w8c
Read as

1 column hidden. Personal columns are masked inside the query. The token column is hidden.

  1. ConnectIceberg tables via S3
  2. DetectAWS key found · 0.96
  3. GovernSecret hidden
  4. GrantRequest approved
  5. Shareorders + customers
  6. Connect BIExcel · own login
  7. LogAgent read · MCP
Start here
docker run -d --name classifyre \  -p 3000:3000 \  --shm-size=1g \  -v classifyre-pgdata:/var/lib/postgresql/data \  -v classifyre-data:/var/lib/classifyre \  -v classifyre-uv-cache:/cache/uv \  classifyre/all-in-one:0.9.0
The problem

Your data is useful. It is also full of personal data.

Every team wants the numbers. Every table that holds them also holds names, accounts, addresses and the odd password. So access becomes a negotiation, and the negotiation ends in a spreadsheet.

The Classifyre investigator in a trench coat, scratching his head over an unanswerable question mark
Fig. 01: six systems, personal data in all of them, no line between who may see what
  • Field note 01

    Who can see this column?

    Finance asks for the customer database. Which of its 212 tables hold personal data? Nobody knows, so the ticket waits, or everyone gets everything.

  • Field note 02

    Just send me the export

    Data leaves by CSV and shared database passwords. Six copies later nobody can say where the customer list lives, or who still has it.

  • Field note 03

    Prove it to the auditor

    Who read the payroll tables last quarter, with which tool? Without a log of every read, the honest answer is: we don't know.

The problem

It is the same shape every time: useful data locked away because nobody can say what is personal in it, or handed out whole because nobody had time to say no. Masked by default, granted on purpose, every read on record: that is the way out.

Reads 40+ systems in place · never copiedBrowse the source catalogue →
Custom Connector
Sandbox
WordPress
Slack
S3-Compatible Storage
Azure Blob Storage
Google Cloud Storage
PostgreSQL
MySQL
Microsoft SQL Server
Oracle
Apache Hive
Databricks
Snowflake
Dremio
MongoDB
Neo4j
Power BI
Tableau
Confluence
Jira
Jira Service Management
Notion
Email
YouTube
Reddit
Iceberg REST Catalog
DuckLake
Trino / Starburst
ODBC
Amazon Athena
Google BigQuery
Amazon Redshift
Apache Kafka
Elasticsearch
OpenSearch
Meilisearch
Mounted Folder
Microsoft 365
Google Workspace
Dropbox
Hugging Face
Git Repository
Custom Connector
Sandbox
WordPress
Slack
S3-Compatible Storage
Azure Blob Storage
Google Cloud Storage
PostgreSQL
MySQL
Microsoft SQL Server
Oracle
Apache Hive
Databricks
Snowflake
Dremio
MongoDB
Neo4j
Power BI
Tableau
Confluence
Jira
Jira Service Management
Notion
Email
YouTube
Reddit
Iceberg REST Catalog
DuckLake
Trino / Starburst
ODBC
Amazon Athena
Google BigQuery
Amazon Redshift
Apache Kafka
Elasticsearch
OpenSearch
Meilisearch
Mounted Folder
Microsoft 365
Google Workspace
Dropbox
Hugging Face
Git Repository
How it works

From a raw table to a shared dataset.

Follow the data through Classifyre: found where it lives, queried in place, governed, used in the tools your team already has, masked for the people who should not see it, and shared on purpose.

  1. 01Connect & detect

    Find personal data and secrets where they live

    Connect databases, lakehouses, buckets and SaaS tools; Classifyre reads them in place, so nothing is copied into another warehouse. Built-in detectors look for 41 kinds of personal data, including Austrian, German and Swiss identifiers, and 27 kinds of secrets. Add your own with a regex, a model or a prompt.

    Every finding comes with a score and a written reason, so a data protection officer can check it and a security team can rank the cleanup. The classification it produces is what the masks follow later.

    • 40+ source types
    • 41 PII entities · 27 secret patterns
    • A score and a reason on every finding
    See the detector packs →
    Scan · 3 sources
    • crmPostgreSQL
      Scanned
    • wikiConfluence
      Scanned
    • exportsParquet in S3
      Scanned
    Findings, ranked
    • IBANcrm.customers.iban · Valid checksum in 4,211 of 4,215 rows0.99
    • AWS access keywiki / Deploy notes · Key and secret on the same page0.96
    • AT SVNRexports/2026-10.parquet · Check digit valid, column named svnr0.93
    • Emailcrm.tickets.body · Addresses in free text, 312 tickets0.81

    crm.customers.iban classified as Personal · masked from the next query

    Personal data found across three sources, ranked with reasons.
  2. 02Query across sources

    Query every system with one SQL statement

    Ask questions across the systems you already have: PostgreSQL, MySQL, Databricks, and Delta, Iceberg and Parquet files in S3, Azure or Google Cloud Storage. Join up to eight sources in one query. Each query runs next to the data; nothing is loaded into a central store first.

    Results go where people work: the SQL page, exports to Excel, CSV and Parquet up to a million rows, or straight into a BI tool.

    • Up to 8 sources in one query
    • Delta · Iceberg · Parquet · CSV
    • Exports up to 1M rows
    Query data →
    Query data
    crm · PostgreSQL
    lake · Parquet in S3
    ▶ Run
    SELECT c.email, c.city, sum(o.amount) AS revenue
    FROM crm.customers c
    JOIN lake.orders o ON o.customer_id = c.id
    GROUP BY 1, 2;
    3 rows · 2 sources joined · email hashed
    emailcityrevenue
    5fc7613cacc41469Graz4,812.40
    8169dd18e1635846Linz1,130.00
    8a84971c7a971d8aWien2,977.15
    A PostgreSQL table joined with Parquet files in a bucket.
  3. 03Governance

    Governance: an owner, a contract and a history for every table

    A governed table has an owner, stewards and a custodian, a classification for every column, and a status from draft to certified. Quality rules check it on a schedule: missing values, invalid IBANs, duplicates, row counts or any SQL you write. The agreement exports as an ODCS data contract.

    Usage shows who reads the table and through which tool; Activity shows every read and every change, old value next to new. When the auditor asks, the answer is already written down.

    • Owners, stewards, custodians
    • Quality rules on a schedule
    • ODCS data contracts
    • Every read and change on record
    Governed assets →
    crm.customers · Governance
    Certified5 of 5 done✓ Certified

    Ownership

    • OwnerGroupFinance
    • StewardGroupData office
    • CustodianGroupIT platform

    Columns

    ColumnClassificationAccess
    ibanPersonal dataMasked · shown as last four
    emailPersonal dataMasked · shown as hashed
    api_tokenSecretHidden

    Quality

    + Add rule
    • email · Missing values = 0
    • Row count ≥ 4,000
    • Check a column · iban · Invalid values ≤ 0.5 %
    Run now0.1 % invalid · passed

    Usage · last 30 days

    Reads
    1,284
    Exports
    37
    Readers
    14

    Through: SQL connections, the app, MCP

    ↓ Export data contract
    apiVersion: v3.2.0
    kind: DataContract
    status: active
    team: [Finance, Data office]
    schema:
    - name: customers
    properties:
    - name: iban
    classification: personal
    quality:
    - type: library
    metric: invalidValues
    mustBeLessThan: 0.5
    Owner, steward and custodian assigned, access set, a quality rule run, the table certified, the contract exported.
  4. 04Power BI & Excel

    Connect Power BI and Excel without a shared password

    Classifyre answers as a PostgreSQL database. Each person creates their own SQL connection, encrypted and expiring, and points Power BI, Excel, Tableau or DBeaver at it. No service account with the keys to everything, no password inside a report file.

    The connection carries the person's own rights: the tables they may query, the rows their group may see, the masks on every personal column. Revoke it and the report stops.

    • A personal connection per tool
    • TLS only, expiring, revocable
    • The read log names the tool
    SQL connections →
    SQL connections · New connection
    Name
    Power BI
    Tables
    crm.customers, sales.orders
    Expires
    in 90 days
    Created
    Server=sql.example.at:5432;Database=finance;User=lena_power_bi;SSL=verify-full
    Customers report · via SQL connection Power BI
    Graz
    Linz
    Wien
    Salzburg
    redacted••••32011,240.00
    redacted••••5864312.50
    redacted••••300088.90

    09:14 · Lena read crm.customers via SQL connection Power BI

    A personal connection, used from a BI report, still masked.
  5. 05Mask per person

    Masked for one person, clear for another

    Personal columns are masked by default: redacted, last four, hashed so tables still join, or hidden. Masks apply inside the query, so a WHERE or a JOIN can't reach past them. Only a group granted Data reader, unmasked reads the clear values, for a source or a single table, with an end date. Admins don't get it by default.

    The hashed mask is pseudonymisation in the sense of the GDPR, not anonymisation: equal values hash the same, so analysts can join and count people without reading who they are. Watch it below: the same queries, run by an analyst and by a finance steward.

    • Masked by default
    • Redacted · last four · hashed · hidden
    • Pseudonymisation, not anonymisation
    • Clear reading is its own grant
    How masking works →
    SELECT city, count(DISTINCT email) AS customers
    FROM crm.customers
    GROUP BY city;
    ▶ Run

    Lena, analyst

    Data reader

    citycustomers
    Graz1
    Linz1
    Wien1
    Salzburg1
    4 rows

    Tom, finance steward

    Data reader, unmasked

    citycustomers
    Graz1
    Linz1
    Wien1
    Salzburg1
    4 rows

    Counts work on masked columns. The answer is useful; the person behind it stays covered.

    Reading masked data is a grant of its own, with an end date, and it is on record.
  6. 06Share

    Share a dataset that joins your sources

    Join tables from different systems into a shared dataset (customers from the CRM, orders from the lake, invoices from finance) and give it to the groups that need it. A shared dataset is a governed, saved query, not a copy: it reads the sources live, and the masks of every input table travel with it as a floor that can only be raised.

    The receiving team queries it like any table, on the SQL page, in Excel or in Power BI, and every read is on record.

    • Joins across sources
    • Masks travel with the data
    • Granted per group, with an end date
    Shared datasets →
    Query data · New shared dataset
    SELECT c.email AS customer, c.city,
    count(o.id) AS orders, sum(i.amount) AS revenue
    FROM crm.customers c
    JOIN lake.orders o ON o.customer_id = c.id
    JOIN finance.invoices i ON i.order_id = o.id
    GROUP BY 1, 2;
    Saved
    Nameshared.sales.customer_revenue
    Regional salesData reader · 90 days
    ✓ Shared
    shared.sales.customer_revenueRegional sales reads it · 3 sources
    5fc7613cacc41469Graz124,812.40
    8169dd18e1635846Linz41,130.00

    Masks kept from the inputs: customer hashed (crm.customers.email)

    Three sources joined into one dataset, shared with a group, masks kept.
When something leaks

This is the part most tools leave to you.

A case, assembling itself
ANALYST LINKDUPLICATE MATCH · SENT FILE = INTERNAL FILECASE #42 · OPENClassified leak via emailHYPOTHESIS 1Sender traced: A. NovakHYPOTHESIS 2214 records exposedEMLIDTAGDUPBY AUTOPILOT
A classified file emailed out: sender traced, impact scoped, duplicate confirmed, every exhibit attributed.
  • EMLThe external email itself: headers, recipient, timestamp
  • IDSender identity resolved across the directory
  • CLASSClassification marking found inside the attachment
  • DUPInternal original confirmed by fingerprint
Walk the real thingshowcase.classifyre.com
Where it lands

The data looks different. The rules are the same.

Classifyre reads whatever the organisation runs on; the sector only decides which columns are personal and who reads them in clear.

  • Public sector · Länder · citiesTypical dataRegisters, case files, statistics, procurementWhat changesDistricts query their own rows, personal columns arrive masked, the DPO reads the log
  • Healthcare · hospitalsTypical dataAdmissions, lab results, staffing, billingWhat changesAnalysts count patients without reading who they are
  • Banking · KYCTypical dataCustomer master, transactions, accountsWhat changesIBANs as last four, hashed IDs that still join, a read log for the regulator
  • InsuranceTypical dataClaims, policies, health declarationsWhat changesActuaries get the tables, not the policyholders
  • BI · analytics teamsTypical dataWarehouses, lakehouses, Delta and Iceberg tablesWhat changesPower BI and Excel on personal connections instead of one shared password
  • Security teamsTypical dataGit, wikis, tickets, buckets, logsWhat changesKeys and tokens found, ranked with reasons, cleaned up first
  • Internal audit · complianceTypical dataAccess logs, payroll, contractsWhat changesWho read which table, through which tool, and when: one filter
  • Incident responseTypical dataMail, drives, databasesWhat changesOne fingerprint across systems, worked as a case

Each row is a starting point, not a separate product: the same masks, grants and read log underneath.

Your move

Open your data safely tonight.

Point it at one database you already run. By the morning you know which columns hold personal data, and your team can query the rest. Everything you set up carries over when you go to Kubernetes.

One command tonight. The same core at scale.

The all-in-one image has the database, the UI and the scan workers in it; everything stays on your machine. The Helm chart runs the same core on Kubernetes when the estate grows.

All-in-one image · free · no signup
docker run -d --name classifyre \  -p 3000:3000 \  --shm-size=1g \  -v classifyre-pgdata:/var/lib/postgresql/data \  -v classifyre-data:/var/lib/classifyre \  -v classifyre-uv-cache:/cache/uv \  classifyre/all-in-one:0.9.0
Helm chart · scales to any size

Or run it on Kubernetes

Ephemeral scan and query workers scale to zero between runs and fan out as far as your estate goes. Your cluster, your data.

helm install classifyre \
  oci://registry-1.docker.io/classifyre/classifyre-core \
  --version 0.9.0
  1. Tonight, on your machine

    One Docker command. Sources, masks and the read log stay local.

  2. At scale, on Kubernetes

    The same core as a Helm chart: workers scale to zero between runs.

  3. When it becomes infrastructure

    Your team or your integrator runs it. Enterprise tailors it to your organisation, adds OpenShift and an SLA. Every feature is already open source.

Straight answers

Questions people actually ask.

More detail lives in the docs · docs.classifyre.com