Cloud Foundry vs Scaleway

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 Scaleway is

Scaleway is a proprietary European cloud with virtual and GPU instances, bare metal, object/block storage, networking, Kubernetes, databases and serverless services. Virtual instances are pay-as-you-go by powered-on time; the advertised compute rate excludes storage and attached public IPv4, while list prices include IPv6 and egress. Savings Plans trade commitment for discounts. On raw instances the customer owns operating-system updates, access, application security, availability and backup design; managed products move only specified responsibilities to Scaleway.

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

Virtual instances

Offers development, general-purpose, memory, compute, GPU and other VM families.

Storage choices

Attaches local or block volumes and provides object, archive and snapshot services.

Managed cloud products

Includes Kubernetes, databases, registries and serverless services with product-specific boundaries.

Usage and commitments

Combines hourly use with optional Savings Plan discounts for committed consumption.

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 Scaleway if

• Development and production VMs whose instance family exists in the required availability zones
• European cloud strategies after legal, residency and disaster-recovery review
• Workloads benefiting from included VM egress and explicit hourly component pricing

Skip Scaleway if

• The architecture requires a service or global region footprint absent from the current catalog
• The team assumes storage, IPv4, snapshots and support are included in the compute price
• No owner exists for instance hardening, OS updates, backups and multi-zone recovery

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.

Scaleway: pros & cons

• Published component pricing: Instance families show hourly and approximate monthly compute rates by availability zone.
• Egress-inclusive VM pricing: Current list rates include outbound traffic and IPv6 for virtual instances.
• European footprint: Products run in named European regions and availability zones.
• Automation options: Console, APIs, CLI and infrastructure-as-code tooling support programmatic operations.
• Compute is not the full bill: Local/block storage, snapshots and attached public IPv4 are separate line items.
• Powered-on time bills: CPU instances accrue charges during startup and standby, not only active workload execution.
• Availability varies: Instance families, SLAs and products differ by region and availability zone.
• VM operations are customer-owned: OS patching, configuration, access control, backups and application resilience are not managed away.