The use case: how Tessian deploys CircleCI
Tessian migrated from self-managed Concourse to CircleCI's SaaS CI/CD with Premium Support to build and deploy its Python monorepo, including Windows-based Outlook add-ins, without running its own CI infrastructure.
More reported results
Figures published in CircleCI’s case study. They are not independently measured by usedby.
In 95% of builds, the build time went from 67 minutes to 42 minutes – 37% faster than with Concourse.
In the customer’s words
Support is critical to our platform — we're deploying many times a day, and if we can't deploy, that's going to stop us being able to do our jobs effectively.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: 37%Checked
Printed word for word on the page, near the name of Tessian.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Tessian.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Tessian uses CircleCIChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Once engineers rolled out CircleCI, they tracked a significant improvement in build times for Tessian’s main Python monorepo. In 95% of builds, the build time went from 67 minutes to 42 minutes – 37% faster than with Concourse.