How we check prices
This is our editorial policy for every record and guide on the site.
Where prices come from
- The vendor’s or project’s own page: pricing pages, order pages, license files, FAQs. This is the only source we accept for a price or a license term.
- Official repositories (such as GitHub releases) for version numbers and license files.
- We don’t take prices from review aggregators, resellers or AI answers. When they disagree with the vendor, we may note the difference, but the vendor’s page wins.
How we label what we checked
- Checked date
- The date we read the vendor’s page. Each price row and source shows it.
- Static vs rendered
- Some pages show prices only after JavaScript runs. For those, we read the page in a real browser and save an excerpt.
- not US-confirmed
- The vendor localizes prices by country, and we couldn’t view the US price from a US location. The row shows the best figure we have, flagged.
- Quote / not listed
- The vendor doesn’t publish a price. We never estimate one.
- Our observation
- Something we saw ourselves, such as a mismatch between sources, rather than a vendor statement.
- Our reading
- Our interpretation of a vendor statement, labeled so you can check it against the source.
- Our classification
- Interface labels (menus, code, syntax) are our own shorthand, not vendor claims.
How often we re-check
Every record is re-checked at least quarterly. An automated weekly job also compares the pricing pages that can be read without JavaScript, and flags changes for a person to review. When a price changes, we update the record, add a line to its history, and list it on the changes page. The “updated” date changes only for substantive edits.
Limits
- Prices exclude taxes, reseller discounts, volume pricing and campus licenses.
- No hands-on testing, no expert review, no ratings. See about.
- Nothing here is legal or purchasing advice. License summaries quote and link the vendor’s terms; read them before you rely on them.
Corrections
Spotted a wrong price or an outdated term? Email info@datasciencesoftware.com with the page and, ideally, the vendor link. We check corrections against the vendor’s page and note fixes in the record history.