runsonwhat

Lizza's tech stack

What does Lizza use?

Lizza (lizza.link) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Google Analytics for analytics and Sentry for monitoring. Last checked .

“One of the largest influencer marketing and UGC creator platforms in Latin America. Discover, manage, and pay 20,000+ verified creators across Mexico and LATAM.”

Industry
Retail
Size
1–10 employees
Based in
Guadalajara, Mexico
Founded
2023
LinkedIn
Company page
Tools found
9
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Lizza'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

Hosting & Cloud

Application

1 tool, what the product is built with

Backend & Database

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

Lizza tech stack FAQ

What tools does Lizza use?

We've found 9 tools at Lizza (lizza.link). Edge & Hosting: Vercel and Namecheap. Application: Supabase. Data & Observability: Google Analytics and Sentry. Go-to-market: Meta Pixel. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.

What cloud does Lizza run on?

Lizza uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.

What email provider does Lizza use?

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

What analytics tools does Lizza use?

Lizza uses Google Analytics for analytics. We found Google Analytics through website code.

Does Lizza use Google Workspace?

Yes. We found Google Workspace at Lizza through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Lizza uses?

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