david caussinus

How a CTO of an IT services company streamlined their cloud infrastructure with Clever Cloud

When David Caussinus took the helm of the technical department of a French IT services company with over 800 employees, he encountered a common reality in the sector: an under-resourced, poorly structured internal IT function, in need of a genuine digital transformation, often sidelined in favour of client-facing projects.

Like many IT Services Companies, this firm specialised in placing tech experts, and internal IT had historically not been a priority. However, as the company grew and its operations became more complex, the need for transformation became unavoidable.

David embarked on a comprehensive modernisation, with a clear goal: streamline infrastructure, ensure business applications’ reliability, and optimise operating costs.

From overcomplication to rationalisation

Upon his arrival, David Caussinus made a stark assessment: the company was running a SaaS ERP, an Office 365 suite, and a digital factory hosting internal and client applications on AWS via Kubernetes (EKS). A complex and costly architecture for only 5–6 applications, while the internal IT team was very small and had limited expertise in managing such infrastructure.

I had just one DevOps engineer, present one day a week. The rest of the time, he had to bill hours on client projects. And yet, we were managing a cloud production environment with several critical applications.

Faced with these constraints, David initiated a paradigm shift. In January 2024, he decided to fully move away from AWS and Kubernetes, migrating everything to Clever Cloud.

Why Clever Cloud?

The ESN needed a simpler, more pragmatic infrastructure, aligned with available skills and business priorities.

The complexity of your architecture should match your teams’ capabilities. There’s no point in building an over-engineered system if no one can operate it.

Clever Cloud’s Platform as a Service solution allows teams to focus on applications, without worrying about operational maintenance.

I shifted the operational burden to Clever Cloud. Their job is operations. It used to be mine, but I no longer had the means to handle it in-house.

Testimonial from David Caussinus as CTO
capture decran 2025 09 22 a 17 40 30

A gradual, usage-oriented migration

Migration began with internal business applications essential to company operations: ERP data extraction, reporting, automations, and more.

These roughly ten applications included tools for extracting data from the SaaS ERP, processing data to feed Power BI reports, and various business automations.

Production runs every day. Not once a week. We needed stability, visibility, and responsiveness.

In total, around ten applications were migrated. The digital factory developers regained a stable, responsive environment, tailored to their needs.

Lasting lessons

The experience reinforced David Caussinus’ strong belief: not all technologies suit every context, and a good technical choice is first and foremost one adapted to the situation.

Clever Cloud is not a compromise solution. It’s a solution that meets a need. And that need is to delegate infrastructure intelligently, to focus on what really matters: the business.

When IT is not your core business, you need to delegate. But you must delegate wisely. Not by blindly outsourcing, but by choosing partners who can handle the run for you, while you retain control over your operations.

UP Program: Clever Cloud announces its fifth startup selection

With this new batch, Clever Cloud welcomes four startups to the UP Program: Sentibee, Pictaderm, Legaia and Cockpit Agriculture.
Company

Sōzu 2.0 — turning a reverse proxy into a programmable edge

Sōzu is the reverse proxy that sits in front of every application running on Clever Cloud. After eighteen months of work — first the HTTP/2 multiplexer, built on our existing kawa pivot, then almost every other layer of the proxy, and finally a long run in production on the cleverapps.io load balancers — Sōzu 2.0 is out.
Engineering

K3s vs K8s: What Are the Differences and Which One Should You Choose in 2026?

Kubernetes has become the standard for container orchestration. But depending on your infrastructure constraints (limited resources, edge computing, IoT, or large-scale enterprise clusters), the distribution you choose can radically change the operational experience. K3s and K8s (upstream Kubernetes) address different needs, even though both share the same CNCF-certified foundation.
Engineering Features