📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

Threlmark has introduced a novel approach to project roadmaps, where the entire plan is a plain JSON file stored locally on the user’s disk, making the file itself the definitive contract. This shift away from SaaS tools aims to provide greater control, interoperability, and durability for teams managing their roadmaps.

The core concept behind Threlmark is that the roadmap exists as a simple, structured JSON file on the user’s local disk, which any program capable of reading or writing JSON can access. There is no reliance on APIs, webhooks, or vendor-specific platforms. The file acts as the single source of truth, and the visual kanban board is just a view over this file.

This approach allows seamless integration with existing tools, as the contract is the file format itself. It also enables agents—automated or human—to read and modify the roadmap directly by manipulating the JSON file, fostering a shared, live workspace. Threlmark emphasizes local-first operation and vendor independence, reducing lock-in and ensuring long-term access to the plan.

The product also features a scoring system for roadmap items, which enforces prioritization and helps teams make clearer trade-offs. Items are ranked by importance, and the system discourages the all-high-priority trap, promoting deliberate decision-making. This scoring integrates directly into the file, making prioritization transparent and actionable.

However, Threlmark acknowledges limitations: it is not suited for large, real-time collaborative editing or enterprise-scale permissioning. The approach requires careful management of agent permissions and scoring accuracy, as a misconfigured score or malicious agent could corrupt the plan. This solution is primarily targeted at small teams or operators seeking simplicity and control.

Implications for Roadmap Ownership and Interoperability

This development matters because it shifts control of project plans from proprietary SaaS platforms to users’ own files, ensuring long-term access and reducing vendor lock-in. It enables a more open, flexible workflow where any tool that reads JSON can participate, fostering interoperability and resilience. For teams valuing operational simplicity and data durability, this approach offers a compelling alternative to traditional roadmap tools.

Background on Roadmap Tools and Data Persistence

Traditional project management tools rely heavily on SaaS platforms with APIs, webhooks, and proprietary data formats, which can lead to vendor lock-in and data loss if the service deprecates or discontinues. The concept of storing operational data as a plain file on disk is rooted in principles of local-first software and data durability. Threlmark’s approach builds on this by making the roadmap a simple, structured JSON file, which can be read and modified by any compatible tool or agent, ensuring longevity and interoperability.

This approach aligns with broader trends favoring open formats and local data ownership, addressing pain points related to SaaS dependency and data portability. It also introduces a scoring system to help teams prioritize work directly within this file-based system.

“A roadmap lives inside our database, behind our API, accessible on our terms. Threlmark makes a deliberately different bet: the roadmap is a plain JSON file on your disk.”

— Thorsten Meyer, Threlmark developer

Limitations and Risks of a Disk-Based Roadmap System

It is not yet clear how well this approach scales for large teams requiring real-time collaboration, or how effectively it manages concurrent edits and conflict resolution. The system relies on careful scoring and permission management, which could pose risks if misused or misconfigured. Additionally, the impact of potential data corruption or agent errors remains to be tested in practice.

Next Steps for Adoption and Ecosystem Development

Threlmark plans to release the full open-source code and documentation, encouraging early adopters to experiment with the system. Future developments may include enhanced conflict management, versioning, and integrations with existing project tools. Monitoring how small teams implement and adapt this model will inform broader improvements and potential scaling solutions.

Key Questions

Can I use Threlmark for large, distributed teams?

Threlmark is primarily designed for small teams or operators, as it does not support real-time multi-user editing or advanced permissioning. Large, distributed teams may face challenges with concurrent edits and conflict resolution.

How does Threlmark ensure data safety and integrity?

The roadmap is a local JSON file, which minimizes data loss risks compared to cloud-based tools. However, it relies on proper management of the file and agent permissions to prevent corruption or accidental modifications.

What if a tool or agent modifies the roadmap incorrectly?

Since the contract is the file format, any incorrect modification can corrupt the plan. Users should implement guardrails and review processes when automating updates.

How does scoring improve roadmap prioritization?

Items are ranked by importance, forcing teams to make deliberate trade-offs. This prevents the common issue of having all tasks marked as high priority, promoting clearer decision-making.

Source: ThorstenMeyerAI.com