📊 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 built entirely on JSON files stored on disk, eliminating the need for servers or databases. This approach enhances portability, safety, and external tool integration, marking a shift in how project data is managed.
Threlmark has unveiled a novel local-first architecture that relies entirely on JSON files stored on disk, without any server or cloud dependency. This design allows users to manage project data in a portable, inspectable, and interoperable manner, fundamentally changing traditional project management tools.
The core architectural principle of Threlmark is that that the on-disk layout is the API. All project data—including cards, dependencies, and reports—is stored as individual JSON files in a dedicated directory, defaulting to ~/.threlmark. This setup enables external tools to access, modify, and participate in the project workflow without requiring permissions or centralized servers.
Key design decisions include atomic file writes—using temporary files and renaming to prevent corruption—and read-merge-write updates that preserve data integrity and forward compatibility. Each project contains specific files for metadata, lane ordering, and individual cards, with shared items stored centrally for multi-project referencing. The system’s stateless nature ensures restartability and ease of backup or migration.
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.
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.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.
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.
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 Disk-Based, Serverless Project Data
Threlmark’s approach offers significant advantages for developers and teams seeking control over their data. By avoiding databases, the system ensures full transparency, easy backup, and seamless external tool integration. This design promotes a more open, flexible, and resilient workflow, especially valuable for solo developers or teams prioritizing data portability and safety.
Additionally, the architecture supports automation and AI integration, enabling agents to read, modify, and close tasks without central coordination. This could influence future project management tools by shifting toward decentralized, file-based systems.
Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Evolution Toward a Local-First, File-Based System
Traditional project management tools often rely on cloud servers or centralized databases, which can fragment workflows and obscure data. Threlmark’s design builds on previous local storage solutions, but it emphasizes a strict contract where files are the source of truth. This approach aligns with trends toward decentralization and open data, aiming to give users more control and transparency.
The decision to base the architecture on JSON files is rooted in practical considerations: simplicity, portability, and safety. The pattern of atomic writes and tolerant normalization has been proven in other applications, ensuring data integrity even during crashes or concurrent modifications.
„The on-disk layout is the API. It’s a deliberate choice to make the data portable, inspectable, and interoperable—no server needed.“
— Thorsten Meyer, creator of Threlmark
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.
Remaining Questions About Threlmark’s Scalability and Use Cases
It is not yet clear how Threlmark performs with very large projects or in collaborative environments involving multiple users simultaneously editing files. The approach’s effectiveness at scale and in complex workflows remains to be tested in real-world scenarios.
Further, the level of external tool support and integration capabilities beyond initial design are still developing, and user adoption details are not yet available.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development of Threlmark
Threlmark plans to release detailed documentation and SDKs to facilitate external tool integration. User feedback from early adopters will likely shape future enhancements, particularly around collaboration features and scalability. Watching how the system handles larger projects and multi-user workflows will be key to understanding its broader applicability.
EXLIFBAG File Organizer, Fireproof File Box with Lids, Important Document Organizer Box with Lock, Portable File Folder Organizer with Handle
- Fireproof Material: Made of silicone-coated fiberglass up to 2000℉
- Durable Zipper: High-quality 2-way zipper for easy access
- Stable Base: Non-slip pad for stability and durability
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to temporary files and renaming them—to prevent corruption. The read-merge-write pattern preserves data integrity during updates.
Can external tools modify Threlmark project data?
Yes, since all data is stored as JSON files in a shared directory, any tool that can read and write JSON can participate without special permissions.
Is Threlmark suitable for team collaboration?
While designed for local-first use, its architecture supports external tool participation, but real-time multi-user collaboration features are still under development.
What are the limitations of this architecture?
Potential challenges include handling large projects or concurrent multi-user edits efficiently. Its effectiveness in such scenarios remains to be seen.
Source: ThorstenMeyerAI.com
