# What does Quave use?

Quave (quave.dev) shows public evidence of 5 tools, according to runsonwhat (last checked 2026-10-29).

- Industry: IT Services
- Size: 11–50 employees
- Based in: Brazil
- Founded: 2013
- LinkedIn: https://www.linkedin.com/company/quave

## Edge & Hosting

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Amazon Route 53](https://www.runsonwhat.com/reverse/route53) | DNS | DNS records |  |

## Application

| Tool | Category | Evidence | Since |
|---|---|---|---|
| [Font Awesome](https://www.runsonwhat.com/reverse/fontawesome) | Media & UI | Website code |  |
| [Next.js](https://www.runsonwhat.com/reverse/nextjs) | 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 Quave use?

As of October 2026, runsonwhat has found 5 tools at Quave (quave.dev) in public records. Edge & Hosting: Amazon Route 53. Application: Font Awesome and Next.js. Company Ops: Google Workspace. Last checked October 29, 2026.

### What email provider does Quave use?

Quave uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 406,793 companies runsonwhat tracks.

### Does Quave use Font Awesome?

Yes. runsonwhat found Font Awesome at Quave through Font Awesome code on quave.dev. Font Awesome is a Media & UI tool used by 458,291 companies runsonwhat tracks.

### How does runsonwhat know what Quave uses?

runsonwhat reads public records only. Of the 5 tools at Quave, 2 were found through DNS records, 2 through code on quave.dev and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and quave.dev about monthly.


---

Source: runsonwhat, https://www.runsonwhat.com/company/quave.dev (updated October 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.