runsonwhat

RecipeUI's tech stack

What does RecipeUI use?

RecipeUI (recipeui.com) uses at least 5 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents and Instantly for sales. Last checked .

“The open source Postman alternative.”

Industry
Engineering, Product and Design
Size
1–10 employees
Based in
San Francisco, United States
LinkedIn
Company page
Re-check liveVisit recipeui.com
Tools found
5
Categories
5
Layers
3 of 5
Last checked
Oct 2026

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

DNS

Go-to-market

2 tools, how they find and keep customers

Marketing

Sales & CRM

Company Ops

1 tool, what the team runs on day to day

Workspace

Companies like RecipeUI also use

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

Companies with a stack like RecipeUI's

Ranked by shared tools, with rare tools counting more.

RecipeUI tech stack FAQ

What tools does RecipeUI use?

We've found 5 tools at RecipeUI (recipeui.com). Edge & Hosting: Vercel and Namecheap. Go-to-market: Instantly. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does RecipeUI run on?

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

What CRM does RecipeUI use?

RecipeUI uses Instantly for sales and CRM. We found Instantly through custom domain.

What email provider does RecipeUI use?

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

Does RecipeUI use Google Workspace?

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

How does runsonwhat know what RecipeUI uses?

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