📊 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 employs a unique local-first architecture where project data is stored directly on disk as JSON files, eliminating the need for a server. This approach enhances portability, safety, and interoperability, with confirmed design choices and ongoing development details.
Threlmark’s new architecture uses on-disk JSON files as the sole source of project data, eliminating the need for a server or cloud storage, and enabling direct, portable, and restartable project management.
The core design decision in Threlmark is that the filesystem layout, with one JSON file per project item, acts as the API and record. This approach allows external tools to read, modify, and participate without permission barriers, fostering open interoperability. Learn more about the architecture.
Data is stored in a directory (defaulting to ~/.threlmark), containing a manifest, dependency graph, project metadata, lane ordering, individual roadmap cards, suggestions, handoffs, and reports. Shared items and archived projects are also managed within this structure, ensuring transparency and accessibility.
Two key techniques ensure safety: atomic file writes—writing to a temporary file then renaming to prevent corruption—and read-merge-write updates, which preserve data integrity and forward compatibility by tolerantly merging changes. This guarantees that external modifications are safe, consistent, and non-destructive.
The system’s design avoids traditional databases, making it restartable and portable. External tools can join the ecosystem simply by reading and writing files, with no lock-in or complex synchronization required.
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 project management tools
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.local-first architecture software
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.
file-based project management app
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.
atomic file write software
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.
Advantages of a File-Based, Serverless Architecture
This architecture provides several benefits: every artifact is inspectable and version-controlled, enabling easy backup and migration; it ensures high interoperability across tools and languages; and it guarantees data safety and consistency without reliance on server infrastructure. This approach challenges conventional database-dependent designs and demonstrates a robust alternative for project management tools.
Evolution of Local-First and File-Based Systems
Traditional project management tools rely on centralized servers or cloud services, complicating data portability and increasing dependency. Threlmark’s approach builds on prior local-first principles, emphasizing that data stored directly on disk can be safe, accessible, and flexible. Its design aligns with recent trends toward open, interoperable, and restartable software systems, but applies these principles specifically to project roadmaps and AI integration.
Previous tools often faced issues with fragmentation, lock-in, and complex synchronization. Threlmark’s architecture aims to solve these by making each file a self-contained, atomic unit of data that can be independently manipulated, merged, and validated, thus enabling multi-tool workflows and external participation.
“The core idea is that the on-disk layout itself becomes the API, ensuring that data remains portable, safe, and open to any tool that wants to participate.”
— Thorsten Meyer, creator of Threlmark
Unresolved Details and Ongoing Development
While the architecture’s principles are clear, specific aspects such as performance at scale, handling concurrent external modifications, and user experience with large project sets remain under evaluation. Additionally, integration with external tools and AI agents is still evolving, with some workflows untested in production environments.
Future Enhancements and Broader Adoption Plans
Threlmark’s developers plan to refine the handling of concurrent updates, improve user interfaces for managing large numbers of files, and expand integrations with AI agents and external tools. They also aim to gather user feedback to optimize workflows and demonstrate the system’s scalability and robustness in diverse project contexts.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to a temporary file then renaming it—and tolerant merge updates that preserve data integrity even during crashes or concurrent modifications.
Can external tools participate in Threlmark’s project management?
Yes, since data is stored as JSON files in a shared directory, any tool that can read and write JSON can join and modify the project data without restrictions.
What are the main benefits of this local-first approach?
It offers portability, inspectability, restartability, and interoperability, making project data accessible and manageable across different tools and environments without lock-in.
Are there limitations or challenges with this architecture?
Handling high concurrency and large project sets may require further optimization, and some workflows involving external AI agents are still in development.
How does this approach compare to traditional cloud-based project tools?
Unlike cloud tools, Threlmark’s system is entirely local, avoiding dependencies on external servers, which enhances privacy, control, and portability.
Source: ThorstenMeyerAI.com
