About Diaryx

Open infrastructure for personal memory. #

What you remember shouldn't depend on whether a company stays alive. Diaryx is an organization building open formats, verifiable files, and software anyone can inspect — and the Diaryx app is where that philosophy becomes something your family can hold.

Open source Every core engine is MIT / Apache-2.0 and public
Plain files Markdown and YAML in folders you control
Local-first Nothing leaves your machine until you say so
The stack

One app, standing on open engines. #

The app is the only closed layer, and it is deliberately the thinnest one. Everything that touches your files — parsing, structure, identity, editing — is an open project anyone can use without us.

Engines
prov the workspace: relations, identity, fixity leaf the rich-text editor over twig's tree flower the structural editor over fig's tree
Foundations
twig documents: Markdown, Djot, HTML — losslessly fig config: YAML, TOML, JSON — losslessly

Each layer only ever edits through the one below it, so every change to your files is a lossless splice — and each project is usable on its own, with no Diaryx anywhere in sight.

Projects

Everything underneath the app is a project of its own. #

prov Rust

Plaintext Records, Organized and Verifiable — the self-describing workspace engine behind Diaryx: documents, relations, identity, fixity.

About prov →
fig Zig

Lossless parsing and editing of config files — YAML, TOML, JSON, ZON — down to every comment, key order, and blank line.

About fig →
twig Zig

A round-trippable document AST for Markdown, Djot, and HTML — parse once, edit precisely, write back exactly what you mean.

About twig →
leaf Rust · Swift

A caret-based rich-text editor over twig's AST — one editing core, from terminal to iOS to the browser.

About leaf →
flower Rust

A structural editor for config files: navigate the parsed tree, edit one value at a time, never hold an invalid document.

About flower →
historica Rust

Convergent version control where the readable files are the authority — history as documents, not a database. It carries what Diaryx publishes, and what readers send back.

About historica →
historica-remark Rust

A reader's remarks on a chain, and the layer that carries them home — lifted out of the app so the annotation model is usable without any of it.

On GitHub →
How we work

Plain files win. #

Everything we build stores its work as Markdown, YAML, and ordinary bytes in folders you own. No opaque containers, no export button to hunt for.

Durability is a practice. #

Content hashes that prove nothing drifted, identifiers that survive renames, structure written into the files themselves — techniques borrowed from professional archives, not invented for an app.

If it matters, it's open. #

The engines are MIT/Apache-2.0 and world-readable. If we vanished tomorrow, everything you keep would still be there, still readable — which is rather the point.

See what it's all for. #

The app is free on iPhone, iPad, and Mac — and every engine under it is on GitHub.