📊 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 disk-based JSON files serve as the primary data store. This approach ensures portability, safety, and interoperability, challenging traditional database reliance.
Threlmark has revealed a novel architecture that treats disk-based JSON files as the definitive contract for project data, eliminating the need for centralized databases and enabling local-first project management.
The core design choice is that all project artifacts, including cards, dependencies, and workflows, are stored as individual JSON files on disk, with the directory structure acting as the API. This setup allows external tools and AI agents to interact directly with files, ensuring portability and interoperability.
Key technical decisions include atomic file writes, using temporary files and rename operations to prevent corruption, and a read-merge-write approach that maintains backward compatibility and forward growth. Each project comprises multiple files: a manifest, dependency graph, project metadata, lane configurations, individual cards, and shared resources. This structure guarantees that all data is inspectable, migratable, and restartable, with no reliance on a central server or database.
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.
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.
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.
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.
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 JSON file organizer
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 Managers Portable Handbook, Third Edition (Project Book Series)
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-First, Database-Free System
This architecture could reshape how project management tools handle data by prioritizing local control, data portability, and resilience. It allows users to back up, migrate, and integrate tools easily, fostering a more open ecosystem. Additionally, the design supports AI automation directly through file interactions, potentially reducing dependency on cloud services and proprietary databases, which could impact the broader software development and productivity landscape.
The Evolution of Local-First Project Management
Traditional project tools often rely on cloud-based servers and databases, fragmenting roadmaps and complicating data portability. Threlmark’s approach builds on prior local-first principles but advances them by making disk storage the central contract. The concept aligns with growing movements toward decentralized data management and offline-first tools, emphasizing user control and interoperability. The design draws from proven patterns in file handling and concurrency safety, adapted for complex project workflows.
“The on-disk layout is the API — it’s a deliberate contract that makes data portable, inspectable, and safe, all without a database.”
— Thorsten Meyer, Threlmark Developer
Unanswered Questions About Scalability and Ecosystem Integration
It remains unclear how well this disk-first approach will scale for very large projects or teams, and whether it can seamlessly integrate with existing cloud-based workflows. The practical limits of concurrency, collaboration, and real-time updates are still being tested, and broader adoption may face challenges in ecosystems dominated by centralized databases.
Next Steps for Threlmark and Broader Adoption
Threlmark plans to continue developing its system, testing its robustness in larger, collaborative environments. Future updates may include enhanced tools for synchronization, cloud backup options, and integrations with other productivity platforms. Observers will watch for community adoption and real-world performance, especially in complex multi-user scenarios.
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, along with read-merge-write patterns that preserve data integrity during updates.
Can external tools modify Threlmark data?
Yes, because all data is stored as plain JSON files, any tool that can read and write JSON can participate, making the system highly interoperable.
Is this approach suitable for large teams or complex projects?
This is still under development; scalability and collaboration in large environments remain uncertain as testing continues.
How does this architecture support AI automation?
AI agents can directly interact with files—reading, updating, and closing loops—without needing an external database or API, enabling more autonomous workflows.
What are the main benefits of a disk-based, database-free system?
Portability, inspectability, safety, and interoperability—users can back up, migrate, and extend their data easily without vendor lock-in.
Source: ThorstenMeyerAI.com
