📊 Full opportunity report: Disk Is the Contract: Inside Threlmark’s Local-First Architecture on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark introduces a local-first, disk-based architecture where JSON files on disk serve as the system’s core data store. This approach enables portability, inspectability, and restartability without relying on a server or database.
Threlmark’s latest architectural approach treats disk-stored JSON files as the definitive record for project data, eliminating the need for a server or database. This design choice, confirmed by Thorsten Meyer, enables a portable, restartable, and interoperable system for managing multi-project roadmaps without lock-in or cloud dependencies.
Threlmark is a multi-project roadmap tool that relies solely on JSON files stored on disk, with the on-disk layout serving as the API and source of truth. This approach removes the need for a central server or database, making the data portable and open for external tools to join. The core files include a manifest (threlmark.json), project metadata, project-specific items, and shared items, all organized in a structured directory hierarchy. The system employs atomic writes—writing to temporary files and renaming—to ensure data integrity even in crashes, and uses read-merge-write cycles with tolerant normalization to maintain compatibility and forward-compatibility. The design also features a self-healing board that reconciles its state against the actual files each time it is read, ensuring consistency without locks or complex concurrency controls. This architecture emphasizes inspectability, portability, interoperability, and restartability, all achieved by avoiding a traditional database layer.Disk is the contract: inside a local-first roadmap hub
A Next.js app on top of plain JSON files — no database, no cloud, no accounts. The key decision: the on-disk layout IS the API. Everything else cascades from taking that seriously.
There is no server-of-record — the files are the record
The UI and any external tool reach the same files through the same discipline. The data root defaults to ~/.threlmark — home-based, because it’s a shared hub every one of your apps points at.
Inspectable
Every artifact is a file you can cat, diff, grep, commit.
Portable · no lock-in
Back up with cp, sync with Dropbox / git, migrate trivially.
Interoperable
Any tool in any language joins by reading / writing files.
Restartable
No in-memory state to lose — stateless over the files.
portable JSON file editor
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Two disciplined patterns instead of a database
“Just use files” is easy to get wrong. These two patterns — ported from a battle-tested sibling app — are what make file-based state sound rather than reckless.
Atomic writes
Write to a temp file in the same dir, then rename() over the target. Rename is atomic on one filesystem — a crash mid-write leaves the complete old file or the complete new one, never a half.
The board heals itself
A single roadmap.json array races when two tools write at once. One file per card makes writes collision-free. Lane order lives in board.json and reconciles on read.
board.json. It writes an item file — the board fixes itself on Threlmark’s next read. Unknown keys are preserved, so the contract is forward-compatible.disk-based project management tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The numbers can’t drift from the files
Anything computable from item state is computed — so the displayed numbers can never disagree with the underlying JSON. Priority is the clearest example: it’s calculated on read, never persisted.
priority — computed on read
Impact weighted heaviest; effort the only axis that subtracts. Reused verbatim from the original tool, so imported cards rank identically.
local-first data storage software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A handoff is a first-class flow event
The genuinely 2026-shaped part: most building is done by AI agents, so Threlmark closes the loop. Watch a card go from ranked to Done without anyone dragging it.
Handoff → report → self-move
The brief carries a reporting protocol. The agent reports through REST or the filesystem — and a done report moves the card itself.
POST /api/projects/:id/
items/:itemId/reportDirect call. Applied immediately.
drop reports/.json
→ ingested on read Robust even if the server’s down at finish time.
JSON file version control tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A small formula, and an honest hosting caveat
Because items are globally addressable (
Portfolio ranking — status-weighted
In-flight work floats to the top; bottlenecks cost the most, so blockers get nudged up.
Static read-only demo
Seeded data, writes to localStorage. Try-before-you-clone.
Personal Node instance
Password-gated, persistent backed-up THRELMARK_DATA_DIR.
Multi-tenant SaaS
Add accounts + per-tenant isolation. A separate build.
src/lib/*/store.ts is the natural seam — the same boundary that keeps the local tool simple is the one you’d extend for multi-tenancy. The architecture doesn’t fight that future; it just doesn’t pay for it until you need it.
Why Disk as the Contract Changes Project Management
This architecture shifts the paradigm of project management tools by removing reliance on centralized databases and cloud services. It empowers users with full control over their data, enhances portability across tools, and simplifies backups and migrations. For developers, it offers a transparent, conflict-free way to extend and integrate the system, fostering an open ecosystem. For organizations, this approach can reduce vendor lock-in and improve resilience, as data remains accessible and manageable locally without server dependencies. It also opens possibilities for offline workflows and local automation, which are increasingly valuable in distributed or privacy-conscious environments.
The Evolution of Local-First, File-Based Systems
Traditional project management tools often rely on centralized servers, cloud storage, or databases, which can introduce lock-in, data silos, and dependency on external infrastructure. The concept of local-first systems has gained traction, emphasizing user control and resilience, exemplified by tools like Git, local notes apps, and file-based databases. Threlmark’s approach builds on this trend by using JSON files on disk as the core data store, inspired by battle-tested patterns in file handling and concurrency control. This design aligns with broader movements toward open data, interoperability, and offline-first workflows, offering a practical implementation for multi-project roadmaps that are both robust and flexible. For a deeper dive into this architecture, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
“The on-disk layout is the API. That choice cascades into how concurrency is handled, why there’s one file per card, and how external tools can participate without permission. For more details, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.”
— Thorsten Meyer
Remaining Questions About Threlmark’s Architecture
While the design principles are clearly articulated, it is not yet confirmed how well this approach scales with very large projects or numerous concurrent external tools. Additionally, the user experience and performance implications of managing many JSON files in complex workflows remain to be fully tested in real-world scenarios. The system’s handling of conflicts and synchronization in multi-user environments also requires further exploration.
Next Steps for Threlmark’s Local-First System
Thorsten Meyer and the Threlmark team are expected to release more detailed documentation and possibly open-source the implementation, allowing the community to evaluate, extend, and test the architecture. Future updates may focus on performance optimizations, multi-user collaboration, and integration with external tools. Monitoring how the system performs in diverse environments will be crucial to understanding its broader applicability.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to temporary files and renaming them—to prevent corruption during crashes, ensuring data integrity.
Can external tools easily join Threlmark’s system?
Yes, because the data is stored in open, portable JSON files, any tool that can read and write JSON can participate without permission or complex integration.
What are the benefits of using disk files as the system’s API?
This approach makes the data inspectable, portable, interoperable, and restartable, reducing lock-in and increasing user control.
Is this architecture suitable for large or multi-user projects?
This remains to be tested; scalability and multi-user synchronization are areas for future evaluation.
Will Threlmark’s approach support offline workflows?
Yes, since all data resides locally on disk, offline use is inherently supported, with synchronization as needed.
Source: ThorstenMeyerAI.com
