runsonwhat

Ticket I/o GmbH's tech stack

What does Ticket I/o GmbH use?

Ticket I/o GmbH (ticket.io) uses at least 22 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, HubSpot for sales and Zendesk for customer support. Last checked .

Industry
IT Services
Size
51–200 employees
Based in
Köln, Germany
Founded
2014
LinkedIn
Company page
Tools found
22
Categories
16
Layers
5 of 5
Last checked
Oct 2026

Ticket I/o GmbH'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

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

Ticket I/o GmbH tech stack FAQ

What tools does Ticket I/o use?

As of October 2026, runsonwhat has found 22 tools at Ticket I/o (ticket.io) in public records. Edge & Hosting: Amazon Web Services and Amazon Route 53. Application: jQuery, Anthropic and Vue.js. Data & Observability: UptimeRobot. Go-to-market: WordPress, Meta Pixel and Yoast SEO. Company Ops: Google Workspace, Apple Business and Atlassian. Last checked October 15, 2026.

What cloud does Ticket I/o run on?

Ticket I/o uses Amazon Web Services for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through a subdomain that points at Amazon Web Services and code on ticket.io. Amazon Web Services is used by 144,878 companies runsonwhat tracks.

What CRM does Ticket I/o use?

Ticket I/o uses HubSpot for its CRM, according to runsonwhat (October 2026). runsonwhat found HubSpot through a subdomain that points at HubSpot. HubSpot is used by 92,110 companies runsonwhat tracks.

What email provider does Ticket I/o use?

Ticket I/o uses Google Workspace for email and office software, alongside Apple Business, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on ticket.io. Google Workspace is used by 397,574 companies runsonwhat tracks.

What does Ticket I/o use for customer support?

Ticket I/o uses Zendesk for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Zendesk through email records that authorize Zendesk and code on ticket.io. Zendesk is used by 40,934 companies runsonwhat tracks.

What is Ticket I/o's website built with?

Ticket I/o uses WordPress for its website, alongside Yoast SEO and HubSpot CMS, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on ticket.io. WordPress is used by 582,767 companies runsonwhat tracks.

Does Ticket I/o use jQuery?

Yes. runsonwhat found jQuery at Ticket I/o through jQuery code on ticket.io. jQuery is a Frontend tool used by 897,845 companies runsonwhat tracks.

Does Ticket I/o use AI tools?

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

Which companies have a tech stack similar to Ticket I/o's?

The companies with the stacks most like Ticket I/o's are Overview.ai, Nickel Technology, AROYA and Quotemedia, according to runsonwhat (October 2026). Each shares 5 to 9 tools with Ticket I/o, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Ticket I/o uses?

runsonwhat reads public records only. Of the 22 tools at Ticket I/o, 8 were found through DNS records, 6 through subdomains that point at the vendor, 4 through code on ticket.io and 4 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and ticket.io 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.