📊 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 for project management, using JSON files as the single source of truth. This approach enhances portability, safety, and external tool integration, with no reliance on cloud or databases.
Threlmark has unveiled a new architecture that treats disk storage as the definitive contract for project data, foregoing traditional databases and cloud services. This design allows external tools and AI agents to interact directly with JSON files, ensuring portability, safety, and interoperability in managing multi-project roadmaps.
The core decision in Threlmark’s design is that all project data resides on disk as JSON files, which serve as the single source of truth. This approach eliminates the need for a central server or database, making the system inherently portable and restartable. The data directory, typically located at ~/.threlmark, contains a manifest (threlmark.json), dependency graphs (links.json), and individual project folders, each holding metadata, lane configurations, and one file per roadmap card.
Threlmark’s system emphasizes atomic file writes by temporarily writing to a separate file before renaming, preventing corruption during crashes. Updates are handled via read-merge-write cycles, preserving existing data structures and allowing forward compatibility. The architecture also employs one file per item, with the lane ordering stored separately in a self-healing board configuration, ensuring consistency even when external modifications occur.
This file-based approach enables external tools to participate seamlessly, as there’s no lock-in or proprietary database. Tools can read, modify, and write files directly, supporting open data and easy migration. The design also supports external suggestions, handoffs, and reports, all stored as JSON files within designated directories, fostering interoperability and collaborative workflows.
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 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.local-first project management tools
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.
disk-based data storage for project management
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-based collaboration tools
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 Local-First and Disk as the Contract Matters
Threlmark’s design fundamentally shifts how project data can be managed, emphasizing local control, safety, and openness. By avoiding a central server or database, it reduces reliance on cloud services, enhances data portability, and simplifies integration with external tools and AI agents. This approach also ensures that project data remains accessible and modifiable even in disconnected environments, making it especially relevant for developers prioritizing privacy, control, and flexibility.
Furthermore, the architecture’s emphasis on atomic operations and forward-compatible file formats reduces risks of data corruption and supports incremental improvements. This model demonstrates a practical way to build robust, collaborative project management tools that are resilient, transparent, and adaptable to future needs.
The Evolution of Project Data Management and Threlmark’s Innovation
Traditional project management tools often rely on centralized servers or cloud-based databases, which can introduce lock-in, data silos, and dependency on external providers. Threlmark’s approach, inspired by principles of local-first software, leverages on-disk JSON files as the authoritative source, enabling users to maintain control over their data. This design aligns with broader trends towards open data, interoperability, and resilience, addressing common pain points in multi-project workflows. Learn more about Threlmark’s local-first architecture.
Previous tools typically used monolithic JSON files or database backends, which posed challenges for external integration and data safety. Threlmark’s architecture breaks from this mold by using one file per item, with self-healing mechanisms that reconcile discrepancies automatically. This innovation is rooted in lessons from previous local-first applications, emphasizing atomicity, backward and forward compatibility, and ease of external tool participation. Read about the architecture behind Threlmark.
“The core idea is that the disk itself becomes the API, making the data portable, safe, and open for any tool to participate without restrictions.”
— Thorsten Meyer, Threlmark developer
Remaining Questions About Threlmark’s Architecture and Adoption
While the architecture’s design principles are clear, it is not yet confirmed how widely it will be adopted or how it performs at scale in diverse environments. Details about integration with existing tools, user workflows, and potential limitations of the file-based model are still emerging. Additionally, the long-term stability and community support for this approach remain to be seen.
Next Steps for Threlmark and Its Community
Threlmark plans to release detailed documentation and open-source its core components, encouraging external developers to build integrations and contribute to the ecosystem. User feedback from early adopters will inform future enhancements, particularly around collaboration features and AI agent integration. The project aims to demonstrate how local-first principles can scale in real-world project management scenarios.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file operations, writing to temporary files before renaming, which prevents corruption during crashes and ensures consistency.
Can external tools modify Threlmark data?
Yes, since data is stored as JSON files in a standard format, any tool that can read and write files can participate, supporting interoperability and open data principles.
What are the benefits of this disk-based approach?
It offers portability, safety, interoperability, and restartability, reducing lock-in and enabling flexible workflows across different environments.
Will this architecture support large-scale projects?
While promising for small to medium projects, scalability at very large scales remains to be tested, and further developments may be needed to handle extensive data sets efficiently.
How does this approach compare to traditional project management tools?
Unlike centralized or cloud-based tools, Threlmark’s local-first, file-based system prioritizes user control, open data, and resilience, but may require more manual setup and management.
Source: ThorstenMeyerAI.com
