📊 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’s architecture centers on using on-disk JSON files as the definitive data source, enabling a portable, restartable, and interoperable project management system. This approach challenges traditional server-based models and emphasizes local control.
Threlmark’s core architectural innovation is its reliance on local disk storage as the contract for all project data, eliminating the need for a server or cloud database. The system uses a Next.js app layered on plain JSON files stored on the user’s disk, making the data portable, restartable, and accessible without lock-in. This approach fundamentally shifts how project management tools can operate, emphasizing local control and interoperability.
Threlmark’s design centers on the principle that the disk is the authoritative source of all project data. Its directory structure includes a manifest file (threlmark.json), dependency graphs (links.json), and project-specific folders containing metadata, lane configurations, and individual cards stored as separate JSON files under items/. Shared cards are stored in a top-level directory, while archived projects are moved to an archive directory. This file-based approach ensures that every artifact is inspectable, portable, and compatible with any tool that can read and write JSON.
The system eschews traditional databases, instead adopting two key patterns to ensure safety: atomic file writes via temporary files and rename operations, and read-merge-write updates that preserve data integrity and forward compatibility. The self-healing nature of the lane ordering, which reconciles the actual set of items with the project’s view on each read, prevents inconsistencies and race conditions, enabling external tools to modify project data without conflicts.
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-based project management software
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 Data Storage in Kotlin: Managing Databases in Android Environments (The Android Developer's Playbook)
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.
disk-based JSON file editors
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.
USB 2.0 High Speed Laptop USB to USB PC Data File Transfer Cable Link Direct Copy Between 2 Computers for XP,Vista,Windows7,8 (32/64 bit),win10
High Speed: This is high-speed USB 2.0 chip,the actual test speed is about 480Mb/s (the actual speed also…
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 Local-First Design Changes Project Management
This architecture offers significant advantages for users seeking control over their data, as it removes reliance on external servers and cloud services. It enhances portability, allowing projects to be backed up, migrated, or integrated with other tools easily. The safety mechanisms reduce the risk of corruption during concurrent edits, and the open format encourages interoperability, fostering a more flexible ecosystem for project management and AI integration. Overall, this approach challenges the prevailing cloud-centric models, emphasizing local ownership and resilience.
The Evolution of Project Data Storage and Threlmark’s Approach
Traditional project management tools often depend on centralized servers or cloud databases, which can limit control and portability. Threlmark’s approach builds on the idea of local-first design, previously explored in other tools, but distinguishes itself through its strict file-based system and the principle that the disk is the contract. This design decision aligns with trends toward user sovereignty over data and interoperability, and it responds to limitations of conventional cloud-dependent systems that can introduce latency, lock-in, and data sovereignty issues.
Thorsten Meyer’s detailed explanation highlights that the key innovation is the use of one JSON file per item, with a self-healing lane structure, enabling external tools to participate seamlessly. This design also facilitates AI integration, as the AI can directly read and modify project files without needing a separate API or database layer.
“The on-disk layout is the API. That one choice cascades into everything else—how concurrency is handled, why there’s one file per card, and how external tools can participate without permission.”
— Thorsten Meyer
Unanswered Questions About Threlmark’s Scalability and Adoption
While the architecture is well-defined, it remains unclear how well Threlmark performs with very large projects or in collaborative environments involving multiple users simultaneously. It is also not yet confirmed how external tools and AI agents will be adopted at scale, or how the system will handle complex conflict scenarios beyond the current self-healing lane logic. Further testing and community feedback are needed to evaluate these aspects.
Next Steps for Threlmark’s Development and Community Engagement
Thorsten Meyer plans to release more detailed documentation and developer tools to facilitate external integrations. Future updates may include enhancements to concurrency handling, user collaboration features, and broader AI support. Community testing and feedback will be crucial to refine the system’s scalability and usability, with the goal of establishing a robust, open ecosystem around this local-first approach.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes via temporary files and renaming, along with read-merge-write updates that preserve data integrity even during concurrent modifications.
Can external tools modify Threlmark data?
Yes, since all data is stored in plain JSON files, any tool capable of reading and writing JSON can participate, enabling interoperability and external integrations.
What are the advantages of a local-first architecture?
It offers greater control over data, simplifies backup and migration, reduces dependency on external servers, and enhances resilience against outages or lock-in.
Is Threlmark suitable for large or collaborative projects?
While the architecture supports safety and portability, its performance and conflict resolution in large-scale or multi-user environments are still being evaluated.
Source: ThorstenMeyerAI.com
