Blueprintr's tech stack
What does Blueprintr use?
Blueprintr (blueprintr.io) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Blueprintr'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
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Blueprintr tech stack FAQ
What tools does Blueprintr use?
We've found 10 tools at Blueprintr (blueprintr.io). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon CloudFront. Application: Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Google Workspace. Last checked October 2, 2026.
What cloud does Blueprintr run on?
Blueprintr uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Blueprintr use?
Blueprintr uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Blueprintr use?
Blueprintr uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Blueprintr use Cloudflare?
Yes. We found Cloudflare at Blueprintr through DNS records and website code. Cloudflare is used by 303,836 companies we track.
How does runsonwhat know what Blueprintr uses?
We read public traces only: Blueprintr'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.