runsonwhat

Tickets.com's tech stack

What does Tickets.com use?

Tickets.com (tickets.com) uses at least 31 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Okta for sign-in. Last checked .

Industry
Entertainment
Based in
United States
Re-check liveVisit tickets.com
Tools found
31
Categories
15
Layers
5 of 5
Last checked
Oct 2026

Tickets.com'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

6 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

DNS

Application

5 tools, what the product is built with

Frontend

Auth & Identity

AI

Data & Observability

4 tools, what they measure and store

Monitoring

Analytics

Go-to-market

3 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

13 tools, what the team runs on day to day

Email Delivery

Workspace

Collaboration

Dev Tools

Security & Compliance

Companies like Tickets.com also use

Tools common among companies with a similar stack that we haven't found at Tickets.com.

Companies with a stack like Tickets.com's

Ranked by shared tools, with rare tools counting more.

Tickets.com tech stack FAQ

What tools does Tickets.com use?

As of October 2026, runsonwhat has found 31 tools at Tickets.com (tickets.com) in public records. Edge & Hosting: Amazon Web Services, Amazon Route 53 and Google Cloud. Application: React, Tailwind CSS and OpenAI. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Google Ads and Meta Pixel. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 10, 2026.

What cloud does Tickets.com run on?

Tickets.com uses Amazon Web Services for hosting and cloud infrastructure, alongside Google Cloud, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through Amazon Web Services code on tickets.com. Amazon Web Services is used by 144,602 companies runsonwhat tracks.

What email provider does Tickets.com use?

Tickets.com uses Microsoft 365 for email and office software, alongside Apple Business, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365 and email records. Microsoft 365 is used by 698,176 companies runsonwhat tracks.

What analytics tools does Tickets.com use?

Tickets.com uses Google Analytics for analytics, alongside Google Tag Manager and PostHog, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on tickets.com. Google Analytics is used by 847,627 companies runsonwhat tracks.

What does Tickets.com use for login and identity?

Tickets.com uses Okta for sign-in and identity, according to runsonwhat (October 2026). runsonwhat found Okta through a subdomain that points at Okta and configuration files. Okta is used by 1,792 companies runsonwhat tracks.

What monitoring tools does Tickets.com use?

Tickets.com uses Sentry for monitoring, according to runsonwhat (October 2026). runsonwhat found Sentry through Sentry code on tickets.com. Sentry is used by 76,760 companies runsonwhat tracks.

Does Tickets.com use Google Ads?

Yes. runsonwhat found Google Ads at Tickets.com through Google Ads code on tickets.com. Google Ads is a Ads & Pixels tool used by 454,191 companies runsonwhat tracks.

Does Tickets.com use AI tools?

Yes. runsonwhat has found OpenAI at Tickets.com; OpenAI, for example, through a DNS verification record for OpenAI. AI services called only from servers leave no public trace, so Tickets.com may use more AI tools than these.

Which companies have a tech stack similar to Tickets.com's?

The companies with the stacks most like Tickets.com's are SPS Commerce, DoubleVerify, F5 and Redis, according to runsonwhat (October 2026). Each shares 4 to 18 tools with Tickets.com, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Tickets.com uses?

runsonwhat reads public records only. Of the 31 tools at Tickets.com, 14 were found through DNS records, 11 through code on tickets.com, 4 through subdomains that point at the vendor and 2 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and tickets.com about 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.