Gandi vs JSDelivr

What Gandi is

Gandi is an ICANN-oriented domain registrar with a large TLD catalog plus Anycast LiveDNS, DNSSEC, web and email forwarding, WHOIS privacy where registries permit it, an API, SSL and separate email/hosting products. Domain cost is not flat: creation, transfer, renewal, owner change and post-expiry restore differ by extension, country, currency, tax and promotional period. A low first-year price can therefore be far below the recurring renewal price.

What JSDelivr is

jsDelivr is a publicly available CDN for open-source files from npm, GitHub, WordPress and selected custom endpoints. Its terms permit free personal and commercial use without bandwidth or request limits when content and usage follow both jsDelivr and upstream-platform policies. The network uses multiple CDN providers and offers exact or aliased version URLs, an API, combination and optimization features. Production consumers should pin an exact reviewed release: aliases can resolve to newer code. The service is not general file/media hosting, private package delivery or a substitute for package, license and resilience review.

What Gandi is built to do

Domain lifecycle

Registers, transfers, renews, changes ownership and restores supported extensions.

LiveDNS

Hosts Anycast DNS with DNSSEC, templates, bulk operations and managed record changes.

Privacy and security

Offers registry-dependent WHOIS masking, account MFA and domain activity controls.

API and delegation

Automates domain/DNS work and delegates scoped permissions through organizations and teams.

What JSDelivr is built to do

Public package endpoints

Serves files from npm, GitHub, WordPress and approved custom open-source sources.

Multi-CDN routing

Uses multiple providers and monitoring-based failover for public asset delivery.

Version selection

Supports exact releases and convenient aliases; exact pins are safer for reproducible production builds.

Package API

Returns versions, files, entry points, CDN links and download statistics for tooling.

Choose Gandi if

• Domain portfolios needing API-driven DNS, templates and delegated administration
• Registrants who compare registration, renewal, transfer and restore cost for each exact TLD
• Teams wanting registrar, DNS, forwarding and optional email/hosting in one account

Skip Gandi if

• The decision uses only a first-year promotion and ignores recurring renewal or restore fees
• The required TLD does not permit the expected privacy, transfer or ownership workflow
• Domain access, recovery contacts, MFA and off-provider DNS exports are not governed

Choose JSDelivr if

• Public npm or GitHub packages that need zero-cost global asset delivery
• Static sites using exact reviewed dependency versions
• Open-source maintainers who want public package metadata and download statistics

Skip JSDelivr if

• The workload is proprietary, private, general-purpose storage or large-scale media hosting
• The application requires negotiated uptime and support-response commitments
• Security policy cannot allow a third-party domain or the build cannot pin and review dependencies

Gandi: pros & cons

• Published lifecycle pricing: Gandi exposes creation, transfer, renewal, owner-change and restore prices by TLD.
• Included DNS tooling: LiveDNS provides Anycast nameservers, DNSSEC, templates and record history/rollback capabilities.
• Domain automation: A public API and bulk configuration tools support portfolio administration.
• Privacy controls: WHOIS masking is enabled by default where registry rules allow it, with WebAuthn account MFA available.
• Renewal can dwarf registration: The reviewed .com example was €11 to register and €31.98 to renew before tax in France.
• Promotions are temporary: Registry campaigns, exchange rates and country pricing can change both availability and cost.
• Privacy is not universal: Registry policy, registrant type and jurisdiction can prevent complete WHOIS masking.
• Bundled services have boundaries: Free SSL is described as first-year and hosting/mail products require their own entitlement review.

JSDelivr: pros & cons

• Free permitted use: The published terms allow personal and commercial use without request or bandwidth limits.
• Broad public-package access: npm, GitHub and WordPress paths cover common open-source distribution workflows.
• Resilient delivery design: Multiple CDN and DNS providers plus health-based routing reduce dependence on one edge network.
• Developer tooling: Public APIs expose package versions, files, entry points, CDN URLs and download statistics.
• Strict usage scope: General image, video, backup or bulk file hosting is prohibited.
• Mutable aliases add risk: Unpinned version ranges or latest URLs can deliver code different from a reviewed build.
• Upstream rules still apply: Content must satisfy npm, GitHub or other source-platform terms as well as jsDelivr's policy.
• Free support is limited: Published terms promise a reasonable level of issue/email support, not a customer-specific response SLA.