SolveStack: local-first IT troubleshooting workspace
Capture observations, commands, evidence, hypotheses, dead ends, decisions, and resolutions while you troubleshoot.
Your investigations stay in this browser and export as portable Markdown, standalone HTML, JSON, and ZIP knowledge packages.
What does SolveStack preserve from each investigation?
SolveStack gives an IT investigation a durable 7-part structure while the work is still happening:
- The original symptom
- Commands and observations
- Evidence
- Competing hypotheses
- Causes ruled out
- The confirmed root cause
- The validation that proved the resolution worked
The result is more useful than a ticket that records only the final command.
Study how real incidents were diagnosed: Root Cause Casebook publishes evidence-grounded IT incident case studies.
How does local-first troubleshooting work?
Core investigation data stays in IndexedDB in the current browser. SolveStack has no account, cloud database, or built-in AI service, and it keeps working offline as a progressive web app. Export to 4 portable formats: Markdown for a knowledge repository, standalone HTML for a readable handoff, JSON for lossless backup or migration, or a ZIP package that keeps the record and supporting evidence together.
Questions about SolveStack
Where does SolveStack store troubleshooting data?
Core investigation data stays in IndexedDB in the current browser profile. SolveStack has no account or cloud database.
What can SolveStack export?
Export Markdown, standalone HTML, JSON, complete backups, or ZIP knowledge packages that keep the record and supporting evidence together.
Does SolveStack use AI?
No. SolveStack does not include an AI service. You can review an export in an organization-approved tool after removing credentials, personal data, and confidential evidence.
Created by Steve Thoms. Contact the creator.