📊 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 that uses JSON files as the single source of truth, enabling portable, inspectable, and collaborative project management without servers. This approach shifts how project data is stored, shared, and managed.
Threlmark has unveiled a novel local-first architecture that uses JSON files stored directly on disk as the definitive source of project data, eliminating the need for servers or cloud storage. This design allows external tools and AI agents to interact with project data seamlessly, making the system highly portable and restartable, with significant implications for collaborative project management.
The core of Threlmark’s architecture is that all project data resides in plain JSON files within a dedicated directory (defaulting to ~/.threlmark). This includes project metadata, dependency graphs, individual roadmap cards, and external suggestions. Unlike traditional tools that rely on centralized databases, Threlmark’s approach makes each artifact inspectable, portable, and interoperable with any tool capable of reading and writing files.
To ensure safety and consistency, Threlmark employs atomic file writes by first writing to temporary files and then renaming them, preventing corruption during crashes. It also uses a read-merge-write pattern, allowing updates that preserve existing data structures and forward compatibility with new fields. The design supports multiple projects, shared items, and archiving, all managed through a structured directory layout that emphasizes simplicity and transparency.
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.
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.
Practical Python Projects Step-by-Step: Build Real Applications, Automation Tools, and Desktop Programs with Python 3.14 (Modern Python Development Mastery Series)
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 Genie Premium: JSON Editor, Viewer & Formatter
Open, view, and edit JSON and JSONC files with a fast tree-based interface
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 Data Model
This architecture shifts the paradigm from cloud or database reliance to a decentralized, local-first approach. It enhances data portability, transparency, and collaboration, allowing users to easily back up, migrate, and integrate tools without vendor lock-in. For developers and teams, this means more control over project data, reduced dependency on centralized services, and improved resilience against outages or data loss.Threlmark’s Design Philosophy and Development Timeline
Threlmark’s approach builds on the idea that project data should be open, portable, and manageable outside of proprietary platforms. The concept emerged from the need to unify fragmented roadmaps and integrate AI-driven automation into project workflows. The system’s design emphasizes simplicity, safety, and interoperability, drawing from previous projects that used file-based state management. The announcement in March 2024 marks a significant step in evolving local-first project tools, with ongoing development focused on refining the architecture and expanding external integrations.“By making the disk the contract, we remove the middleman—no database, no cloud, just files that anyone can read, write, and trust.”
— Thorsten Meyer, creator of Threlmark
Unresolved Questions About Threlmark’s Scalability and Integration
It is not yet clear how well Threlmark’s architecture performs under very large projects or with numerous concurrent external tools. The system’s reliance on local files may pose challenges for distributed collaboration at scale, and integration with existing enterprise workflows remains to be tested comprehensively.Next Steps for Threlmark Development and Adoption
Threlmark plans to release further updates that improve external tool integration, enhance multi-user collaboration, and test scalability with larger projects. Community feedback and real-world usage will shape future features, including potential support for cloud syncing while maintaining the core local-first philosophy. Developers and users are encouraged to experiment with the current setup and contribute to its evolution.Key Questions
How does Threlmark ensure data safety without a database?
Threlmark employs atomic file writes by writing to temporary files and then renaming them, preventing corruption during crashes. It also uses a read-merge-write pattern to preserve data integrity and support forward compatibility.
Can Threlmark’s system support multiple users?
Currently, Threlmark is designed as a local-first tool with single-user control. Multi-user collaboration at scale is not yet fully supported and remains an area for future development.
What makes Threlmark’s architecture different from traditional project tools?
Unlike cloud-based tools that store data on servers, Threlmark stores all project data in plain JSON files on disk, making it portable, inspectable, and independent of any specific platform or provider.
Is Threlmark suitable for large or complex projects?
While promising for small to medium projects, its performance and scalability in very large or highly complex projects are still being evaluated, with future updates expected to address these concerns.
Source: ThorstenMeyerAI.com
