runsonwhat

Weddingspaces's tech stack

What does Weddingspaces use?

Weddingspaces (weddingspaces.com) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Intercom for customer support, Google Analytics for analytics and Cookiebot for security. Last checked .

Industry
IT Services
Size
51–200 employees
Based in
Utrecht, Netherlands
Founded
2021
LinkedIn
Company page
Tools found
9
Categories
7
Layers
5 of 5
Last checked
Oct 2026

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

1 tool, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Weddingspaces tech stack FAQ

What tools does Weddingspaces use?

We've found 9 tools at Weddingspaces (weddingspaces.com). Edge & Hosting: Amazon Web Services. Application: Font Awesome. Data & Observability: Google Analytics, Hotjar and GrowthBook. Go-to-market: Google Ads, Meta Pixel and Intercom. Company Ops: Cookiebot. Last checked October 6, 2026.

What cloud does Weddingspaces run on?

Weddingspaces uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What does Weddingspaces use for customer support?

Weddingspaces uses Intercom for customer support. We found Intercom through website code.

What analytics tools does Weddingspaces use?

Weddingspaces uses Google Analytics and Hotjar for analytics. We found Google Analytics through website code.

Does Weddingspaces use Google Analytics?

Yes. We found Google Analytics at Weddingspaces through website code. Google Analytics is used by 732,368 companies we track.

How does runsonwhat know what Weddingspaces uses?

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