runsonwhat

Winking Fig's tech stack

What does Winking Fig use?

Winking Fig (winkingfig.com) uses at least 6 tools we can see from public records, including Vercel for hosting, PostHog for analytics, Cloudflare for content delivery and Resend for email delivery. Last checked .

Size
1–10 employees
Based in
Chicago, United States
Founded
2025
LinkedIn
Company page
Re-check liveVisit winkingfig.com
Tools found
6
Categories
6
Layers
5 of 5
Last checked
Oct 2026

Winking Fig'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

CDN & Edge

Application

1 tool, what the product is built with

Frontend

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Companies like Winking Fig also use

Tools common among companies with a similar stack that we haven't found at Winking Fig.

Companies with a stack like Winking Fig's

Ranked by shared tools, with rare tools counting more.

Winking Fig tech stack FAQ

What tools does Winking Fig use?

We've found 6 tools at Winking Fig (winkingfig.com). Edge & Hosting: Cloudflare and Vercel. Application: Next.js. Data & Observability: PostHog. Company Ops: Resend. Last checked October 2, 2026.

What cloud does Winking Fig run on?

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

What analytics tools does Winking Fig use?

Winking Fig uses PostHog for analytics. We found PostHog through website code.

Does Winking Fig use Cloudflare?

Yes. We found Cloudflare at Winking Fig through email records and DNS records. Cloudflare is used by 518,135 companies we track.

How does runsonwhat know what Winking Fig uses?

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