runsonwhat

Ressence Watches's tech stack

What does Ressence Watches use?

Ressence Watches (ressence.eu) uses at least 13 tools we can see from public records, including Shopify for its website, Klaviyo for marketing, Bugsnag for monitoring and Cloudflare for content delivery. Last checked .

Industry
Watchmaker
Based in
Belgium
Founded
2010
LinkedIn
Company page
Re-check liveVisit ressence.eu
Tools found
13
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Ressence Watches'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

CDN & Edge

Application

5 tools, what the product is built with

AI

Media & UI

Data & Observability

1 tool, what they measure and store

Monitoring

Go-to-market

5 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Companies like Ressence Watches also use

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

Companies with a stack like Ressence Watches's

Ranked by shared tools, with rare tools counting more.

Ressence Watches tech stack FAQ

What tools does Ressence Watches use?

We've found 13 tools at Ressence Watches (ressence.eu). Edge & Hosting: Cloudflare and Amazon CloudFront. Application: YouTube, GSAP and Vimeo. Data & Observability: Bugsnag. Go-to-market: Meta Pixel, Shopify and Klaviyo. Last checked October 3, 2026.

What CMS does Ressence Watches use?

Ressence Watches uses Shopify for its website. We found Shopify through website code.

What marketing software does Ressence Watches use?

Ressence Watches uses Klaviyo and Kit for marketing. We found Klaviyo through website code.

Does Ressence Watches use Cloudflare?

Yes. We found Cloudflare at Ressence Watches through website code. Cloudflare is used by 304,276 companies we track.

How does runsonwhat know what Ressence Watches uses?

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