Sessions's tech stack
What does Sessions use?
Sessions (sessions.com) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Webflow for its website. Last checked .
- Industry
- Clothing
- Based in
- United States
- Founded
- 1985
- Tools found
- 8
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Sessions'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
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Workspace
Sessions tech stack FAQ
What tools does Sessions use?
We've found 8 tools at Sessions (sessions.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: Webflow. Company Ops: Google Workspace. Last checked October 3, 2026.
What cloud does Sessions run on?
Sessions uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Sessions use?
Sessions uses Google Workspace for email and documents. We found Google Workspace through DNS verification records and email records.
What analytics tools does Sessions use?
Sessions uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Sessions use?
Sessions uses Webflow for its website. We found Webflow through custom domain, DNS verification records and website code.
Does Sessions use jQuery?
Yes. We found jQuery at Sessions through website code. jQuery is used by 590,281 companies we track.
How does runsonwhat know what Sessions uses?
We read public traces only: Sessions'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.