Documents to ClickHouse, at any volume

How it works

1. 1

   Connect ClickHouse once

   Create a role with insert rights on one schema and paste its credentials into Holofin. Holofin creates the table on the first load; nothing else in ClickHouse is visible to it.

2. 2

   Send documents the way you already do

   Upload in the app, forward by email, or post to the API. Holofin classifies each file, splits bundles into documents and reads the fields of each type.

3. 3

   Query the rows

   Each field lands as one row with its confidence, the page it came from and a needs_review flag. Join it to your own tables in ClickHouse like any other source.

How the ClickHouse connector writes

The only grant Holofin needs:

CREATE USER holofin_loader IDENTIFIED WITH sha256_password BY '...';
GRANT INSERT, SELECT ON extracted.document_fields TO holofin_loader;

The table Holofin writes

One row per field, so a new document type never changes the table. The same columns exist in every warehouse; types follow ClickHouse's own names.

Query it in ClickHouse

Review rate and median confidence per document type over 30 days, with countIf and quantile:

-- Review rate per document type over the last 30 days
SELECT
    document_type,
    uniqExact(document_id) AS documents,
    round(countIf(needs_review) / count(), 3) AS review_rate,
    quantile(0.5)(confidence) AS median_confidence
FROM extracted.document_fields FINAL
WHERE loaded_at >= now() - INTERVAL 30 DAY
GROUP BY document_type
ORDER BY documents DESC

Security

• Documents are processed in Europe, on OVHcloud servers in France certified ISO 27001.
• Holofin only ever writes to the schema you grant. It cannot read your other tables.
• Retention of the source files in Holofin is set per organization, from zero data retention to indefinite. Rows in your warehouse follow your own policies.
• GDPR: Holofin acts as your processor. No document leaves the European Union.