📊 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 makes disk storage the primary data contract, eliminating databases in favor of file-based persistence. This approach improves offline capabilities, data portability, and system transparency, with some challenges in concurrency management.
Threlmark has adopted a novel architecture in which disk storage is treated as the definitive source of truth, moving away from traditional database reliance. This approach is detailed in the original analysis. This design allows for simplified synchronization, better offline usability, and enhanced data portability, making the system more resilient and transparent, according to the company.
Threlmark’s approach centers on storing all data directly on disk as plain files, with each item represented by a separate file. This eliminates the need for a central database or server, allowing users to edit files directly and see immediate updates across tools. The system employs atomic file writes to prevent corruption during crashes and uses tolerant merge strategies to handle concurrent edits, ensuring data integrity without locking mechanisms.
The directory structure itself acts as a formal data contract, defining how data is organized and accessed. This transparency allows external tools to read and modify files without special permissions, fostering interoperability. The architecture also includes self-healing mechanisms, enabling the system to reconstruct state from individual files if inconsistencies occur.
While this approach simplifies deployment and enhances portability, it introduces challenges in managing many small files and resolving conflicts from simultaneous edits. Developers must carefully design directory layouts and update logic to balance performance and simplicity.
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.
offline file-based data storage solutions
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.![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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.
Advanced Organizing Systems – The VFile37/VFolder37 Vertical Flat Storage for Easy Efficient Access of Documents up to 24”x36”. (Includes 8 VFolder37’s)
MADE IN THE USA: Responsive USA Customer Support; GSA Compliant
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.
Offline-First Apps: Mastering Progressive Web Apps (PWA): Build fast, reliable web applications that work anytime, anywhere (even without internet)
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.
Implications of Disk as the Single Data Source
This architecture shifts the focus from centralized databases to file integrity and synchronization, offering greater transparency, offline resilience, and data portability. For a deeper dive, see this detailed overview. It reduces vendor lock-in and simplifies data recovery, making it attractive for users seeking flexible, robust tools. However, it also demands careful handling of concurrency and conflict resolution, which can increase system complexity.
Background and Development of Local-First Design
Traditional project management tools rely heavily on cloud servers and proprietary databases, which can limit offline access and create vendor lock-in. Threlmark’s local-first approach aims to address these issues, as discussed in this article. The local-first movement advocates for storing data locally in plain files, ensuring users retain control and access even without network connectivity. Threlmark’s approach aligns with this trend, emphasizing simplicity, transparency, and interoperability. The concept has gained traction in recent years as users seek more resilient and portable solutions, with Threlmark pioneering this specific implementation.
“Treating disk as the contract simplifies synchronization and makes data more portable and accessible.”
— Thorsten Meyer, Threlmark Developer
Remaining Challenges and Unanswered Questions
It is not yet clear how well the system scales with very large datasets or numerous concurrent users. The performance implications of managing many small files and the effectiveness of conflict resolution in complex scenarios remain to be fully tested. Additionally, the long-term reliability of self-healing mechanisms and manual data recovery methods need further evaluation.
Future Developments and Testing Milestones
Threlmark plans to expand testing of its file-based architecture in real-world environments, focusing on scalability and conflict management. The company aims to develop tools for better conflict resolution and to optimize directory structures for larger datasets. User feedback and performance metrics will guide further refinements, with broader adoption expected in the coming months.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark employs atomic file writes and tolerant merge strategies to prevent corruption and handle concurrent edits, ensuring data integrity.
Can external tools modify Threlmark data?
Yes, the explicit directory structure acts as a contract, allowing external tools to read and write files directly without special permissions.
What are the main tradeoffs of this architecture?
Managing many small files can introduce filesystem overhead and complexity in maintaining data relationships, and conflict resolution in concurrent edits can be challenging.
Is this approach suitable for large-scale or multi-user environments?
While promising for offline and single-user scenarios, scalability and multi-user conflict handling are still under evaluation and may require further development.
Source: ThorstenMeyerAI.com
