📊 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 project management system where disk-stored JSON files serve as the definitive data source. This design emphasizes portability, safety, and interoperability without relying on servers or databases. The approach enables external tools and AI agents to participate seamlessly.
Threlmark has announced a novel architecture that treats disk-stored JSON files as the definitive source of project data, eliminating the need for servers or databases. This approach enables a fully local, portable, and interoperable system that external tools and AI agents can participate in without permission or lock-in, marking a significant shift in project management design.
The core design choice in Threlmark’s system is that all project data resides in plain JSON files stored on the user’s disk, with the on-disk layout serving as the API. This means that every artifact—such as project metadata, roadmap items, and external suggestions—is stored as individual files, enabling direct inspection, diffing, and version control. This file-based approach removes the reliance on centralized servers, promoting portability and resilience.
The system is built around two key principles: first, the data is open and portable, allowing users to back up, migrate, or sync their project data with any tool that can read and write files. Second, it is restartable; since the state is stored solely on disk, the system can recover from crashes without losing data. These principles are enforced through careful design patterns like atomic file writes—writing to a temporary file and renaming it atomically—and read-merge-write updates that preserve data integrity and forward compatibility.
The architecture also includes mechanisms for external tools and AI agents to interact seamlessly. For example, each roadmap item is stored in its own JSON file, which external agents can modify or move without conflicts. The lane ordering is maintained separately in a self-healing ‘board.json’ file, which reconciles itself with the actual items on each read, ensuring consistency even if external modifications occur.
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.
JSON file project management tools
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.local-first project management software
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.
file-based project tracking system
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.
version control for project files
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-Based Architecture Transforms Project Management
This approach fundamentally changes how project data is managed and shared. By removing server dependencies, Threlmark enhances data portability, allowing users to easily back up, migrate, or integrate with other tools without vendor lock-in. The file-based model also improves resilience, as data recovery is straightforward and atomic operations prevent corruption. Furthermore, this design facilitates external automation and AI integration, enabling smarter, more autonomous workflows. Overall, it offers a more transparent, flexible, and robust foundation for managing complex projects across multiple tools and environments.
Background of Threlmark’s Local-First Design Philosophy
Traditional project management tools often rely on centralized servers or cloud databases, which can create barriers to portability, pose security concerns, and introduce single points of failure. Threlmark’s design draws inspiration from local-first principles seen in other applications, emphasizing user control over data and resilience against connectivity issues.
Prior to this architecture, most tools used monolithic JSON files or cloud-based databases, which limited external participation and complicated data migration. Threlmark’s shift to a file-based, serverless model aims to address these limitations by making the data itself the contract, accessible directly on disk, and compatible with any tool capable of reading and writing JSON.
“The core idea is that the disk is the contract. There’s no server, no database—just files that serve as the single source of truth.”
— Thorsten Meyer, creator of Threlmark
Unresolved Questions About System Scalability and Collaboration
It is not yet clear how well this architecture scales with very large projects or numerous concurrent external modifications. While atomic file operations and self-healing mechanisms promote safety, the impact on performance and conflict resolution in highly collaborative environments remains to be tested extensively. Additionally, the user experience of managing many individual files versus traditional centralized views is still evolving.
Next Steps for Adoption and External Tool Integration
Threlmark plans to continue refining its file-based protocols, potentially developing standardized APIs for external tools and AI agents. Broader adoption by users and integrations with other project management ecosystems will provide more data on scalability and usability. Future updates may include enhanced conflict resolution features and user interface improvements that better visualize the file-based data structure.
Key Questions
How does Threlmark handle concurrent edits from multiple external tools?
It uses atomic file writes and read-merge-write patterns to prevent conflicts, ensuring each update is safe and consistent.
Can I migrate existing project data into Threlmark’s system?
Yes, since data is stored as plain JSON files, you can back up, transfer, or modify your data directly without vendor lock-in.
What are the limitations of a disk-based, serverless architecture?
Potential challenges include handling very large projects efficiently and managing conflicts in highly collaborative environments, which are areas for ongoing development.
How does this approach compare to traditional cloud-based project tools?
It offers greater data control, portability, and resilience, but may require more manual management and local storage considerations.
Source: ThorstenMeyerAI.com
