TicketSource's tech stack
What does TicketSource use?
TicketSource (ticketsource.co.uk) uses at least 15 tools we can see from public records, including Google Workspace for email and documents, Stripe for payments, Mailchimp for marketing and Cloudflare for content delivery. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Penarth, United Kingdom
- Founded
- 2004
- Company page
- Tools found
- 15
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
TicketSource'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
2 tools, what the product is built with
Payments & Billing
Go-to-market
4 tools, how they find and keep customers
Ads & Pixels
Company Ops
8 tools, what the team runs on day to day
Email Delivery
Workspace
Collaboration
TicketSource tech stack FAQ
What tools does TicketSource use?
We've found 15 tools at TicketSource (ticketsource.co.uk). Edge & Hosting: Cloudflare. Application: Anthropic and Stripe. Go-to-market: Meta Pixel, Mailchimp and Ahrefs. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 3, 2026.
What email provider does TicketSource use?
TicketSource uses Google Workspace for email and documents. We found Google Workspace through email records.
What payment provider does TicketSource use?
TicketSource uses Stripe for payments. We found Stripe through DNS verification records.
What marketing software does TicketSource use?
TicketSource uses Mailchimp and Ahrefs for marketing. We found Mailchimp through email records.
Does TicketSource use Cloudflare?
Yes. We found Cloudflare at TicketSource through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what TicketSource uses?
We read public traces only: TicketSource'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.