Cloud Foundry vs Tencent Cloud

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 Tencent Cloud is

Tencent Cloud is a proprietary cloud platform; this record focuses on the international Cloud Virtual Machine (CVM) service. CVM supports prepaid monthly/annual subscription, per-second pay-as-you-go settled hourly, spot and other purchasing models. The VM bill combines CPU/memory, system and data disks, images and public network usage. Shutdown waives compute only for eligible pay-as-you-go configurations; ineligible instances and retained disks, IPs or snapshots can continue charging. Services and rules differ between mainland China and international regions.

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

Cloud Virtual Machine

Provides regional virtual compute with multiple instance types, images and attached disks.

Billing modes

Offers prepaid subscription, per-second pay-as-you-go, spot and commitment-oriented purchasing.

Network and placement

Uses VPCs, subnets, security groups, EIPs and availability zones for workload topology.

Images and snapshots

Captures disk state and templates within documented zone and region boundaries.

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 Tencent Cloud if

• Asia-Pacific workloads after confirming service availability in the intended international region
• Elastic server fleets provisioned through CVM APIs and infrastructure automation
• Fault-tolerant batch jobs that can safely use interruptible spot capacity

Skip Tencent Cloud if

• The architecture assumes mainland and international products or rules are interchangeable
• The cost model ignores disks, public bandwidth, images, snapshots and retained stopped resources
• The application cannot tolerate spot reclamation and has no multi-AZ or backup design

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.

Tencent Cloud: pros & cons

• Flexible compute purchasing: Subscription, pay-as-you-go and interruptible spot options fit stable or variable workloads.
• API provisioning: CVM instances can be purchased and managed through the international console or signed HTTPS APIs.
• Regional isolation: Regions and availability zones expose explicit placement, private networking and cross-AZ recovery patterns.
• Supporting primitives: Cloud disks, snapshots, images, security groups, load balancing and monitoring compose production systems.
• Multi-part invoice: Compute, disks and network are separately relevant to total CVM cost.
• Shutdown rules are conditional: Only eligible pay-as-you-go instances stop compute charges after shutdown.
• Spot and overdue risk: Spot capacity can be repossessed and overdue/expired instances can ultimately be released unrecoverably.
• Regional policy differences: Available types, image/OS operations, latency, compliance and network behavior vary by location.