Start A Fire's tech stack
What does Start A Fire use?
Start A Fire (startafire.com) uses at least 9 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Internet
- Size
- 11–50 employees
- Based in
- Tel Aviv-Yafo, Israel
- Founded
- 2013
- Company page
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Start A Fire'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
4 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Start A Fire tech stack FAQ
What tools does Start A Fire use?
We've found 9 tools at Start A Fire (startafire.com). Edge & Hosting: Amazon Route 53, Google Cloud and Amazon CloudFront. Application: Google Fonts. Data & Observability: Google Analytics. Go-to-market: Pinterest. Company Ops: Google Workspace and SendGrid. Last checked October 6, 2026.
What cloud does Start A Fire run on?
Start A Fire uses Google Cloud and WP Engine for hosting. We found Google Cloud through custom domain.
What email provider does Start A Fire use?
Start A Fire uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Start A Fire use?
Start A Fire uses Google Analytics for analytics. We found Google Analytics through website code.
Does Start A Fire use Google Analytics?
Yes. We found Google Analytics at Start A Fire through website code. Google Analytics is used by 725,202 companies we track.
How does runsonwhat know what Start A Fire uses?
We read public traces only: Start A Fire'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.