runsonwhat

Wavect.io's tech stack

What does Wavect.io use?

Wavect.io (wavect.io) uses at least 12 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, PostHog for analytics and Cloudflare for content delivery. Last checked .

Industry
Blockchain
Size
1–10 employees
Based in
Ampass, Austria
Founded
2018
LinkedIn
Company page
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Wavect.io'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

3 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Wavect.io tech stack FAQ

What tools does Wavect.io use?

We've found 12 tools at Wavect.io (wavect.io). Edge & Hosting: Cloudflare, Vercel and OVHcloud. Application: YouTube and Font Awesome. Data & Observability: PostHog and Umami. Go-to-market: Pinterest. Company Ops: Google Workspace and SendGrid. Last checked October 4, 2026.

What cloud does Wavect.io run on?

Wavect.io uses Vercel and OVHcloud for hosting. We found Vercel through DNS verification records.

What email provider does Wavect.io use?

Wavect.io uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Wavect.io use?

Wavect.io uses PostHog and Umami for analytics. We found PostHog through website code.

Does Wavect.io use Cloudflare?

Yes. We found Cloudflare at Wavect.io through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Wavect.io uses?

We read public traces only: Wavect.io'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.