Nine hundred and sixty nine thousand seven hundred and fifty four rows, in twenty seven comma separated files, about what the feedback and roadmap tool category charges, publishes, writes and links to.
They were all built because something here needed them. A page cannot say what thirty two vendors charge without somebody reading thirty two pricing pages first, and once that reading is done the file is more useful in public than in a private directory.
Every one of them is free to copy, change, quote and use commercially, with no attribution and no link back.
What is in the twenty seven?
| The file | Rows | What each row is |
|---|---|---|
| Pricing | 32 | One vendor, its entry price, the unit the bill is metered on, and what its free plan stops at |
| Board votes | 702 | One public Canny or Featurebase board, with its posts, votes, how concentrated they are, its decided and declined share, days since its newest request, and how long its waiting requests have waited |
| Board indexing | 2,743 | One public feedback board from one of seventeen tools, with the kind of plan its own record names and whether it carries noindex |
| Board settings | 3,275 | One Featurebase, Frill or FeatureOS workspace or public Canny board, with who may vote, post and comment without an account, what it hides, its default order, its integrations and its search indexing switch |
| Atlassian feature requests | 179,402 | One suggestion on Atlassian's public tracker, with its product, status, resolution, the dates it was filed and resolved, its votes and its watchers |
| JetBrains feature requests | 149,466 | One public feature request on JetBrains' YouTrack tracker, with its project, state, the dates it was filed and resolved, and its votes |
| VS Code feature requests | 28,886 | One issue labelled feature-request in the VS Code repository, with its dates, close reason, milestone, labels, reactions and the filer's tie to the repository |
| GitHub feature requests | 1,000 | One of the 1,000 most starred GitHub repositories, with its request labels, templates and Ideas category, and the outcomes, thumbs up and ages of its feature requests |
| Discourse feature requests | 56,951 | One topic in the feature request category of one of ten Discourse forums that run topic voting, with its dates, state, votes, likes, replies, views and tags |
| GitLab feature requests | 77,666 | One issue labelled type::feature in GitLab's own project, with its dates, state, milestone, upvotes, comment count and the labels that mark a paying customer's request and how it ended |
| Firefox and Spotify ideas | 18,164 | One idea on Mozilla Connect or on Spotify's community idea boards, with its board, status, kudos, replies, views and dates |
| Autodesk ideas | 83,020 | One idea on one of 46 Autodesk Community idea boards, Revit and Inventor the largest, with its board, status, votes, replies, views and dates |
| Discord feedback posts | 85,272 | One post on Discord's Zendesk feedback board, with its topic, status, score, up and down votes, comments, followers and dates |
| Zendesk product feedback | 7,761 | One request on Zendesk's own product feedback board, with its status, votes, replies, views, product area and dates |
| Intercom wishlist ideas | 3,383 | One idea on Intercom's Product Wishlist, with its status, votes, replies, views, product area and dates |
| Minecraft feedback posts | 144,812 | One post on the Minecraft feedback site, with its topic, status, votes, comments, followers and dates |
| Miro Wish List ideas | 4,892 | One idea on Miro's community Wish List, with its status, votes, views, replies, product areas and dates |
| Microsoft feedback posts | 107,826 | One post in one of the 68 forums of Microsoft's Feedback portal, Teams and XBOX Player Voice the largest, with its status, category, votes, comments and date |
| Release notes frequency | 327 | One public Canny or Featurebase changelog, with its entries in the last year, total entries read, newest entry age, median words, notify share and whether it was capped |
| Capabilities | 32 | One vendor against nine questions, each cell naming the plan tier that gates the answer or recording that nobody publishes one |
| Page addresses | 9,432 | One address slug, how many vendors publish it, and which ones |
| Headings | 1,748 | One heading at least two vendors write, with how many pages and how many companies carry it |
| Page counts | 69 | One vendor's whole sitemap, counted twice three weeks apart, sorted into path clusters |
| Link graph | 2,706 | One outside domain that links to more than one vendor in this category |
| Domain authority | 70 | One vendor domain and where it sits on the web's link graph, across seven releases |
| Directories | 55 | One software directory, opened on a real listing, with the rel attribute on the link it gives |
| Template overlap | 78 | One pair of a vendor's own pages, and how much wording they share |
What does the licence let you do?
Everything, including the commercial things.
The dedication is CC0, which is as close to public domain as a licence gets. Copy a file. Put it in a spreadsheet and sell the spreadsheet. Publish a chart from it under your own name. Train something on it. Rewrite the conclusions to disagree with VoteFirst's own.
No attribution is required and no link back is required. If you would rather cite than copy, every file has a page of its own with a permanent address and the date the figures were read, and citing the page rather than the file means your reader can check whether it has moved since.
Why is a vendor publishing data about its own category?
Because the alternative was leaving it in a directory nobody can see, and because the figures do not flatter VoteFirst.
The capability matrix has a column VoteFirst fails on. The authority file ranks seventy domains in this category and puts this one sixty ninth of the seventy, with five referring domains against the category leader's six thousand four hundred and fifty one. The directory file says that of fifty five software directories, seven pass ranking credit, which is a fact about how little a listing is worth, including VoteFirst's own.
A file that only made its author look good would not be worth downloading, and anybody who checked two rows of it would know.
What do all twenty seven have in common?
Three things, and they are the reasons to trust any of them.
A read date on every row or file. The vendor files date each row, and the eighteen read from public boards, changelogs, the Atlassian, JetBrains and GitLab trackers, GitHub, Discourse forums, Mozilla Connect, Spotify's community, Autodesk's and Zendesk's idea boards, Intercom's Product Wishlist, Miro's Wish List, Discord's feedback board, Minecraft's feedback site and Microsoft's Feedback portal were each read on one day, named in the file. Pricing changes and a table without a read date is a claim about an unspecified past.
The address it was read at. Most rows carry the page they came from, so a row can be checked rather than believed.
Silence recorded as silence. Where a vendor publishes no answer, the cell says unpublished. It does not say no. An absence of evidence on a marketing site has never been proof that software cannot do a thing, and a file that quietly turns one into the other is worse than no file.
What none of these is
None of them is a scorecard, and none of them weights its columns against each other.
They also stop where the measurement stopped. A sitemap is what a vendor chose to list, so pages that exist and are not listed are not counted. The link graph is one crawler's view of the web and not the whole of it. A pricing page read on one day says nothing about the next.
Where a file has a limit, that limit is written on the file's own page rather than left for you to find.
When do they go stale?
The pricing ones go first, and they can go within a week.
Prices and plan tiers move whenever a vendor edits a page, which is why the date sits on the row. The structural ones, being the addresses, the headings and the link graph, move much more slowly, because a company changes its page template far less often than it changes a number.
Each page says when it was read. Nothing here is on a promise to be current, and a file whose date has aged is still true about the day it names.