Lumber's tech stack
What does Lumber use?
Lumber (lumber.dev) uses at least 11 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Segment for analytics and Contentful for its website. Last checked .
- Industry
- IT Services
- Size
- 11–50 employees
- Based in
- New York, United States
- Founded
- 2018
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Lumber'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
4 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Lumber tech stack FAQ
What tools does Lumber use?
We've found 11 tools at Lumber (lumber.dev). Edge & Hosting: Google Cloud and Netlify. Application: Google Fonts, React and Adobe Fonts. Data & Observability: Segment. Go-to-market: Contentful. Company Ops: Google Workspace and SendGrid. Last checked October 6, 2026.
What cloud does Lumber run on?
Lumber uses Google Cloud and Netlify for hosting. We found Google Cloud through DNS records.
What email provider does Lumber use?
Lumber uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Lumber use?
Lumber uses Segment for analytics. We found Segment through website code.
What CMS does Lumber use?
Lumber uses Contentful for its website. We found Contentful through website code.
Does Lumber use Google Fonts?
Yes. We found Google Fonts at Lumber through website code. Google Fonts is used by 525,912 companies we track.
How does runsonwhat know what Lumber uses?
We read public traces only: Lumber'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.