Cloud Foundry vs Yandex 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 Yandex Cloud is

Yandex Cloud is a proprietary cloud platform with Compute Cloud virtual machines and more than 50 infrastructure, data, container, serverless and ML services. Billing and signup depend on payer type, country and contracting entity. New business customers can receive a limited trial; new individuals start on consumption billing, while a separate initial grant requires a linked card and has exclusions. VM compute is billed per second while running, but disks, snapshots, images, public IPs, licenses and outbound traffic are separate and may continue after a VM stops or is deleted.

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

Compute Cloud

Runs virtual machines, preemptible capacity and fault-tolerant instance groups.

Persistent storage

Uses zonally replicated disks plus separately billed snapshots and images.

Organization and IAM

Structures organizations, clouds and folders with role-based service access.

Billing controls

Tracks detailed usage, grants, budgets, notifications and commitment discounts.

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

• Workloads targeting Russia or supported surrounding markets after legal and residency review
• Teams needing Yandex-native data, analytics or ML services alongside infrastructure
• Businesses approved for trial or program credits with a plan for post-credit operating cost

Skip Yandex Cloud if

• The payer country or required payment method is unsupported
• The project assumes every new account receives the advertised maximum trial credit
• Disks, snapshots, IPs, marketplace licenses, egress and recovery are absent from the cost model

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.

Yandex Cloud: pros & cons

• Broad managed catalog: Compute, object storage, databases, Kubernetes, serverless, analytics and ML share one platform.
• Granular compute billing: VM CPU, RAM and eligible operating-system use accrue per second only while running.
• Cost controls: Billing dashboards, budgets, alert thresholds, grants and commitment discounts support governance.
• API-managed resources: Compute exposes HTTP APIs, IAM roles, quotas, instance groups, images and snapshots.
• Access is country-dependent: Official signup documentation notes unsupported countries and different payer/contract flows.
• Trial is not universal: Business customers and individuals receive different trial or consumption treatment, with grant exclusions.
• Stopped VM is not zero cost: Disks bill from creation to deletion; images, snapshots, IPs, licenses and traffic are separate.
• Regional/legal fit is specific: Currency, tax, data location, compliance and service availability depend on contracting entity and region.