Cloud Foundry vs Gandi

What Cloud Foundry is

Cloud Foundry is an Apache-licensed, openly governed application-platform ecosystem. Developers push supported application code through the cf CLI and platform API; operators provide routing, buildpacks, container scheduling, identity, logs, quotas and service integrations. The software has no license fee, but a production foundation still requires infrastructure, load balancers, DNS/TLS, databases, blob stores, monitoring, backups, updates and skilled operations—or a separately priced commercial distribution or managed provider. Certification verifies required core components for a specific program year; it is not the same as generic API compatibility or an uptime guarantee.

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 Cloud Foundry is built to do

cf push workflow

Stages supported source or artifacts with buildpacks and schedules application instances.

Organizations and spaces

Scopes applications, routes, services, quotas and role-based access for multiple teams.

Service broker model

Provisions and binds managed services through the Open Service Broker API.

UAA identity

Provides OAuth-based platform identity with configurable LDAP and SAML federation.

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.

Choose Cloud Foundry if

• Large application portfolios that conform to buildpack or supported container workflows
• Organizations prioritizing consistent developer experience across infrastructure choices
• Internal platforms with dedicated owners for upgrades, security, observability and disaster recovery

Skip Cloud Foundry if

• The organization has only a few simple services and no platform-operations capacity
• Applications require privileged hosts, unusual kernels or infrastructure-level control
• The selected distribution has no verified lifecycle, support, certification or backup responsibility

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

Cloud Foundry: pros & cons

• Developer abstraction: A consistent cf push workflow hides much of the infrastructure configuration from application teams.
• Open governance and source: Foundation projects use open contribution, design and governance processes.
• Infrastructure choice: Cloud Foundry can be deployed on multiple IaaS environments or consumed through commercial offerings.
• Platform controls: UAA identity, RBAC, orgs, spaces, quotas, routing, logs and service brokers provide multi-team governance.
• Free software has real operating cost: Production topology, infrastructure, upgrades, security and recovery need a platform team.
• Provider experience varies: Buildpacks, services, extensions, support, certification and pricing differ among distributions.
• State remains external: Databases and bound services need their own durability, credential and restore strategy.
• Not general compute: The opinionated application model is a poor fit for workloads needing unrestricted hosts or unusual system 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.