runsonwhat

Lumina's tech stack

What does Lumina use?

Lumina (lumibot.com) uses at least 8 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Amazon CloudFront for content delivery and SendGrid for email delivery. Last checked .

“AI+human powered automation on job-community platform with 1.5M…”

Industry
Operations
Size
11–50 employees
Based in
Singapore, Singapore
Re-check liveVisit lumibot.com
Tools found
8
Categories
8
Layers
4 of 5
Last checked
Oct 2026

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

CDN & Edge

DNS

Application

2 tools, what the product is built with

Frontend

Media & UI

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Lumina also use

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

Companies with a stack like Lumina's

Ranked by shared tools, with rare tools counting more.

Lumina tech stack FAQ

What tools does Lumina use?

We've found 8 tools at Lumina (lumibot.com). Edge & Hosting: Amazon Route 53, Amazon CloudFront and Vercel. Application: Google Fonts and SvelteKit. Company Ops: Google Workspace and SendGrid. Last checked October 2, 2026.

What cloud does Lumina run on?

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

What email provider does Lumina use?

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

Does Lumina use Google Workspace?

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

How does runsonwhat know what Lumina uses?

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