📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark has announced a new product philosophy: the roadmap is a JSON file stored locally, making it open, simple, and vendor-agnostic. This shifts how teams and agents collaborate on project plans.
Threlmark has introduced a new approach to project roadmaps, asserting that ‘disk is the contract.’ The company’s product centers on storing the entire roadmap as a plain JSON file on the user’s local disk, enabling direct, tool-agnostic access and modification. This shift aims to enhance interoperability, durability, and ownership of project data, diverging from traditional SaaS-based roadmap tools.
The core idea behind Threlmark’s approach is that the roadmap’s structure is defined by a JSON file stored locally, which any program capable of reading or writing JSON can access. This eliminates dependency on proprietary SaaS APIs, vendor lock-in, and cloud-based data storage, offering a more durable and accessible format for project planning.
The product also features a scored kanban board where each task carries a priority score, making prioritization explicit and facilitating trade-offs. The board is merely a view over the JSON file, which can be read or updated by humans or automated agents without requiring special integrations or permissions.
Threlmark emphasizes that this approach is best suited for small teams or operators, as it does not support real-time multi-user editing, conflict resolution, or permissioning at scale. The system is designed for durability, ownership, and simplicity, with the trade-off being that it’s less suited for large, distributed teams needing concurrent editing.
Threlmark — disk is the contract
The roadmap is a plain JSON file on your disk. The board is just a view over it — and your tools and your agents read and write the same file directly.
Independent commentary, produced with AI assistance under human editorial oversight. The views are the author’s own and may change. Threlmark is open source under MIT, provided “as is” without warranty; see the repository LICENSE. Automated agents that read and write the roadmap file may introduce errors — treat agent writes as changes to review, not facts to trust. Product and company names are trademarks of their respective owners; mention does not imply endorsement.
Implications for Project Data Ownership and Interoperability
This development matters because it challenges the dominant SaaS-based project management paradigm by prioritizing data ownership and long-term durability. By storing the roadmap as a plain, open format on local disk, teams can avoid vendor lock-in, ensure their project data remains accessible regardless of tool changes, and facilitate seamless integration with any JSON-compatible system. This approach could influence future project management tools to adopt more open, decentralized architectures.
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.
Limitations and Trade-offs of a Disk-Based Roadmap
Traditional roadmap tools rely on cloud-based SaaS platforms offering real-time collaboration, conflict resolution, and permission management. Threlmark’s approach, by contrast, relies on a static JSON file stored locally, which can be read and modified by any compatible tool. This design aligns with local-first, provider-agnostic principles but sacrifices features like concurrent editing and audit trails at scale.
The concept builds on the idea that operational data, like project plans, benefits from durability and ownership, which are often compromised by SaaS dependencies. For more on this topic, see raw-feed licensing and the future of open data contracts.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark’s approach makes the entire product a single JSON file on your disk.”
— Thorsten Meyer, Threlmark
local JSON roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About Scalability and Collaboration
It is not yet clear how well this approach will perform in larger teams or organizations requiring real-time, multi-user collaboration. The system’s reliance on static files means conflict resolution and concurrent editing are limited, which could restrict its applicability for enterprise-scale project management. Additionally, the risks associated with agent-writable files, such as potential data corruption, require further safeguards and review processes.
pmxboard 4 Column Magnetic Kanban Board, Scrum Board Flex Whiteboard Kit. Agile Kit, 64 Magnetic Kanban Cards Kit, Scrum Cards Set. Project Management Board for Project Planning, Kanban Whiteboard Kit
✔ FULL AGILE MANAGEMENT BOARD SET. A special flexible Magnetic Agile Board comes with 64 pieces of Magnetic…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Ecosystem Development
Threlmark is expected to continue refining its local-first, open format philosophy, potentially developing tools for better conflict management and versioning. Future updates may include integrations that enhance collaboration without sacrificing the core principles. Observers will also watch for adoption by small teams and how the approach influences broader project management practices.
plain JSON task management app
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark’s approach differ from traditional roadmap tools?
It stores the entire roadmap as a plain JSON file on the user’s local disk, avoiding SaaS dependencies and enabling direct access and modification by any compatible tool or agent.
What are the main benefits of a disk-based roadmap?
Ownership, durability, interoperability, and resistance to vendor lock-in, ensuring the plan remains accessible regardless of future tool changes.
What limitations does this approach have?
It is less suitable for large teams requiring real-time collaboration, conflict resolution, and permission management at scale. It also requires careful management of agent writes to prevent data corruption.
Is this system intended for enterprise use?
No, it is primarily designed for small teams or individual operators who prioritize simplicity, ownership, and durability over large-scale collaboration features.
Will there be future updates or integrations?
Yes, Threlmark plans to develop tools that enhance conflict management and facilitate broader ecosystem compatibility while maintaining its core principles.
Source: ThorstenMeyerAI.com
