I use it for developing scripts - UI scripts and API tests. 

I worked with an iGaming company called Betsson, which is a very big operator. We used Apica to monitor our brands and our white labels. We used different product features, simulating user experience such as logging in to the website, playing slot-games, registering an account, etc. We used various aspects of the product.

Synthetic: To replace and improve on the current solution and integrate it with the multiple platforms that are already available in the organization.

LoadTest: To replace the current solution with a newer and better platform which would not only expand on the current capabilities but also reduces the infrastructure maintenance.

We have a mix of hybrid models. We have the orchestration platform as SaaS in Apica's cloud. However, the agents that we run checks (or load test from) are located on-prem. 

There are quite a few things that we use Synthetic for:

• We use it for error checking and geo-protection checking because we are very regulated since we are in gaming. Basically, if it doesn't see X text on a page, the geo-protection is not firing properly for blocked areas. This checks all our maximized databases. 
• We use it for timings in making sure the web page is optimal so we can tell if someone accidentally seeks a large image up through the CMS site. 
• For the load test side, it is pretty much obvious what it does. It is load testing outside through journeys what we have through Synthetic. It checks the API back to the login services and so forth. 

That's a great overview of what we use it for. We use probably around 75 checks on Synthetic across our three verticals that we do per casino. 

Our primary use case is for monitoring. We've got a number of auto finance applications and hosted applications that my teams are supporting. Apica offers outside-in visibility of what a user would experience if they were actually logging into the platform. We noticed that we were missing that outside component. We had a lot of internal monitoring in place for making sure that the user experience was good, but when it came to being able to support our users and report back on issues our users might be experiencing, and work to remediate or identify and resolve issues that our users may be experiencing from the open internet connection that they've got into our hosted environment, it was just not sufficient. So Apica is what we're using that for today to actually give us an outside-in view of what the end-user would actually experience from the beginning to the end and from their overall use case experience for our hosted applications. 

We also use it to monitor the internal service platforms that we use to support our infrastructure, support our environments, and support our internal clients. We use it for monitoring port status and service statuses associated with network-based applications like FTP file transfer platforms, MQ platforms, shared services, SOA platforms, and a number of other internal platforms that we utilize the shared services across our application stacks to serve the service of our clients.

We monitor various applications provided as dependent services. We also monitor internal applications that are required for different departments. Then, we have a wide variety of applications supporting different departments as well as clients. Whether it be a background transaction, front-end UI, or vendor application, we try to monitor the DNS with Apica

We have been using it both on-prem and off-prem recently. The Apica platform has its own external instance.

We're a banking software company, so we use it for Synthetic logins to test how one of our end users would log into our product for a customer, how long it would take, what loads, and then log them out. Then we test how long it takes to do that entire process.

On the Synthetic side, we only use it SaaS-based. We actually put it through an SSO. We use Okta for an SSO. That's how we're securing our connections there. Security-wise, Apica's got a couple of things in the works that are going to help them out, but they're not there now. In particular, they're coming out with a key chain that allows us to save. You can hash passwords and users, they don't have that right now. Passwords and logins are set in plain text.

Apica is used to perform availability checks of our IT services. We put what we call synthetic checks in place, and these are mainly used to check if a specific application is running correctly, or if it is not available.

I used Apica to perform load testing. We switched a project from London to Africa, and I used Apica to develop performance test scripts, design load tests, execute them, and generate reports.

We have an eCommerce company. so we manage a lot of online stores. Our main usage is to make sure that our store web pages are different types of web pages, so there can be a homepage, search page, or product list page for each online store that we manage worldwide. We leverage a lot of Apica Synthetic probes to make sure that every store is available and responding as we expected worldwide. This is to ensure that there are no outages in specific parts of the world. Also, we collect some performance metrics, like response time, time to first buy, etc.

We are using the web-based service. While we do have some on-premise probes installed, we use the service on cloud the all the way. We installed the probes two or three months ago.

Apica Synthetic is definitely one of our core pillars on the synthetic side. We also use synthetics as a measure of external customer application availability. So, we do a daily report internally, which goes out to the tech leadership team, showing how their applications are performing and how available they are. So, it is an integral part of our monitoring tools, and the synthetics are huge.

These are complex multi-step synthetic checks. The intent is to mirror as closely as possible the points and clicks or API/system-to-system calls that our customers are using. So, if anything is not operating properly, then teams are alerted who can triage and ultimately resolve the issue.

The primary use cases are SaaS, but we do have an on-prem environment for Apica Synthetic as well. That option is very helpful because we do have a number of applications that don't have external endpoints. For those use cases that are only accessible internally, we do leverage the Apica on-prem model. This allows flexibility when monitoring applications that we couldn't with a strictly SaaS deployment.

We have various tools, applications, and websites and the use case for Apica is emulating user actions on those sites and in the tools. We use it for proactive action. Before the user starts getting errors, Apica will alert us because we have it monitoring the same actions we expect the users will be taking. Once Apica detects an error it will notify us so we can take necessary action, before it becomes widespread and users start to report it. Apica is doing an important job in monitoring because our company offers services through those sites and the application.

We're using it on-premises and we're using their agents on their cloud.

I used Apica for monitoring browser synthetic checks, like websites and URLs. And I also used it to monitor API collections – specifically mobile APIs for iOS and Android. It was a comprehensive monitoring tool.