runsonwhat

LUUCKA's tech stack

What does LUUCKA use?

LUUCKA (luucka.com) uses at least 14 tools we can see from public records, including Cloudways for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Stripe for payments. Last checked .

Industry
Financial Services
Size
11–50 employees
Based in
Hallandale Beach, United States
Founded
2013
LinkedIn
Company page
Tools found
14
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

6 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

LUUCKA tech stack FAQ

What tools does LUUCKA use?

We've found 14 tools at LUUCKA (luucka.com). Edge & Hosting: Cloudflare and Cloudways. Application: Google Fonts, YouTube and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel. Company Ops: Microsoft 365 and Resend. Last checked October 6, 2026.

What cloud does LUUCKA run on?

LUUCKA uses Cloudways for hosting. We found Cloudways through custom domain.

What email provider does LUUCKA use?

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

What payment provider does LUUCKA use?

LUUCKA uses Stripe for payments. We found Stripe through website code.

What analytics tools does LUUCKA use?

LUUCKA uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does LUUCKA use Microsoft 365?

Yes. We found Microsoft 365 at LUUCKA through email records. Microsoft 365 is used by 685,111 companies we track.

How does runsonwhat know what LUUCKA uses?

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