📊 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 project management system where the disk is the contract, meaning all data is stored as JSON files on disk. This design eliminates servers, enhances portability, and allows external tools and AI agents to participate seamlessly.
Threlmark has announced a novel local-first architecture that treats disk storage as the definitive contract for project data, removing the need for servers or cloud databases. Disk Is the Contract: Inside Threlmark’s Local-First Architecture This approach enables open, portable, and restartable workflows, allowing external tools and AI agents to interact directly with project files.
Threlmark’s system is built as a Next.js app layered on plain JSON files stored on disk, with the core principle that the disk layout functions as the API. The data resides in a directory (default ~/.threlmark), containing a manifest, dependency graph, project folders, and individual JSON files for each roadmap card. This design ensures every artifact is inspectable, portable, interoperable, and restartable, sidestepping the complexities of server-based systems. The architecture’s key decision is that there is no central server or database. Instead, all external access, whether from the UI or third-party tools, reads and writes these files directly, following strict discipline to ensure safety and consistency. Atomic file writes, achieved via temporary files and rename operations, prevent corruption during crashes. Updates are handled through read-merge-write cycles that preserve data integrity and forward compatibility, allowing new fields to be added without breaking existing tools. The system uses one file per item, avoiding race conditions associated with bulk lists, and employs a self-healing board that reconciles its state on each read, ensuring consistency even when files are added or removed externally.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 storage device
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.external disk storage for project management
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.
high-performance SSD for data integrity
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.
file synchronization tools for JSON files
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 Disk-Only Data Contract
This architecture fundamentally shifts how project data is managed, emphasizing openness, portability, and resilience. Learn more about Threlmark’s architecture By avoiding centralized servers, Threlmark enables users to back up, migrate, and integrate tools easily, fostering a more flexible and collaborative environment. It also allows AI agents and external tools to participate directly, closing the loop in project workflows without proprietary restrictions. For developers and teams prioritizing control, this approach offers a transparent, low-overhead alternative to traditional cloud-based project management systems.
Evolution Toward Local-First Project Management
Traditional project management tools often rely on cloud servers or centralized databases, which can obscure data ownership and complicate integrations. Threlmark’s approach draws inspiration from local-first principles, emphasizing data portability and resilience. Its architecture echoes broader trends in software design that favor decentralized data storage, as seen in the rise of open formats and peer-to-peer systems. The decision to make the disk the source of truth aligns with efforts to reduce dependency on cloud services, especially for developers and teams working in sensitive or disconnected environments. Read about local-first project management
“The core idea is simple: the on-disk layout is the API. This choice cascades into everything—how concurrency is handled, how external tools participate, and how AI agents can close their own loops.”
— Thorsten Meyer, creator of Threlmark
Unanswered Questions About Scalability and Collaboration
While the architecture is well-defined for individual use and small teams, it remains unclear how it performs under heavy concurrent access or in large-scale collaborative environments. The system’s reliance on file-based synchronization could face challenges with simultaneous external modifications or complex workflows. Additionally, how this approach scales to enterprise-level projects or integrates with existing tools is still to be tested and documented.
Next Steps for Threlmark’s Development and Adoption
Threlmark plans to gather user feedback and performance data to refine its concurrency and collaboration features. Future updates may include enhanced conflict resolution, integration guides for external tools, and broader documentation on scaling. The project team also aims to demonstrate real-world use cases and facilitate community contributions to validate and expand the architecture’s capabilities.
Key Questions
How does Threlmark handle concurrent edits from multiple external tools?
Currently, it relies on atomic file operations and self-healing board reconciliation to manage changes. However, detailed conflict resolution strategies for high concurrency are still under development.
Can Threlmark integrate with cloud storage or existing project management tools?
Yes, since all data is stored as JSON files, it can be backed up or synchronized with cloud services like Dropbox or Git. Integration with other tools depends on reading and writing these files directly.
Is this architecture suitable for large teams or enterprise environments?
While promising for small to medium teams, scalability and collaboration in large environments are still being tested. The architecture’s effectiveness at scale remains an open question.
Source: ThorstenMeyerAI.com
