📊 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 uses a local-first, file-based architecture where disk storage is the system’s contract, enabling open, portable, and restartable project management. This approach eliminates server reliance and enhances interoperability.
Threlmark has revealed a pioneering local-first architecture that treats disk storage as the definitive contract for managing project data, removing the need for servers or databases. This design choice enables a highly portable, interoperable, and restartable system, fundamentally changing how project management tools can operate at the local level.
The core of Threlmark’s approach is that all project data—whether individual cards, project metadata, or cross-project links—is stored in JSON files directly on the user’s disk. The main directory, defaulting to ~/.threlmark, contains files like threlmark.json (manifest), links.json (dependency graph), and individual project folders with files for cards, lanes, and suggestions. This file-based structure acts as the system’s single source of truth, accessible directly by any tool that reads or writes JSON.
Two key patterns ensure data safety: atomic file writes, achieved by writing to temporary files and then renaming them, and read-merge-write updates that preserve existing data while allowing forward compatibility. This design guarantees consistency even during crashes or concurrent modifications. External tools can participate seamlessly without permissions or API restrictions, as they simply read and write files in the established layout. This approach makes the entire system restartable—no in-memory state is lost—and highly portable, as files can be backed up, synced, or migrated easily.
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.
ENGPOW File Box with Lock,Fireproof Document Box with Zipper＆Pockets,Collapsible File Organizer Filing Storage Cabinet with Handle,Portable Home Office Safe for Hanging Letter/Legal Folder,Black
Fireproof and water-resistant: Fireproof lock box is made of double layered non-itchy silicone coated fiberglass which stands up…
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.
IMPACT IMPLEMENTS® Disc Plow Harrow with Weight Tray for ATV/UTV/Garden Tractors. Prep Soil, Cut Weeds & Clear Crop Remains.
USA COMPANY: Our Impact Implements Disc Plow is a critical tool for all soil preparation. All our implements…
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: Management Notebooks Organizer & Work Log Book Tracker With Checklist Brainstorming for Entrepreneurs, Managers & Small Business Owners
TURN YOUR IDEAS INTO REALITY: Unleash your creativity with this unique planning notebook, consisting of 224 pages divided…
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 as the Contract Transforms Project Data Management
This architecture shifts the paradigm from server-dependent systems to a purely local, file-based model, enhancing portability and interoperability. It allows users to back up, migrate, and integrate tools without vendor lock-in, fostering a more open ecosystem. The approach also simplifies recovery and debugging, as every artifact is inspectable and version-controlled through standard file operations. For developers and teams, this means greater control over their data and workflows, reducing reliance on proprietary platforms.
The Evolution of Local-First and File-Based Systems
Traditional project management tools often rely on centralized servers or cloud services, which can introduce lock-in and complicate data portability. For more on how Threlmark’s architecture addresses these issues, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s approach builds on the growing trend of local-first software, emphasizing user control and resilience. Its design draws inspiration from battle-tested file handling patterns, emphasizing atomic operations and tolerant updates, which have proven effective in other local-first applications. This development aligns with broader movements toward open, interoperable tools that respect user sovereignty over data, as discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
“The key decision was to make disk the contract, so all tools and UI reach the same files through the same discipline, ensuring data integrity and portability.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Scalability and External Tool Support
It is not yet clear how well this architecture scales with very large projects or complex dependencies. While the file-based approach offers portability and safety, performance under heavy load or extensive concurrent edits remains to be tested. Additionally, the extent of support for external tools beyond reading and writing JSON files is still evolving, and integration with existing project ecosystems could face challenges.
Next Steps for Threlmark and Broader Adoption
Threlmark plans to continue refining its architecture, potentially introducing more robust tools for conflict resolution and version control. Community engagement and external tool integration are expected to grow, with the goal of demonstrating the system’s scalability and interoperability. Future updates may include enhanced automation features and broader ecosystem support, making the local-first model more accessible for diverse workflows.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to a temporary file and renaming it atomically—to prevent corruption during crashes. Updates are merged carefully to preserve data integrity and forward compatibility.
Can external tools participate in Threlmark’s workflow?
Yes, external tools can read and write JSON files directly within the established directory layout, enabling seamless participation without API restrictions.
What are the limitations of this file-based architecture?
Scalability with very large projects or high concurrency remains unproven, and integration with complex external ecosystems may require additional development.
Is this system suitable for team collaboration?
While designed for local-first use, the portability and version control features support collaborative workflows, especially when combined with sync tools like Dropbox or git.
Source: ThorstenMeyerAI.com
