📊 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 is a JSON file stored locally, making it open, interoperable, and durable. This contrasts with traditional SaaS tools and emphasizes simplicity and control.
Threlmark has introduced a new approach to project roadmaps, where the entire plan is stored as a plain JSON file on the user’s local disk, making it the definitive contract for planning and automation. This departure from SaaS-based tools emphasizes simplicity, interoperability, and durability, offering a different model for teams and automation agents.
Threlmark’s core product is a plain JSON file that represents the roadmap, which can be read and written by any tool capable of handling JSON. The roadmap is not hosted on a SaaS platform, but resides locally, giving users full ownership and control. The visual interface is a scored kanban board, where each item has a priority score, enforcing explicit prioritization and trade-offs. Because the contract is a file format, any compatible program can interact with the roadmap without needing SDKs or APIs, enabling straightforward integration and automation.This approach contrasts with traditional SaaS roadmap tools that rely on APIs, real-time collaboration, and vendor lock-in. Threlmark emphasizes local-first, provider-agnostic architecture, reducing dependency on specific vendors and ensuring long-term access to planning data. However, it acknowledges limitations, such as reduced support for concurrent editing by large teams and risks associated with agent-writable files, which require careful management.
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 Roadmap Management and Automation
This new model shifts the paradigm of project planning by making roadmaps independent of SaaS platforms, emphasizing ownership, interoperability, and durability. It simplifies integration with automation agents, reduces vendor lock-in, and ensures long-term access to planning data. For small teams or operators, this approach offers a more transparent and resilient way to coordinate work. However, it may not suit large, highly collaborative environments that rely on real-time editing and conflict resolution, making it a significant development for specific use cases and a potential alternative to traditional tools.
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 the ‘Disk as the Contract’ Concept
Traditional project management tools increasingly rely on SaaS platforms with APIs, real-time collaboration, and vendor-specific features, which can lead to vendor lock-in and dependency. For more on this trend, see Raw-feed licensing. Threlmark’s approach builds on the idea that operational data, like roadmaps, should be owned and controlled directly by users. The concept of ‘disk as the contract’ emphasizes that the plan’s format and location should be the source of truth, enabling interoperability and long-term access. This approach aligns with broader trends toward local-first, provider-agnostic architectures, but is a departure from the typical SaaS-based planning tools.“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark’s ‘disk is the contract’ approach makes the plan a simple, shareable file.”
— Thorsten Meyer, Threlmark founder
local disk roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of the ‘Disk as the Contract’ Model
It is not yet clear how well this approach scales for large, distributed teams requiring real-time collaboration or conflict management. The reliance on local files may introduce risks of data corruption or loss if not properly managed. Additionally, the security and permissioning model for agent writes and multi-user editing are still being developed, with potential for mis-writes or errors. Further testing and user feedback are needed to evaluate these aspects.
Learn How To Introduce Kanban: Agile Project Management Methods
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development
Threlmark plans to release the full open-source product and documentation in the coming months, encouraging early adopters to test the approach. Future updates may include tools for conflict resolution, version control, and enhanced collaboration features, while maintaining the core principle of a local, file-based contract. The company also aims to build community tools that can read and write the roadmap file, expanding interoperability.
Project Planner: Management Notebooks Organizer & Work Log Book Tracker With Checklist Brainstorming for Entrepreneurs, Managers & Small Business Owners
TURN YOUR IDEAS INTO REALITY: Unleash your creativity with this unique planning notebook, consisting of 224 pages divided…
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 SaaS roadmap tools?
Instead of hosting the roadmap on a SaaS platform, Threlmark stores it as a plain JSON file on the user’s local disk, making it ownership-based and interoperable with any tool that reads JSON.
What are the main benefits of using a file-based roadmap?
Ownership, durability, interoperability, and resistance to vendor lock-in. The plan is portable, long-lasting, and easily integrated with automation tools.
What are the limitations of this approach?
It is less suitable for large, collaborative teams needing real-time editing, conflict resolution, or advanced permissioning. There’s also a risk of data corruption if not managed carefully.
Can I automate updates to the roadmap?
Yes, any program capable of reading or writing JSON can update the roadmap file, enabling automation and integration with agents.
Source: ThorstenMeyerAI.com
