The use case: how Toss deploys CircleCI
Toss's frontend developers replaced Jenkins with CircleCI to run CI/CD for a large repository of independently deployed services, using parallelism, test splitting and scaling concurrency to test and deploy code quickly and frequently.
More reported results
Figures published in CircleCI’s case study. They are not independently measured by usedby.
“Toss deploys to production 70 times per day.”
In keeping with the development team’s goal of creating happy users of the Toss app, developers also want to deploy frequently – as Park notes, as many as 40 to 50 times a day.
In Jenkins, complex tests and deployments could take as long as two or three hours, Park adds.
In the customer’s words
With CircleCI our testing and deployments are running at about two minutes.Other companies using CircleCI
Customers across industries, with public evidence.
See all CircleCI customers
Go straight to the source
Based on CircleCI’s published case study. We check the public evidence; the results are reported by the vendor.
circleci.com- Source published
- Nov 13, 2026
- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: two minutesChecked
Printed word for word on the page, near the name of Toss.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Toss.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Toss uses CircleCIChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
In Jenkins, complex tests and deployments could take as long as two or three hours, Park adds. But with CircleCI’s scaling concurrency, those jobs take a fraction of the time.