Questions and answers
Short answers, including the unflattering ones. Each is written to stand on its own if it is quoted somewhere without the rest of the page.
What is InspectDock?
InspectDock is a browser extension that puts 61 web development and design tools into a dock on any page: inspection, screen capture, colour and typography, accessibility and SEO checks, and local text utilities. It is in pre-release and cannot be installed yet, and none of those tools is verified in a browser. It is built by Callsmaster Services LLP.
Can I install InspectDock yet?
No. It is in pre-release and is not listed in any browser store, so there is nothing to install. No store submission has been made and no listing URL exists. The install page says the same thing rather than offering a button that does nothing.
How many of the tools actually work?
61 tools are built and 0 are verified. That is not a contradiction: every tool is written and its logic is unit-tested, but none has yet been observed running in a real browser, so none is advertised as working. The project tracks the difference explicitly rather than counting code as evidence.
Does InspectDock send my data anywhere?
No. There is no analytics, no telemetry, no account and no server. Every tool runs on your own device. The only network requests the extension makes are the ones a tool needs to do its job, such as fetching a page you asked it to inspect, and the text utilities make none at all. Two tests scan every utility source to prove it contains no network call.
What does InspectDock cost?
Nothing today, because nothing is purchasable. A paid tier is designed but checkout is closed, and the configured figures ($2.99 / month, $19.99 / year, $39 once) are a proposal rather than an offer. Anything already available free stays free; that rule is enforced by a test, not just stated.
Which browsers will InspectDock support?
Packages are built for Chrome, Edge, Opera and Firefox. None has been loaded in any of them yet. The Firefox build deliberately drops the user-scripts permission, because Mozilla approves that API only for extensions whose purpose is managing user scripts.
What permissions does InspectDock need?
As few as possible, and the broad ones are optional. Cookie access and access to all sites are requested only at the moment a tool needs them, from a dedicated extension page, and both tools degrade with a clear explanation if you refuse. There is no always-on content script: nothing runs on a page until you open the dock.
Is InspectDock open source?
Not at present. The repository is private. The privacy claims on this site are backed by tests in that repository rather than by public source, which is a weaker guarantee and is stated as such.
How is InspectDock different from SuperDev Pro or Hoverify?
Honestly, it is behind them on the only measure that matters: they are shipping and verified by real users, and InspectDock is neither. It has a comparable tool count and a stricter permission model on paper. A dated, sourced comparison is maintained in the project documentation, including the dimensions where InspectDock loses.
How do I get support?
Email hello@inspectdock.com. There is no live chat, no forum and no ticket system, and no response-time commitment is made, because none has been tested.