SEVECU Videoovervågning's tech stack
What does SEVECU Videoovervågning use?
SEVECU Videoovervågning (sevecu.dk) uses at least 13 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics, Cloudflare for content delivery and Resend for email delivery. Last checked .
- Industry
- Security and Communication Networks
- Based in
- Denmark
- Founded
- 2012
- Tools found
- 13
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
SEVECU Videoovervågning'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
2 tools, what the product is built with
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Security & Compliance
SEVECU Videoovervågning tech stack FAQ
What tools does SEVECU Videoovervågning use?
We've found 13 tools at SEVECU Videoovervågning (sevecu.dk). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Let's Encrypt, Sectigo and DigiCert. Last checked October 4, 2026.
What cloud does SEVECU Videoovervågning run on?
SEVECU Videoovervågning uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What analytics tools does SEVECU Videoovervågning use?
SEVECU Videoovervågning uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does SEVECU Videoovervågning use Cloudflare?
Yes. We found Cloudflare at SEVECU Videoovervågning through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what SEVECU Videoovervågning uses?
We read public traces only: SEVECU Videoovervågning'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.