runsonwhat

Nessum's tech stack

What does Nessum use?

Nessum (nessum.es) uses at least 13 tools we can see from public records, including Google Cloud for hosting, Zoho for sales, Google Analytics for analytics and Shopify for its website. Last checked .

Size
1–10 employees
Based in
Spain
Founded
2025
LinkedIn
Company page
Tools found
13
Categories
9
Layers
4 of 5
Last checked
Oct 2026

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

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Nessum tech stack FAQ

What tools does Nessum use?

We've found 13 tools at Nessum (nessum.es). Edge & Hosting: Cloudflare and Google Cloud. Data & Observability: Google Analytics, Google Tag Manager and Bugsnag. Go-to-market: Meta Pixel, Google Ads and Zoho. Last checked October 4, 2026.

What cloud does Nessum run on?

Nessum uses Google Cloud for hosting. We found Google Cloud through DNS records.

What CRM does Nessum use?

Nessum uses Zoho for sales and CRM. We found Zoho through DNS verification records and email records.

What analytics tools does Nessum use?

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

What CMS does Nessum use?

Nessum uses Shopify for its website. We found Shopify through custom domain, DNS records and website code.

What marketing software does Nessum use?

Nessum uses Klaviyo and Judge.me for marketing. We found Klaviyo through custom domain, DNS verification records and website code.

Does Nessum use Cloudflare?

Yes. We found Cloudflare at Nessum through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Nessum uses?

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