📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announces a new roadmap approach where the plan lives as a JSON file on disk, making it open, vendor-agnostic, and easily accessible for automation. This shifts the traditional SaaS-based model to a local-first, file-based system.
Threlmark has unveiled a new approach to project roadmaps, where the entire plan is stored as a plain JSON file on the user’s disk, rather than within a SaaS platform. This local-first architecture emphasizes simplicity, interoperability, and ownership, potentially transforming how teams manage and automate their planning processes. This design emphasizes simplicity, interoperability, and ownership, potentially transforming how teams manage and automate their planning processes.
The core innovation from Threlmark is that the roadmap exists solely as a JSON file, which any program capable of reading or writing JSON can access. The product is open source under the MIT license and is designed to be local-first and provider-agnostic, meaning it does not rely on cloud services or proprietary APIs. The roadmap’s structure serves as the integration point, enabling seamless automation and sharing between tools and agents without vendor lock-in.
Additionally, Threlmark introduces a scored kanban system where each item carries a priority score, facilitating visible prioritization and trade-offs. The design allows agents—automated or human—to read, modify, and update the roadmap directly by manipulating the JSON file, making it a shared, live workspace for planning and execution. However, the approach has acknowledged limitations, such as reduced support for concurrent multi-user editing and conflict resolution, making it more suitable for small teams or individual operators.
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 of a File-Based Roadmap System
This development matters because it shifts control of project planning data from SaaS platforms to the user’s own infrastructure, enhancing ownership, durability, and interoperability. It reduces dependency on vendor-specific APIs and mitigates risks associated with platform deprecation or pricing changes. For teams and automation agents, this means a more transparent, flexible, and future-proof way to manage roadmaps, especially for small teams or individual operators who prioritize simplicity and control.
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.
Background on Roadmap Tools and Threlmark’s Approach
Traditional project management tools often rely on SaaS platforms with proprietary APIs, which can lead to vendor lock-in and limited control over data. Threlmark’s philosophy challenges this by proposing that the roadmap should be a simple, open, and durable artifact—specifically, a JSON file stored locally. The company emphasizes that this approach is a deliberate counterpoint to complex, cloud-dependent tools, aiming for interoperability and long-term accessibility of planning data. Threlmark’s philosophy challenges this by proposing that the roadmap should be a simple, open, and durable artifact—specifically, a JSON file stored locally. The company emphasizes that this approach is a deliberate counterpoint to complex, cloud-dependent tools, aiming for interoperability and long-term accessibility of planning data.
This concept aligns with broader trends favoring local-first, open standards, and automation-friendly architectures. Threlmark’s approach is especially appealing to small teams and operators who value simplicity and data ownership over advanced collaboration features.
“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 is to make the roadmap a plain JSON file on your disk, ensuring durability and interoperability.”
— Thorsten Meyer, Threlmark founder
Limitations of the File-Based Roadmap Model
It is not yet clear how well this approach scales for larger teams or organizations requiring real-time collaboration, conflict resolution, and permission management. Threlmark acknowledges that concurrent editing and multi-user support are limited, which could restrict its applicability in enterprise environments. The risk of accidental corruption from miswritten JSON or agent errors also remains a concern, necessitating guardrails and review processes.
Next Steps for Adoption and Development
Threlmark plans to continue developing tools and best practices for small teams and operators to adopt the JSON-based roadmap. Future updates may include enhanced conflict resolution, versioning, and collaboration features, though the core philosophy of simplicity and ownership will remain. The company also intends to foster a community around open standards for project planning artifacts, encouraging wider adoption and interoperability.
Key Questions
How does Threlmark’s approach differ from traditional SaaS roadmap tools?
Unlike SaaS tools that store data in proprietary cloud systems, Threlmark stores the entire roadmap as a plain JSON file on the user’s disk, enabling ownership, durability, and interoperability without vendor lock-in.
Can multiple users edit the roadmap simultaneously?
Currently, the system is optimized for small teams or individual operators. It has limited support for concurrent multi-user editing, and conflicts must be managed manually or through external tools.
What are the risks of using a file-based roadmap?
The main risks include potential data corruption from miswritten JSON or agent errors, and the lack of real-time conflict resolution. Proper guardrails and review processes are recommended.
Is Threlmark suitable for enterprise-level project management?
Threlmark is primarily designed for small teams and operators prioritizing simplicity and control. It may not meet the needs of large organizations requiring advanced collaboration features.
Where can I learn more or access the open-source project?
The project is open source under the MIT license and available at threlmark.com. The site offers detailed documentation and deep dives into the internals.
Source: ThorstenMeyerAI.com
