How we verify a price
Software pricing is published for people to read and almost never for machines. Vendors put it behind toggles, split it across plans and add-ons, and change it without notice. Most comparison sites solve that by asking vendors what their prices are. We solve it by reading the vendor page and keeping a copy of what we read.
What is a binding?
Every component in the catalog, every plan, add-on and consumable, is stored with the capture it was extracted from and the span of text inside that capture where the value appeared. Not a citation someone typed afterwards. The link is made when the value is extracted, and a value that cannot be bound to a source does not become a component.
What is a binding not?
It is not a promise that the price is correct today. A vendor can change a page an hour after we read it and nothing tells us. What the binding gives you is the ability to find out: the address we read, and the day we read it. If the two disagree now, you have learned something real, and you learned it from us rather than in spite of us.
It is also not a copy of the vendor's page served back to you. We link to the vendor and nothing else.
What gets marked due for re-reading?
A catalog that never admits it is out of date is a catalog you cannot use. Each product is either currently researched or flagged to be read again, and a flagged product still holds real data. It has been through the same extraction and the same binding; it is simply overdue.
We publish that split rather than the total on its own, because the total on its own is the sentence someone would quote.
See it on a product
Every product page in Juukbox carries the same provenance this page describes: the plans, the amounts, and where each came from.