CheckoutBack to list
Checkout.com is an API-based platform providing companies with a cross-border payment solution for digital commerce. The business offers direct access to domestic acquiring across payment methods and geographies, including all major credit and debit cards, online banking, PayPal, Apple Pay, and other eWallets.
Checkout.com is a highly flexible and customizable payments platform that helps global brands deliver faster, more reliable transactions.
They were using Jenkins for their Terraform infrastructure-as-code deployments but the user experience didn’t meet their needs. And so they turned to Spacelift.
Marius Galbinasu, Senior Engineering Manager at Checkout.com, explains why his team switched and the impact it’s had on the company.
We found that Jenkins is a good generic tool, but it doesn’t offer anything special when it comes to deploying infrastructure. So we looked for an alternative. We didn’t get enough information and control over what was being run, while deployment pipelines were inconsistent.
We chose Spacelift as a Terraform-specific tool that would streamline our work and allow us to be more consistent with our output without having to reorganize our code in GitHub or hand over control of our state files, as rival tools would require.
The Spacelift experience
One of the best things about the experience of moving to Spacelift has been the level of support and the knowledge of the team there.
When we have a question, we always get an almost instant answer or at least their attention. And it’s great to be able to request features and see them work on them, or plan to deliver them at a later date. Some of the features Spacelift offers were essentially built for us, because we specifically requested them.
Using Spacelift has improved our overall developer experience around deploying infrastructure. Features like proposed runs on code changes have improved our GitHub workflows. And we now get instant feedback for what code changes actually mean in reality through the ability to add comments.
We also now have an estimate of our costs through the Infracost integration Spacelift provides. And we have control over what types of resources can be deployed in our AWS environment, enforced through Spacelift.
We develop faster with Spacelift. We’re now able to get feedback on what our code will do much more quickly. And we can apply those changes faster as well by replacing manual steps with triggering a pipeline and relying on GitHub commits.
That increased efficiency has an impact across the company. We’re able to effectively advertise and share our Terraform code across multiple teams and organizations.
We have around 30 Spacelift organizations, and dozens of Terraform modules that we share across the company. Spacelift makes it easy to share that reusable code, generate documentation for it, and instructions as well on how to use it.
Code reviews are more efficient, too. Our entire code review process now happens in GitHub, because Spacelift’s checks show up there, letting us see what the cost will be and making sure that our policies are being applied consistently. It allows us to use GitHub as the only place we really need to go into to control our infrastructure-as-code. Everything is far more streamlined and consistent for the whole organization.
In all, life is a lot easier with Spacelift on our side.