The use case: how Tyler Technologies deploys Harness
Tyler Technologies replaced a half dozen homegrown and vendor-sourced deployment tools with Harness Continuous Delivery to deploy its services, including as part of its Kubernetes migration.
More reported results
Figures published in Harness’s case study. They are not independently measured by usedby.
In a few months, they onboarded 230 unique services.
In addition to a seamless migration, Harness helped Tyler Tech achieve a best in class change failure rate of 10%.
If an environment goes down, it only takes Tyler Tech 25 minutes to do a full re-deploy.
Tyler Tech completed its first deployment with Harness in 6 hours.
In the customer’s words
We were facing the prospect of re-writing our deployments from scratch, stringing together a bunch of scripts and CLI stuff, or choosing Harness which was clearly superior to our other options.Cloud AutoStopping opened up new possibilities for cloud cost managementOther AI tools used by Tyler Technologies
Other public relationships recorded on usedby.
Explore Tyler Technologies’s AI stackOther companies using Harness
Customers across industries, with public evidence.
AI Data Management CompanyConfirmed
AncestryConfirmed
Burst SMSConfirmed
CitiConfirmed
DeluxeConfirmed
DigiCertConfirmedGo straight to the source
Based on Harness’s published case study. We check the public evidence; the results are reported by the vendor.
harness.io- Source published
- Aug 28, 2026
- Last checked
- Nov 16, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: $1.2 millionChecked
Printed word for word on the page, near the name of Tyler Technologies.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Tyler Technologies.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Tyler Technologies uses HarnessChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Their legacy applications were deployed using a half dozen homegrown and vendor sourced deployment tools. None of these deployment tools were capable of deploying to Kubernetes and each required 1-2 full-time software engineers to maintain.



