Our DevOps and our development team used Catchpoint exclusively for synthetic testing of API and URL endpoints. Our DevOps team is like a composite team for the solution users. Their job was to operate the tool and build the test, and they were the primary folks using it daily.
The developers used Catchpoint for pre-production testing to ensure that the tests ran and gave them the needed data. They made improvements to the systems that were being monitored. We had around 100 users on the whole platform. The third group was my team, the platform owners. We were in there running daily reports.
When we started, it was pretty light because we were trying to evolve our thinking, and then it grew. The contract was renegotiated when I was leaving, and we were increasing the test count even higher than we had, indicating a higher level of interest in what we could get out of it.
Catchpoint is a natively built cloud. There are also ways to deploy an agent internally for tests that sit behind firewalls and internal systems, but the platform is definitely SaaS.
Integration is essential. We can tell what's going on in our infrastructure and all the other events in our environments simultaneously. Our hand-built, in-house integration solution had a lot of overhead. at the same time, Catchpoint was essentially ready out of the box. We only need to configure a connector. That was a huge win.
Also, our outside-in tests from our previous provider would trigger an alert. Someone would look at that test failure and say, "Well, the site's up. What's wrong here?" We couldn't eliminate ourselves as the culprit. We couldn't tell if it was being routed through an entirely different AS across the internet because someone between us and the test site has a provider issue.
Catchpoint helped us establish that something is in a provider network, so we could tell our customers to check their internet provider because the traffic is not getting to us. You need to be gentle when you tell them that, but the fact that we could do it was crucial.