runsonwhat

Lunchly's tech stack

What does Lunchly use?

Lunchly (lunchly.com) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Microsoft Clarity for analytics, Shopify for its website and Klaviyo for marketing. Last checked .

Size
1–10 employees
Based in
Louisville, United States
LinkedIn
Company page
Tools found
14
Categories
12
Layers
5 of 5
Last checked
Oct 2026

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

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Collaboration

Security & Compliance

Lunchly tech stack FAQ

What tools does Lunchly use?

We've found 14 tools at Lunchly (lunchly.com). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Vimeo and YouTube. Data & Observability: Microsoft Clarity and Bugsnag. Go-to-market: Shopify and Klaviyo. Company Ops: Microsoft 365, Box and UserWay. Last checked October 4, 2026.

What email provider does Lunchly use?

Lunchly uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Lunchly use?

Lunchly uses Microsoft Clarity for analytics. We found Microsoft Clarity through website code.

What CMS does Lunchly use?

Lunchly uses Shopify for its website. We found Shopify through custom domain, DNS records and website code.

What marketing software does Lunchly use?

Lunchly uses Klaviyo for marketing. We found Klaviyo through DNS verification records.

Does Lunchly use Microsoft 365?

Yes. We found Microsoft 365 at Lunchly through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Lunchly uses?

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