📊 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, file-based architecture that uses JSON files on disk as the sole data source, enabling portable, interoperable, and restartable project management. Its design eliminates servers, promoting openness and resilience.
Threlmark has unveiled a new architecture that relies entirely on JSON files stored locally on disk as the single source of truth for managing multiple projects, without any server or cloud dependency. This approach aims to simplify data portability, interoperability, and system restartability, marking a significant shift from traditional server-based project tools.
The core design decision in Threlmark is that all project data resides in plain JSON files within a dedicated directory, defaulting to ~/.threlmark. This directory contains a manifest (threlmark.json), a dependency graph (links.json), and individual project folders with files like project.json, board.json, and one file per roadmap card in items/. External tools can read and write these files directly, enabling seamless integration and collaboration.
Threlmark emphasizes data safety and concurrency through atomic file writes—writing to temporary files and renaming them atomically—and a read-merge-write cycle that preserves data integrity and forward compatibility. The architecture supports external suggestions, agent handoffs, and report-backs, all managed through a structured folder hierarchy. This setup allows any tool, regardless of language, to join the ecosystem by simply reading or writing files, avoiding lock-in and vendor dependency.
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.
Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON
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.
Real-World Android App Projects with Kotlin and Jetpack Compose: Build Production-Style Android Apps with Modern Architecture, API Integration, State Management, Local Data Storage, Practical Projects
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.
Ciieeo Empty 25-Disc CD/DVD Cake Box Spindle, Clear Plastic Media Storage Bucket with Locking Black Base, Protective Spindle Container for Optical Discs and Data Backup (1-Piece)
25-Disc Capacity Spindle: Features a vertical center post designed to hold up to 25 standard 12cm optical discs,…
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.
Project Planner Notepad – Project Management Organizer Desk Pad – Manage Project Tasks and Meeting Deadlines Effectively – 50 Sheets of Premium 120gsm Paper | Management | A4 Mono
Comprehensive Project Planning: Plan for success with a dedicated project timeline and task sections to track milestones and…
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 a Serverless, File-Based System
This architecture shifts the paradigm of project management tools by removing the need for centralized servers or cloud storage, making data more portable and resilient. It enables users to back up, migrate, and integrate with other tools easily, fostering openness and collaboration. For AI workflows, this design allows agents to operate directly on local data, closing the loop without external APIs or databases, which could streamline automation and reduce reliance on cloud services.
Previous Project Management Limitations Addressed
Traditional project tools often fragment workflows across multiple platforms, with each project maintaining its own list or kanban, making it difficult to ask universal questions like ‘What’s the most important thing to do next?’ Threlmark’s approach consolidates data into a single, portable format, addressing issues of fragmentation, lock-in, and data silos. Its design builds on prior local-first principles but extends them into multi-project management with AI integration.
“The on-disk layout is the API. It’s simple yet powerful—any tool can participate just by reading or writing files.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions on Scalability and Collaboration
It is not yet clear how well this architecture performs with very large projects or teams, especially regarding concurrent access and synchronization. While atomic file operations are robust for individual updates, handling simultaneous edits across multiple tools or users may present challenges that are still being explored. Additionally, the ecosystem’s maturity and how external tools will adopt this model remain uncertain.
Next Steps for Adoption and Development
Threlmark plans to release detailed documentation and encourage community experimentation with its file-based architecture. Future developments may include enhanced conflict resolution, broader tool integrations, and performance optimizations for larger datasets. Monitoring how users adopt and adapt to this approach will be key to understanding its long-term viability.
Key Questions
How does Threlmark ensure data safety with file-based storage?
It uses atomic writes—saving data to temporary files and renaming them—to prevent corruption during crashes or interruptions. It also employs a read-merge-write cycle that preserves data integrity and forward compatibility.
Can external tools easily integrate with Threlmark’s data?
Yes. Since all data is stored as plain JSON files, any tool or script that can read and write JSON can participate, making the system highly interoperable and open.
What are the limitations of this local-first approach?
Handling concurrent edits by multiple users or tools may pose challenges, particularly around synchronization and conflict resolution in larger teams or projects. These issues are still being explored.
Is this approach suitable for large-scale enterprise use?
While promising for individual users and small teams, scalability and collaboration features for large organizations are not yet fully demonstrated and remain areas for further development.
Source: ThorstenMeyerAI.com
