runsonwhat

Lavide Holding N.v.'s tech stack

What does Lavide Holding N.v. use?

Lavide Holding N.v. (lavideholding.com) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Stripe for payments, WordPress for its website and SendGrid for email delivery. Last checked .

Industry
Financial Services
Size
11–50 employees
Based in
Heemstede, Netherlands
LinkedIn
Company page
Tools found
12
Categories
8
Layers
3 of 5
Last checked
Oct 2026

Lavide Holding N.v.'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.

Application

5 tools, what the product is built with

Go-to-market

3 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Lavide Holding N.v. tech stack FAQ

What tools does Lavide Holding N.v. use?

We've found 12 tools at Lavide Holding N.v. (lavideholding.com). Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 2, 2026.

What email provider does Lavide Holding N.v. use?

Lavide Holding N.v. uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.

What payment provider does Lavide Holding N.v. use?

Lavide Holding N.v. uses Stripe for payments. We found Stripe through website code.

What CMS does Lavide Holding N.v. use?

Lavide Holding N.v. uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Lavide Holding N.v. use Microsoft 365?

Yes. We found Microsoft 365 at Lavide Holding N.v. through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Lavide Holding N.v. uses?

We read public traces only: Lavide Holding N.v.'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.