Data Methodology

Public sources, structured records, and human verification

This page explains how DevPrice selects sources, organizes prices and deals, marks unknowns, and handles updates and corrections.

Source priority

Prices, plans, product capabilities, and deal conditions are taken primarily from providers’ own pricing pages, product pages, documentation, terms, or announcements. Third-party directories and community tips are used for discovery only; material facts must be checked against an original public source.

How records are normalized

Records preserve the original currency, billing unit, region, eligibility, validity period, source URL, and latest verification date where available. Prices may be normalized for sorting when the conversion is deterministic. Unknown conditions are marked as unknown rather than guessed.

Quality gates

Automated collection and deterministic scripts handle parsing, deduplication, and anomaly checks; material factual changes are reviewed before publication. Only detail pages that meet content-quality thresholds enter a sitemap. Search results, filter parameters, and thinner details are not submitted as separate index pages.

Updates and limitations

Update frequency varies by source, and external pages can change between reviews. A displayed verification date is not a guarantee of continued availability. Open the cited source and verify it again before making a payment or business decision.

Corrections

If a price, link, region, end date, or description is wrong, use the Feedback control in the lower-right corner. Include the specific DevPrice URL, the fact to correct, and a source that can be checked.