Swapping out Travis for something else takes a few minutes. If you have a lot of repositories and very complicated scripts, it might take a day or so. But ult

Swapping out Travis for something else takes a few minutes. If you have a lot of repositories and very complicated scripts, it might take a day or so. But ultimately, the lock-in for CI solutions is minimal. The effort to migrate is very small. Over the last few years, I've transitioned projects between Jenkins, Travis, AppVeyor, CircleCI, GitLab and others. In most cases, the logic had mostly been factored out in to shell scripts and batch files. Telling one CI system to set up the build/test environment and run that script is pretty much the same as any other. And this might be the reason why this layoff has happened. What future did Travis have as a business? What was its growth potential? How many paying customers did it have? When everything you offer is done better, often for free, by your competitors and customers can easily set up their own self-hosted replacement if they choose, I'm a bit skeptical that the business was worth that much in the first place.