Twin Protocol's tech stack
What does Twin Protocol use?
Twin Protocol (twinprotocol.com) uses at least 11 tools we can see from public records, including Google Workspace for email and documents, WordPress for its website, Brevo for marketing and web-vitals for monitoring. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- Seattle, United States
- Founded
- 2021
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Twin Protocol'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
1 tool, where the bytes are served from
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Workspace
Twin Protocol tech stack FAQ
What tools does Twin Protocol use?
We've found 11 tools at Twin Protocol (twinprotocol.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: web-vitals. Go-to-market: WordPress and Brevo. Company Ops: Google Workspace, Amazon SES and Resend. Last checked October 6, 2026.
What email provider does Twin Protocol use?
Twin Protocol uses Google Workspace for email and documents. We found Google Workspace through email records.
What CMS does Twin Protocol use?
Twin Protocol uses WordPress for its website. We found WordPress through website code.
What marketing software does Twin Protocol use?
Twin Protocol uses Brevo for marketing. We found Brevo through DNS verification records.
Does Twin Protocol use jQuery?
Yes. We found jQuery at Twin Protocol through website code. jQuery is used by 650,197 companies we track.
How does runsonwhat know what Twin Protocol uses?
We read public traces only: Twin Protocol'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.