I built DevDock because reopening a codebase is not the same as recovering the context needed to work on it. A product may span several folders, and the useful state is scattered across commands, Docker, Git, databases, project health, and the checks I want to run before release.
DevDock is my attempt to keep that context in one local Windows workspace. Each registered project gets an overview, saved commands, run history, Docker and Git state, database operations, local security findings, settings, and tools. A Today view keeps recent projects and saved daily workflows close when I switch between products.
The important boundary is that it is a local tool. It does not upload source code. The security audit checks registered folders for exposed secrets, private keys, tracked credential files, unsafe permissions, escaping symlinks, and missing lockfiles, while withholding matched secret values. Database tools are deliberately bounded around schema inspection, constrained record lookups, migration review, diagnostics, and confirmed backup operations.
The Free tier supports up to three local projects with core commands, Git, Docker, Project Doctor, and security audits. Pro is a one-time purchase for unlimited and multi-folder projects, custom workflows, complete history and insights, database tools, SSH transfers, and configuration backup and restore.
I would especially value feedback from developers who work across several local repositories: which piece of context costs you the most time when you return to a project?
Top comments (1)
This is a small topic with a big productivity cost. The useful memory is not everything that was open; it is the few pieces needed to resume without rebuilding context from scratch: current task, last command, failing test, and why the next step was chosen. Anything more can become clutter.