# What does Weft use?

Weft (weft.sh) shows public evidence of 6 tools, according to runsonwhat (last checked 2026-11-01).

## Edge & Hosting

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Amazon Route 53](https://www.runsonwhat.com/reverse/route53) | DNS | DNS records |  |
| [Amazon CloudFront](https://www.runsonwhat.com/reverse/cloudfront) | CDN & Edge | Website code |  |

## Application

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Astro](https://www.runsonwhat.com/reverse/astro) | Frontend | Website code |  |

## Company Ops

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Google Workspace](https://www.runsonwhat.com/reverse/google-workspace) | Workspace | Email records |  |

## FAQ

### What tools does Weft use?

As of November 2026, runsonwhat has found 6 tools at Weft (weft.sh) in public records. Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Astro. Company Ops: Google Workspace. Last checked November 1, 2026.

### What email provider does Weft use?

Weft uses Google Workspace for email and office software, according to runsonwhat (November 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 414,618 companies runsonwhat tracks.

### Does Weft use Amazon Route 53?

Yes. runsonwhat found Amazon Route 53 at Weft through DNS records that point at Amazon Route 53. Amazon Route 53 is a DNS tool used by 87,793 companies runsonwhat tracks.

### How does runsonwhat know what Weft uses?

runsonwhat reads public records only. Of the 6 tools at Weft, 2 were found through DNS records, 2 through code on weft.sh, 1 through email records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and weft.sh about monthly.


---

Source: runsonwhat, https://www.runsonwhat.com/company/weft.sh (updated November 2026). Counts are companies with direct public evidence of the tool (DNS records, certificates, website code, a real-browser crawl, subprocessor lists), so they are lower bounds. Methodology: https://www.runsonwhat.com/methodology.
