runsonwhat

Handle Delivery's tech stack

What does Handle Delivery use?

Handle Delivery (handledelivery.com) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Webflow for its website and Brevo for marketing. Last checked .

Industry
Logistics and Supply Chain
Size
11–50 employees
Based in
Los Angeles, United States
Founded
2021
LinkedIn
Company page
Tools found
9
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Handle Delivery'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

Application

1 tool, what the product is built with

Go-to-market

4 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Handle Delivery tech stack FAQ

What tools does Handle Delivery use?

We've found 9 tools at Handle Delivery (handledelivery.com). Edge & Hosting: Cloudflare, GoDaddy and Vercel. Application: jQuery. Go-to-market: Brevo, Webflow and Short.io. Company Ops: Google Workspace. Last checked October 6, 2026.

What cloud does Handle Delivery run on?

Handle Delivery uses Vercel for hosting. We found Vercel through DNS verification records and DNS records.

What email provider does Handle Delivery use?

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

What CMS does Handle Delivery use?

Handle Delivery uses Webflow for its website. We found Webflow through custom domain and website code.

What marketing software does Handle Delivery use?

Handle Delivery uses Brevo and Short.io for marketing. We found Brevo through email records.

Does Handle Delivery use jQuery?

Yes. We found jQuery at Handle Delivery through website code. jQuery is used by 600,560 companies we track.

How does runsonwhat know what Handle Delivery uses?

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