runsonwhat

Tails in the City's tech stack

What does Tails in the City use?

Tails in the City (tailsinthecity.com) uses at least 8 tools we can see from public records, including Rackspace Email for email and documents, Shopify for its website and Cloudflare for content delivery. Last checked .

Based in
United States
Founded
2004
Re-check liveVisit tailsinthecity.com
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Tails in the City'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

DNS

Application

4 tools, what the product is built with

AI

Media & UI

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

Companies like Tails in the City also use

Tools common among companies with a similar stack that we haven't found at Tails in the City.

Companies with a stack like Tails in the City's

Ranked by shared tools, with rare tools counting more.

Tails in the City tech stack FAQ

What tools does Tails in the City use?

We've found 8 tools at Tails in the City (tailsinthecity.com). Edge & Hosting: Cloudflare and GoDaddy. Application: Google Fonts, Vimeo and YouTube. Go-to-market: Shopify. Company Ops: Rackspace Email. Last checked October 4, 2026.

What email provider does Tails in the City use?

Tails in the City uses Rackspace Email for email and documents. We found Rackspace Email through email records.

What CMS does Tails in the City use?

Tails in the City uses Shopify for its website. We found Shopify through custom domain, DNS records and website code.

Does Tails in the City use Cloudflare?

Yes. We found Cloudflare at Tails in the City through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Tails in the City uses?

We read public traces only: Tails in the City'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.