The Dota Companion web edition is a free page at dotacompanion.dhseadev.online that runs the Dota Companion extension’s own code in an ordinary browser tab. Paste a Steam profile link or ID and it shows that player’s recent form, heroes, matchups and wards, read from the public OpenDota API. There is nothing to install and no sign-in. There is also a demo with a made-up player, so you can see every screen before you type a real ID.

How do you use the web edition?
Open the page, paste a Steam profile URL or a numeric ID, and press Enter. A link of the form ?player= followed by an ID opens straight onto that player, so you can send someone their own page. If the page comes back empty, the usual reason is that the profile does not share match data: turn on “Expose Public Match Data” in Dota 2’s settings and give OpenDota a while to catch up. The page has a short setup dialog that says the same thing, and a six-step tour for first visits.
What is in the demo, and what is made up?
Everything in the demo is invented. The player has 1,080 sample games, 648 wins and 432 losses, generated for the page; none of it is a real account. The demo inventory is the extension’s own inventory page running on synthetic Steam responses: 62 sample items that total $990.08 at sample prices, not real market prices. It loads the items and prices them by itself when you open it, because the first version made people press two buttons to see anything, and the buttons still work if you want to run it again. Every control in the demo has a one-line tooltip saying what it does.

What does the page send, and to whom?
The live page makes read-only requests to the OpenDota API and loads Steam’s public avatar and item images. The page enforces that in code rather than by promise: a request to any other player-data host is refused. The one write is optional and off by default. If you tick the box, the page may ask OpenDota to parse a match replay, which is a request to a single OpenDota path. Visits are counted two ways. Jetpack Stats, the same counter as the rest of this site, loads one script from WordPress.com and sends one small request to its pixel host; it sets one cookie, named tk_qs. Cloudflare Web Analytics loads one script and makes one small request, both to Cloudflare’s own hosts. As of 2026-11-17 I checked that the page itself writes no storage key for either. One thing to know: the ?player= value is part of the page address, so the host can see it in an ordinary request, as with any URL. It is a public ID, but it is not invisible. Dota Companion is not affiliated with or endorsed by Valve.
How is it built without forking the extension?
A build script reads the extension’s own popup page, works out which files it needs, copies them untouched and injects a small layer that stands in for the browser extension APIs the app expects. The extension source (version 2.5.0) is not edited, so there is one app to maintain, not two. The build fails if any of the places it hooks into move. There is exactly one patch to the extension’s code, applied at build time, and it is described below; I will remove it when the extension ships the fix.
What went wrong on the way
On a return visit the benchmark rows appeared twice. The cause is a race in the extension’s own benchmark rendering, where two overlapping loads each append their rows. The extension has the same defect; the web edition patches it at build time, and a test now loads a player twice and counts the rows. The first screen was another miss: everything sat in a narrow strip at the left of a wide window, and it looked off even though nothing was broken. It is now one shared reading column, with the Overview in two columns from 1,000 pixels up, and I checked it at four widths. And the custom domain returned a certificate error for about two minutes after I attached it, until the host finished issuing the certificate.
What is not there yet
An item-usage view, which would show how often the items you own are used in your games, is not built, because I have not verified that OpenDota exposes the data it needs. Pasting an inventory in by hand is still an idea, not a feature. The side panel exists only in the extension, which remains the version for day-to-day use and is on the Chrome Web Store.
The project page has the feature list, the changelog and the privacy notes. The earlier chapters are on the blog: what 2.5 changed, how the inventory half got built and why it is deliberately slow.
