Komodor | How Splitit Reduced MTTR and Innovates Faster Using Komodor Komodor | How Splitit Reduced MTTR and Innovates Faster Using Komodor

How Splitit Reduced MTTR and Innovates Faster Using Komodor

Customer Logo
Company size:

51 - 200 employees

Industry:

Financial services

Komodor Installation:

5 clusters, 80 nodes

About Splitit

Splitit is a global payments provider, offering next-generation Buy Now, Pay Later solutions in over 52 countries around the world. Thousands of brands such as Google, AliExpress, TikTok, and Samsung use Splitit’s white-label service to give customers the option of card-linked installment payments.

Constant pressure to maintain uptime and availability

As a payments company, Splitit must always be on. There’s no room for downtime or failures, so the engineering team has to constantly maintain the company’s systems for maximum robustness and availability.

But Splitit CTO Ran Landau does more than maintain the status quo — his priority is innovation. In addition to making sure systems operate and process secure end-to-end transactions, Landau oversees the development team, which consistently pushes updates and new capabilities to better serve clients.

Kubernetes streamlines these daily deployments across a dynamic environment.

Increasing reliance on DevOps prevented scalability

As Splitit scaled their continuous deployment pipeline, Day Two Operations became increasingly complex, with diminishing visibility and control over their Kubernetes environment.

Initially observing its environment using the basic Kubernetes dashboard, Splitit quickly ran into permission, connectivity, and scalability issues. When problems arose, the dashboard was insufficient in helping engineers observe, locate, solve, and validate across all environments. Identifying the root cause of production issues, accessing pods, or changing the Kubernetes environments required constant DevOps involvement. The dependence on the DevOps team consumed valuable production time.

When Landau joined Splitit as CTO, one of his goals was to adopt solutions to support high scalability. Finding a secure solution that would allow DevOps engineers to track, maintain, and debug Kubernetes clusters as necessary was top priority.

A permissions-based solution delivers complete visibility to engineers

Splitit wanted full control over their Kubernetes cluster, and Komodor was one of the few solutions in market that provided full visibility and fine-grained access control necessary to manage permissions effectively.

From the start, Komodor’s Kubernetes Management Platform offered Splitit engineers more visibility and control. The team’s first step was to implement Komodor’s automated remediation playbooks for debugging issues, which dramatically accelerated incident resolution workflows. The team gained granular observability, RBAC-based access controls, and comprehensive visibility and command of their development and production clusters across their multi-environment architecture. It removed friction and simplified an otherwise complex management process. The platform also gave the CTO visibility into Splitit’s entire environment.

Landau grants individual engineers only as much access and control as their role requires. With a proper permission structure and the correct level of access, engineers gained greater visibility into individual pods than they would have with an application log. Unlike with many other platforms, engineers can fix issues within the platform.

Putting these tools in developers’ hands meant they could self-serve more often, without additional assistance from the DevOps team. The result? Reduced MTTR, which is a big win at a fast-moving company where application availability directly impacts revenue. Automated alerts are another time saver. Komodor transforms traditional MELT telemetry into actionable intelligence. It delivers contextual alerts with recommended remediations directly to team Slack channels, enabling immediate action 24/7. Meanwhile, the Komodor dashboard’s monitoring tools and AI-enabled suggestions allow the team to investigate, test, and ultimately adapt in the fastest and best way possible.

Komodor has continued to add new capabilities, providing Splitit with opportunities to expand the platform usage from Kubernetes to Airflow and health check monitoring.

Splitit adopted other Kubernetes tools, but Komodor has been the only solution to withstand the test of time. After the first year, the team asked, “Which of these brings us the most value and solves our problems?” The answer, resoundingly, was Komodor.

Peace of mind in a high-powered environment

If a company operates in a high-scale production environment using Kubernetes, engineers require a continuous reliability platform that provides full-stack visibility, contextual insights, and automated guardrails to proactively prevent critical issues. Komodor delivers that for Splitit.

“It solves unnecessary noise so we can focus on providing real value in our operations. The platform brings us peace, quiet, and the knowledge we can access what we need, whenever we need, by whoever needs it.”

Download this Case Study in PDF

Download PDF