Edouard Tardif
FREN

In progress · as of 10 October 2026

Chartrium — document management designed for small law firms

Find a document fast, never lose a version, and be able to show what happened to it.

For whom
Small law firms (4 to 10 lawyers)
Stack
  • Go
  • React + TypeScript
  • PostgreSQL
  • Temporal
  • Apache Tika
All applicationsWrite to me
Chartrium's station, drawn: a document gets filed, its versions stack up, every event is added to the chain.

In figures (as of 10 October 2026)

  • 621

    agent PRs out of 640 merged

    A "PR" (pull request) is a proposed change that is tested, then merged into the software.

  • 720

    closed issues

  • 7.5/10

    average self-reported confidence

Build timeline

From 19/07 to 10/10/2026, twelve weeks. The solid bar is Chartrium; the others show where it sits in the factory.

  1. Chartrium
  2. Merkindium: from 18/08/2026 to 02/10/2026, 440 agent PRs
  3. Recette: from 01/09/2026 to 01/10/2026, 179 agent PRs
  4. Bottrading: from 10/09/2026 to 02/10/2026, 201 agent PRs
  5. Raccourci: from 19/07/2026 to 16/08/2026, 16 agent PRs

18/08/2026 · first merge10/10/2026 · figures snapshot

621 agent PRs out of 640 merged, as of 10 October 2026.

The problem

In a firm of four to ten lawyers, documents live in shared folders, email attachments and USB sticks. Searching takes time, a version gets overwritten, and the day you need to show who saw what, you can't.

Chartrium, home page on fictional data: 21 documents to check, 38 documents filed, 9 deadlines not to miss, 4 active share links

The home page, on fictional data.

The answer

Chartrium rests on three commitments: nothing gets lost, nothing leaks, nothing is invisible.

  • Every document keeps its versions, dated and attributed.
  • Search covers the content of documents, not just their names.
  • A share with someone outside the firm can be revoked, and it is logged.
  • An audit log records every event and cannot be altered afterwards.
  • Each firm is isolated: another organisation gets an explicit refusal.

These journeys are delivered and replayed automatically on every change, from sign-up to restoring a backup.

Three screens

Chartrium, "To check" queue: a fictional document read, the suggested folder and the "File here" button
①The "To check" queue: a fictional document read, the suggested folder and the "File here" button.
Chartrium, a fictional document open with its record and its "Extracted information" and "Versions" tabs
②A document and its record, with its "Extracted information" and "Versions" tabs.
Chartrium, "Who did what, and when" history with its filters and the Export button
③The history: "Who did what, and when", with its filters and export.

Real screenshots on fictional data.

What was hard

A log that cannot be rewritten.

Each event is chained to the previous one by a cryptographic fingerprint. Changing one line breaks the chain, and verification catches it. The log can be exported as a signed file.

A "fingerprint" (hash) is a short value computed from the content: the smallest change alters it.

Building without any secret.

Email and text extraction each have a stub mode: the factory builds and tests everything without holding a single real key. Real services are plugged in through configuration at deployment.

A "stub" is a fake version of a service that answers like it during tests.

An honest roadmap.

End-to-end encryption is designed, documented and under development; it is not available yet.

What is left

End-to-end encryption. Opening the public website. Chartrium is not on sale yet.

Under the hood

A single Go binary embedding the React interface. PostgreSQL for data, Temporal for long-running jobs, Apache Tika to read document text. A core kept separate from enterprise modules. Playwright screenshots of every screen on every PR.