runsonwhat

bigspark's tech stack

What does bigspark use?

bigspark (bigspark.dev) uses at least 9 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, HubSpot for sales and Google Analytics for analytics. Last checked .

Industry
Software
Size
51–200 employees
Based in
London, United Kingdom
Founded
2019
LinkedIn
Company page
Tools found
9
Categories
9
Layers
5 of 5
Last checked
Oct 2026

bigspark'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

2 tools, where the bytes are served from

Application

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

bigspark tech stack FAQ

What tools does bigspark use?

We've found 9 tools at bigspark (bigspark.dev). Edge & Hosting: Google Cloud and Amazon CloudFront. Application: Astro. Data & Observability: Google Analytics. Go-to-market: HubSpot. Company Ops: Google Workspace and HashiCorp Cloud. Last checked October 6, 2026.

What cloud does bigspark run on?

bigspark uses Google Cloud for hosting. We found Google Cloud through custom domain and DNS records.

What CRM does bigspark use?

bigspark uses HubSpot for sales and CRM. We found HubSpot through website code.

What email provider does bigspark use?

bigspark uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does bigspark use?

bigspark uses Google Analytics for analytics. We found Google Analytics through website code.

Does bigspark use Google Analytics?

Yes. We found Google Analytics at bigspark through website code. Google Analytics is used by 436,502 companies we track.

How does runsonwhat know what bigspark uses?

We read public traces only: bigspark'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.