Same workflow, every cloud
Multi-cloud means multi-everything: different CLIs, different credential formats, different state management, different modules. Your team context-switches between AWS, GCP, and Azure tooling all day.
One YAML manifest format, one CLI, one console — whether deploying to AWS, GCP, Azure, or all three. OpenMCF provides provider-specific specs, not lowest-common-denominator abstraction.
planton cli
$ planton apply -f gcp-cloud-sql.yaml
✓ GCP Cloud SQL instance provisioned
$ planton apply -f aws-rds.yaml
✓ AWS RDS instance provisioned
$ planton apply -f azure-sql.yaml
✓ Azure SQL Database provisioned
How Planton unifies multi-cloud
Five capabilities that eliminate cloud-specific context switching.
01
One Manifest Format
KRM YAML manifests with provider-specific specs. Not a generic abstraction that hides capabilities — full access to each cloud's features through typed specifications.
Same apiVersion/kind/metadata/spec structure for every resource
Provider-specific spec fields — GCP, AWS, and Azure each get their native options
Validated at write time, not at apply time
02
Centralized Credentials
One place to manage cloud integrations and credentials across providers. Switch clouds without switching credential workflows or learning new secret management patterns.
AWS IAM roles, GCP service accounts, and Azure service principals in one interface
Environment-scoped defaults — dev uses one account, prod uses another
Secrets encrypted at rest, resolved only at execution time
03
Same Workflow
planton apply works the same whether you're deploying GCP Cloud SQL, AWS RDS, or Azure SQL Database. One command, one review flow, one audit trail.
planton apply / planton destroy — same verbs, every provider
Preview changes before applying, regardless of target cloud
Consistent state management across all providers
04
Provider-Specific Where It Matters
OpenMCF gives you full access to each provider's features through typed specifications — not a limited intersection that forces you into the lowest common denominator.
GCP-specific fields for Cloud Run, GKE, and Cloud SQL
AWS-specific fields for ECS, EKS, and RDS
No capability hiding — if the provider supports it, you can configure it
05
Multi-Cloud Pipelines
Infra Charts can template resources across providers in a single DAG, letting you orchestrate cross-cloud deployments from one definition.
Provision GCP networking and AWS compute in a single chart
Dependency ordering across providers
Reusable templates for common multi-cloud patterns
