Theory+practice's tech stack
What does Theory+practice use?
Theory+practice (tap.work) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Webflow for its website and Cloudflare for content delivery. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Vancouver, Canada
- Founded
- 2018
- Company page
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Theory+practice'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
Theory+practice tech stack FAQ
What tools does Theory+practice use?
We've found 9 tools at Theory+practice (tap.work). Edge & Hosting: Cloudflare and Amazon Route 53. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: Google Ads, LinkedIn Insight Tag and Webflow. Company Ops: Google Workspace. Last checked October 6, 2026.
What email provider does Theory+practice use?
Theory+practice uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Theory+practice use?
Theory+practice uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Theory+practice use?
Theory+practice uses Webflow for its website. We found Webflow through custom domain, DNS verification records and website code.
Does Theory+practice use jQuery?
Yes. We found jQuery at Theory+practice through website code. jQuery is used by 589,320 companies we track.
How does runsonwhat know what Theory+practice uses?
We read public traces only: Theory+practice'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.