runsonwhat

Big Parser's tech stack

What does Big Parser use?

Big Parser (bigparser.com) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, ReadMe for customer support, Amazon CloudFront for content delivery and SendGrid for email delivery. Last checked .

Industry
Software
Size
51–200 employees
Based in
Reston, United States
LinkedIn
Company page
Re-check liveVisit bigparser.com
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Big Parser's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Edge & Hosting

3 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

2 tools, what the product is built with

Media & UI

Go-to-market

2 tools, how they find and keep customers

Marketing

Support & Docs

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Companies like Big Parser also use

Tools common among companies with a similar stack that we haven't found at Big Parser.

Companies with a stack like Big Parser's

Ranked by shared tools, with rare tools counting more.

Big Parser tech stack FAQ

What tools does Big Parser use?

We've found 8 tools at Big Parser (bigparser.com). Edge & Hosting: Amazon Web Services, Amazon CloudFront and IONOS. Application: YouTube and Vimeo. Go-to-market: ReadMe. Company Ops: SendGrid. Last checked October 6, 2026.

What cloud does Big Parser run on?

Big Parser uses Amazon Web Services and IONOS for hosting. We found Amazon Web Services through custom domain.

What does Big Parser use for customer support?

Big Parser uses ReadMe for customer support. We found ReadMe through custom domain.

Does Big Parser use SendGrid?

Yes. We found SendGrid at Big Parser through email records. SendGrid is used by 183,234 companies we track.

How does runsonwhat know what Big Parser uses?

We read public traces only: Big Parser's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.