Leaseweb CDN vs Swissnode

Compare Leaseweb CDN y Swissnode en capacidades, jurisdicción, garantías y encaje para compradores europeos.

Logo: Leaseweb CDN

Leaseweb CDN

Netherlands· Web Hosting and Cloud Computing

Needs review

Shortlist when you want a Dutch (or other local Leaseweb) B2B contract that fronts four partner CDNs with NS1 Pulsar steering and included Amsterdam or Washington, D.C. origin shields. Skip when you need EU-only processors, named partner inventory up front, Cloudflare-class WAF or Workers, or signed URLs without a shield hop. Consider Cloudflare for a single global edge platform, or OVHcloud if you want a French-operated CDN attached to EU datacentres.

Dutch sales entityMulti-CDN (4 partners)Origin shield (AMS + WDC)Portal + REST APIISO 27001 (company, claimed)
Leaseweb CDN vs Swissnode: Resumen
CaracterísticaLogo: Leaseweb CDNLeaseweb CDNLogo: SwissnodeSwissnode
País de origenNetherlandsSwitzerland
CategoríaWeb Hosting and Cloud ComputingEmail Services
Código abiertoNoNo
AutoalojadoNoNo
SedeNetherlandsNo indicado
Entidad legalLeaseweb Netherlands B.V. (KvK 30141839, Amsterdam). Website: Leaseweb Global B.V. (KvK 60593652). Other local sales entities exist.No indicado
Matriz / control EE.UU.Sin matriz estadounidense conocidaNo indicado
Exposición CLOUD Act (indicativa)MedioNo indicado
Alojamiento / residenciaDelivery is a mix of four unnamed third-party CDNs (global PoPs). Leaseweb origin shields in Amsterdam and Washington, D.C. Request steering via NS1 Pulsar. Origins may be customer HTTP hosts or S3-compatible buckets (including AWS). Raw logs (including client IP) collected from partners and optionally written to customer S3. No public CDN subprocessor list naming the four partners.No indicado
Resumen

Dutch Multi-CDN that steers traffic across four partner networks with NS1 Pulsar, plus included origin shields in Amsterdam and Washington, D.C. Sold under local Leaseweb sales entities.

European cPanel email, shared web hosting, and KVM VPS under the Swissnode brand—vendor-stated Spain data center after Swiss DC closure, with optional Cloudflare CDN on web plans.

Etiquetas
De un vistazo: Leaseweb CDN vs Swissnode
De un vistazoLogo: Leaseweb CDNLeaseweb CDNLogo: SwissnodeSwissnode
HQAmsterdam, NetherlandsNo indicado
Website operatorLeaseweb Global B.V. (KvK 60593652)No indicado
Typical NL contractLeaseweb Netherlands B.V. (KvK 30141839)No indicado
Founded1997 (vendor, 2023 press)No indicado
Product typeManaged Multi-CDN (not self-hosted, not open source)No indicado
EdgeFour unnamed partner CDNs, 400+ PoPs (vendor claim)No indicado
Shield locationsAmsterdam and Washington, D.C.No indicado
SteeringNS1 Pulsar (Volume: cost; Premium: QoE)No indicado
Commercial modelB2B traffic tiers, annual commitmentNo indicado
Key capabilities: Leaseweb CDN vs Swissnode
Key capabilitiesLogo: Leaseweb CDNLeaseweb CDNLogo: SwissnodeSwissnode
Dutch sales entityNo indicado
Multi-CDN (4 partners)No indicado
Origin shield (AMS + WDC)No indicado
Portal + REST APINo indicado
ISO 27001 (company, claimed)No indicado

Leaseweb CDN

  • Four-provider Multi-CDN (400+ PoPs claimed)

    Leaseweb sells a managed mix of four unnamed third-party CDNs and claims more than 400 points of presence. One distribution CNAME (examples in docs: di-xxxx.leasewebultracdn.com, *.pr.lswcdn.net, *.vo.lswcdn.net) fronts the mix. Features are limited to the common subset all four support. You cannot pin a user to a specific PoP.

  • NS1 Pulsar Volume and Premium steering

    Leaseweb says it connects partner performance to NS1 Pulsar real-user metrics. Volume tier chooses the most cost-effective partner at similar latency. Premium tier chooses on latency and quality of experience. Regional DNS logic can still send a whole region to a single partner when that path is faster.

  • Origin shields in Amsterdam and Washington, D.C.

    Shield CDN distributions add a Leaseweb cache layer so partner edges do not all hit origin. Marketing states shields are included on Volume and Premium and sit in Amsterdam and Washington, D.C. Shields support multiple path policies, origin groups (up to 10 hosts, round-robin, consistent, sticky, or failover), and tokenized URLs. Wildcard invalidation is not supported on shields. A Multi-CDN invalidation does not clear the shield automatically.

  • HTTP, S3, and object-storage origins

    Simple origins take a hostname or IP. AWS Signature Version 4 can authenticate S3-compatible buckets (Leaseweb Object Storage or AWS). Advanced origins (custom ports, subdirectory) work only behind shields and do not support Sig V4. Authenticated object storage cannot join an origin group. Each origin is HTTP or HTTPS exclusively, not mixed.

  • Portal, REST API, and raw logs to S3

    Distributions, origins, certificates, and invalidations are managed in the Leaseweb Customer Portal (CDN menu, active contract required) or via the documented REST API on developer.leaseweb.com. Raw logs from all partners can be normalized to JSON and uploaded as .gz files to a customer S3 bucket. Leaseweb states logs are informational only and may be delayed or incomplete versus billing records.

  • Cache templates and edge ACLs

    Web, live, and VoD templates set methods, TTL, compression, and stale-serve defaults. Operators can force CDN-controlled or origin-controlled cache, passthrough or static headers, geo blocking, IP-subnet blocking, and referrer allowlists. HTTP/2 is default on all partners. Gzip delivery compression applies only to files up to 20 MB. CORS Access-Control-Allow-Origin is stripped unless you passthrough or set it.

Swissnode

  • Residencia de datos suiza

    Correo y datos web permanecen en instalaciones suizas, apoyando narrativas de clientes sobre jurisdicción y ley de acceso distinta de proveedores estadounidenses.

  • Alojamiento de correo de dominio

    Direcciones profesionales en su propio dominio con filtrado antispam, webmail y asistencia de migración desde hosts heredados.

  • Paquetes de hosting web

    Hosting compartido y gestionado para sitios corporativos, WordPress y pequeños e-commerce con contactos de soporte locales.

  • Soporte local y orientación al cumplimiento

    Soporte en alemán y contratos orientados a expectativas suizas de privacidad (nFADP) y clientes UE que necesitan subprocesadores documentados.

Assurance & compliance: Leaseweb CDN vs Swissnode
Assurance & complianceLogo: Leaseweb CDNLeaseweb CDNLogo: SwissnodeSwissnode
Independent security / no-logs audit
Not found

Multi-CDN collects partner access logs (IP, URI, cache status) and can ship them to S3. No public independent audit of CDN logging or routing found.

No indicado
ISO 27001
Vendor claimed

ISO 27001:2022 via EY CertifyPoint for multiple entities including Leaseweb Netherlands B.V. and Leaseweb Global B.V. Published certified services omit CDN (bare metal, VPS, cloud, colo, web hosting, domains). Ask for SoA / CDN scope.

No indicado
SOC 2 / SOC 3
Partial

SOC 2 published for Leaseweb Canada, Inc. colocation (Security and Availability). Not a Multi-CDN report. Several entities have SOC 1 Type II (EY) covering cloud, dedicated, colo, and web hosting, not CDN.

No indicado
GDPR / EU data protection
Vendor claimed

EU sales entities; privacy page states GDPR is taken into account. DPA in sales terms. Transfers to US entity via DPF (Leaseweb USA, Inc.). Multi-CDN partners unnamed.

No indicado
US CLOUD Act exposure (indicative)
Partial

Dutch group, no known US parent, but path includes Washington, D.C. shields, Leaseweb USA, Inc., NS1 Pulsar, and four unnamed global partner CDNs. Assessment row, not a vendor claim. Not legal advice.

No indicado
Data processing agreement (B2B)
Vendor claimed

Vendor: DPA incorporated as Clause 8 of local sales terms; additional standalone DPA on request when appropriate. Confirm Multi-CDN partners and NS1 are scheduled.

No indicado
EU AI Act
Not applicable

Content delivery and traffic steering product, not an AI system offering.

No indicado
PCI DSS
Partial

Vendor: PCI DSS 4.0 scoped to physical security at named DCs (AMS-01, FRA-01, LON-01, WDC-02, SIN-01, Montreal). Not a card-data or CDN application control.

No indicado
CISPE IaaS Code of Conduct
Vendor claimed

Company says it registered products with CISPE. Confirm whether Multi-CDN is on the public CISPE register.

No indicado
Considerations & known limitations: Leaseweb CDN vs Swissnode
Considerations & known limitationsLogo: Leaseweb CDNLeaseweb CDNLogo: SwissnodeSwissnode
Unnamed partner CDNs and NS1 in the data path
High

Delivery and RUM leave Leaseweb facilities. The four partners are not named on public product or legal pages. NS1 Pulsar steers requests. Treat as a multi-processor design until sales produces a current list and DPA schedule.

No indicado
Washington, D.C. origin shield
Medium

Included shields are in Amsterdam and Washington, D.C. Enabling a shield can place origin-pull traffic in the United States even when the sales entity is Dutch. Live streaming docs also advise against shields for latency reasons.

No indicado
ISO / SOC reports do not list CDN
Medium

Published ISO 27001 and SOC 1 service lists omit CDN. SOC 2 is Canada colocation only. Do not assume Multi-CDN inherits those reports without a scoped letter.

No indicado
Features limited to partner intersection
Medium

No Multi-CDN URL tokens, no PoP pin, Gzip-only compression with a 20 MB cap, no MPEG-DASH Gzip, mixed origin HTTP/HTTPS unsupported, invalidation rate-limited. SSL and stats propagate on partner clocks.

No indicado
Raw logs not billed as complete
Low

Partner logs shipped to S3 are informational. Leaseweb states they may be late or missing versus invoice counters. Do not use them as a legal completeness record.

No indicado

Encaje

Leaseweb CDN

Best fit when

  • Teams already on Leaseweb dedicated servers, object storage, or private cloud who want delivery on the same invoice
  • Media, ads, SaaS, or gaming publishers who want multi-CDN failover without four vendor contracts
  • Origins that can sit behind an Amsterdam or Washington, D.C. shield and pull over HTTP or HTTPS (or S3 with Sig V4)
  • Operators who will live with partner-subset features (HTTP/2, geo/IP/referrer ACLs, portal and REST API) rather than Workers-style compute
  • Buyers who can accept Volume (cost) versus Premium (QoE) steering instead of pinning a single CDN

Poor fit when

  • Organizations that require an EU-only edge with a public, named subprocessor list (partners are unnamed; WDC shield and NS1 are in path)
  • Sites that need signed URLs, a WAF, bot management, or edge functions on the same product
  • Teams that must purge thousands of URLs per minute or treat invalidation as the publish pipeline
  • Buyers who want a self-serve free tier or an open-source, self-hosted CDN
  • Workloads that need MPEG-DASH Gzip, mixed HTTP and HTTPS to one origin, or per-user PoP selection

Consider instead when

  • When: You need a single global edge with WAF, bot management, Workers, and a self-serve free tier

    Consider: Cloudflare

    US company. Broader edge platform. Different jurisdiction story.

  • When: You want CDN plus compute from one European infrastructure group and can diligence that group's own PoPs

    Consider: OVHcloud

    French operator. Own datacentres. Not a four-provider multi-CDN.

  • When: You mainly need EU origin compute and will add a CDN you can inventory yourself

    Consider: Hetzner or Scaleway

    Neither replaces Multi-CDN. They keep origin in EU facilities you can name.

  • When: You wanted Swiss-branded hosting with optional Cloudflare, not a multi-CDN fabric

    Consider: Swissnode

    Different product class. Optional Cloudflare on web plans.

Swissnode

Best fit when

No indicado

Poor fit when

No indicado

Open questions for due diligence

Leaseweb CDN

  • What are the current four partner CDN legal names, and can they be listed in the DPA?
  • Can routing be constrained to EU (or named) partners and the Amsterdam shield only?
  • Is Multi-CDN in the current ISO 27001 statement of applicability?
  • Will Leaseweb sign a standalone DPA that covers NS1 Pulsar and each partner?
  • What is the current annual-commitment commercial offer (confirm on the official Multi-CDN page or with sales)?

Swissnode

No indicado