How we collect pricing data

Every price in this archive comes from a page the company published itself. Here is exactly how we get it, and how to make us stop.

What we collect

We read publicly published pricing pages. That is the whole source.

We do not sign in to anything. We hold no accounts and no credentials for any company we track, and we do not read anything that requires a login, a trial, a sales call or a paywall. We collect no personal data of any kind. Pricing is commercial information about a product, not information about a person.

How often, and from where

One request per company per week, on Sundays at around 02:00 UTC.

Every request comes from a single machine at 107.172.134.238. If you are looking at a log line and wondering whether it was us, that is how to tell.

Our crawler runs a real Chromium browser and sends an ordinary desktop browser user agent, which means you cannot pick us out by user agent alone. That is why the IP above is published here. If you would rather see a dedicated user agent that names us, email us and we will set one for your domain.

robots.txt

We honour robots.txt, in code, before any request is made.

If your robots.txt disallows the path your pricing page sits on, we do not fetch it. The check runs before the fetch, so there is no version of this where we look first and apologise later. If your file says no today and yes tomorrow, we will follow it.

Where a site publishes a process for requesting crawl permission, we use that process and we wait for an answer. We do not treat silence as a yes.

History before April 2026

This archive starts before we did. Records dated earlier than April 2026 come from the Internet Archive's Wayback Machine, read through its public CDX API at the rate limits it publishes. Those records say so, and they carry the date of the original capture rather than the date we read it.

What we store

Two things. The prices we extract, and, for pages we fetched ourselves, the page itself as it came back, kept as the record of where each price came from.

We keep the stored page so that a customer can check an extracted price against the source it was taken from. Our highest paid tier can request that stored copy through the API. We are telling you this here because it means the copy does not only sit in our database. This covers the pages we fetched ourselves, from April 2026 on. The older records we recovered from the Internet Archive carry prices and a hash of the page they came from, but we did not keep those pages, so there is nothing to hand back for them.

Accuracy

Prices are extracted automatically by a language model reading the stored page. It makes mistakes. Plan names get merged, a footnote gets read as a tier, an annual price gets recorded as a monthly one.

Verify against the company's own page before making a business decision on anything you read here. Every record links to the source page and carries the date it was captured, so you can check. If you find an error, tell us and we will fix the record.

Removal

Email removals@saaspricingarchive.com with the domain you are asking about. You do not need to explain why, cite anything, or be the site's legal owner. Asking is enough.

We will stop crawling the domain, take it out of the list we fetch, and reply to confirm when it is done. Expect that within five working days.

Records we have already captured stay in the archive. Each one is dated and links to the page it came from. If a specific record is wrong, tell us and we will fix it.

The same address works for a correction, a request for a different crawl frequency, a dedicated user agent, or a question about any of the above. A person reads it.