Frozen Peak Solutions

Notebook

Notes, databases and whiteboards in one folder of plain files

Notebook brings notes, databases, whiteboards and evidence boards together, with links between all of them, in a folder of plain files that Obsidian can also open. It works offline, it never rewrites what you did not change, and every action is open to scripts and other programs.

See what it holds See what works today

In development. notebook works today as a command-line program, a C API, a server for AI agents and a desktop program. Databases, whiteboards and evidence boards are planned. Nothing is released yet.

What it promises

Your knowledge, in files that stay yours

Each promise below is part of the design, written down before the code. Next to each one is what exists on 15 October 2026.

  • Your files, in your folder

    Everything you create is a plain file in a folder you choose: Markdown notes with YAML properties, and documented JSON for databases and boards. Any sync service or Git can carry it, and you can read it without our software.

    Today notebook works on a folder of Markdown notes and attachments. Its index is a cache in your user folder, never in the vault, and can be deleted at any time.

  • Obsidian vaults open as they are

    Notes, links, properties and attachments written by Obsidian are read without conversion, and our notes open in Obsidian. Boards import and export JSON Canvas.

    Today Wiki links, embeds, Markdown links and links in properties resolve as Obsidian resolves them. The Markdown parser reads Obsidian's syntax and is tested with all 652 CommonMark examples.

  • Editing is never lossy

    A change to one property, one link or one board element rewrites only the bytes that change. Unknown properties and syntax survive every save, and a save never overwrites a newer change made by another program.

    Today Setting a property changes only its bytes, writing a note refuses to overwrite a newer version, and a rename that meets a changed file writes nothing. The editor merges another program's changes into the text you have not saved and shows each clash.

  • Everything links to everything

    A note links to a board or to one element on it, a board card shows a note, a database row can be a note, and the graph view shows every link, whatever kind of item it starts or ends in.

    Today Links, backlinks and unresolved links across the whole vault, and Obsidian's graph as data: the library computes the graph of 10 000 notes and 50 000 links in 7 ms. Moving a note rewrites every link it would break.

  • One query language

    Full-text search with Obsidian's query syntax, and SQL over one documented set of views for query blocks, database filters and formulas, in notes and on boards alike.

    Today Full-text search with Obsidian's operators and regular expressions finds a word in every one of 100 000 notes in 47 ms, and SQL runs over documented views of the vault, in query blocks inside notes too.

  • Offline, and open to programs

    Everything works offline, and sync is optional. Every action of the desktop program is an operation that scripts and other programs reach through the C API, the command line and packages for other languages.

    Today 127 operations work through the notebook command-line program, its C API and its server for AI agents, on Windows and Linux, and the desktop program runs on the same operations.

What it holds

Four kinds of content, linked to each other

A note can link to a board or to one element on it, a board card can show a note, a database row can be a note, and one query can list all of them.

  • Notes

    In development

    Markdown files with YAML properties, wiki links, embeds, tags and block anchors, with backlinks, full-text search, SQL and query blocks, graph data, a reading view, templates and daily notes, and export as a static website, edited in live preview in a desktop program on Windows and Linux.

  • Databases

    Planned

    Tables with a typed schema, whose rows live in the database file or come from notes, shown as table, board, list, gallery, calendar and timeline views with filters, formulas, relations and rollups.

  • Whiteboards

    Planned

    An infinite canvas of shapes, text, connectors, images, note cards and embedded diagrams and queries, with shapes from shape libraries that are plain data files.

  • Evidence boards

    Planned

    Boards whose cards carry typed properties such as person, place, event and document, with dates and sources, relationship types and a timeline layout.

The roadmap shows the order in which they arrive: the desktop program first, then databases and boards.