What is Crossplane and what are its top alternatives?
Top Alternatives to Crossplane
- Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel. ...
- Nutanix Beam
It delivers savings for public and private clouds. Drive financial accountability with intelligent resource sizing and accurate visibility into cloud metering and chargeback. ...
- CloudBolt
Deploys in minutes. Simple to use. Easy to extend. Centralize workload automation and orchestration, achieve unparalleled hybrid cloud visibility and cost-savings, and deliver self-service IT for your developers. ...
- Komiser
Stay under budget by uncovering hidden costs, monitoring increases in spend, and making impactful changes based on custom recommendations. ...
- Cloud Custodian
It is a tool that unifies the dozens of tools and scripts most organizations use for managing their public cloud accounts into one open source tool. It uses a stateless rules engine for policy definition and enforcement, with metrics, structured outputs and detailed reporting for clouds infrastructure. ...
- Krateo PlatformOps
It is an open source tool, based on CNCF projects such as Kubernetes and Crossplane, that gives users the capability to create any desired resource on basically any infrastructure they'd like. Be it a K8s cluster, microservice, application, pipeline, database or anything else, Krateo has got your back. ...
- Cloudmarker
Can be used as a ready-made tool that audits your Azure or GCP cloud environments as well as a framework that allows you to develop your own cloud monitoring software to audit your clouds. ...
Crossplane alternatives & related posts
Terraform
- Infrastructure as code119
- Declarative syntax73
- Planning44
- Simple28
- Parallelism24
- Cloud agnostic8
- Well-documented8
- Immutable infrastructure6
- It's like coding your infrastructure in simple English6
- Platform agnostic5
- Portability4
- Extendable4
- Automation4
- Automates infrastructure deployments4
- Scales to hundreds of hosts2
- Lightweight2
- 12441241
- Doesn't have full support to GKE1
related Terraform posts





We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).
We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .
Read the blog post to go more in depth.
We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.
To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas
To build #Webapps we decided to use Angular 2 with RxJS
#Devops - GitHub , Travis CI , Terraform , Docker , Serverless