Skip to main content

Bringing the Power of the Crowd to SaaS

Patrick Carey

Every day, compelling new applications, built to support the needs of enterprises, are turning up in the cloud. As the significant benefits of these SaaS and hybrid cloud services become more evident, it's no surprise that cloud is playing an increasing role in enterprise application portfolios.

Over the last couple of years a new class of mission-critical SaaS applications providing core communication services (e.g., email, VoIP, online meetings, document storage/collaboration, etc.) have come to the fore, enabling organizations of any size to cost-effectively provide highly sophisticated services to their users.

However, while the reward is great, because these apps are mission-critical and deployed to your entire workforce, so is the risk. If your cloud-based CRM system is unavailable, the sales team is certainly impacted, but if email, IP and/or VoIP communications are unavailable, the entire organization takes a productivity hit.

To address this risk, IT must take a fresh look at how they monitor and manage these services. Moving your mission-critical apps to the cloud doesn't absolve IT of responsibility for the quality of service. If users can't access email, they are not going to call Microsoft or Google or Amazon. They are going to call the IT help desk and the IT team will be expected to fix the issue regardless of where it exists.

Therein lies the problem. With SaaS applications, IT does not have direct access to most of the server and network infrastructure running the services. They may have access to a service provider status dashboard, but those often do not provide anything close to real time information. Nor do they provide any information on the health and availability of the various networks (yours, the ISP's, the regional backbone, etc.) connecting the users to the service.

To effectively monitor and manage mission-critical SaaS applications, IT needs to be able to identify and isolate problems that may exist outside the infrastructure they own and operate. But how?

Bring on the Crowd

SaaS applications are by definition shared by a global community of customers. So it stands to reason that monitoring of these services could and should be done in a shared manner as well.

There are certainly examples of the crowd monitoring the cloud already happening in informal ways through Twitter. It's not uncommon for users to check Twitter when they are having problems with a cloud service. Twitter in effect becomes an impromptu global network of monitors, watching the service from hundreds of thousands of access points.

The problem with Twitter though is that it is primarily anecdotal and qualitative information and generally does not give organizations using mission-critical SaaS applications the fidelity needed to fix issues impacting users.

Despite Twitter's limitations as an IT tool, there is a lot to be said for the "power of the crowd" that is so fundamental to Twitter. What if IT could take that same model and use it to proactively monitor SaaS applications?

First, you need to go from ad hoc qualitative observations (e.g. "My email seems slow today") to consistent collection of performance data from a broad user community. This requires some type of active monitoring at the locations where users access their SaaS applications. Monitoring from the organization's points of access is critical. A solution that monitors from arbitrary points on the Internet will still be blind to local or ISP issues affecting a specific office.

Monitoring from a single location gives you real-time data for that location, which is certainly an improvement over the service provider dashboards, but that isn't enough. From a single point of access, an outage will look much the same regardless of whether it's local, in the network, or as the provider. This is where the crowd model comes in. By aggregating data from multiple locations, you can start to see trends and spot anomalies between them.

But why stop there? Why not aggregate data across all users of the SaaS service? The greater the number of monitoring points, the more accurately you can detect and isolate specific problem spots. Think of it like GPS for the cloud, pinpointing the issues that degrade service levels and user experience.

Armed with this level of visibility, IT could do a better job of optimizing their environment and minimizing the time to resolution of any service impacting issues. In doing so they regain the ability to ensure their users get consistent service and a high quality user experience.

A Call to Action

Obviously, no single consumer of a SaaS application can expect to gather all this data themselves. Cobbling together measurements from multiple office locations would be challenging enough and collecting data from other organizations would be downright impractical. This is where the industry needs to innovate and bring new SaaS solutions to market that enable IT organizations to realize the benefits of the cloud without losing the visibility and control they've had with their traditional systems.

The power of the crowd is a pervasive and growing force enabled by cloud-based technologies. Virtual crowds come together every day to do everything from building software to funding start-ups, from collecting funny cat pictures to overturning oppressive governments. Maybe it's time IT was able to leverage the power of the crowd to help manage the ever more complex array of cloud applications and services they depend on.

Patrick Carey is VP Product Management & Marketing at Exoprise.

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

Bringing the Power of the Crowd to SaaS

Patrick Carey

Every day, compelling new applications, built to support the needs of enterprises, are turning up in the cloud. As the significant benefits of these SaaS and hybrid cloud services become more evident, it's no surprise that cloud is playing an increasing role in enterprise application portfolios.

Over the last couple of years a new class of mission-critical SaaS applications providing core communication services (e.g., email, VoIP, online meetings, document storage/collaboration, etc.) have come to the fore, enabling organizations of any size to cost-effectively provide highly sophisticated services to their users.

However, while the reward is great, because these apps are mission-critical and deployed to your entire workforce, so is the risk. If your cloud-based CRM system is unavailable, the sales team is certainly impacted, but if email, IP and/or VoIP communications are unavailable, the entire organization takes a productivity hit.

To address this risk, IT must take a fresh look at how they monitor and manage these services. Moving your mission-critical apps to the cloud doesn't absolve IT of responsibility for the quality of service. If users can't access email, they are not going to call Microsoft or Google or Amazon. They are going to call the IT help desk and the IT team will be expected to fix the issue regardless of where it exists.

Therein lies the problem. With SaaS applications, IT does not have direct access to most of the server and network infrastructure running the services. They may have access to a service provider status dashboard, but those often do not provide anything close to real time information. Nor do they provide any information on the health and availability of the various networks (yours, the ISP's, the regional backbone, etc.) connecting the users to the service.

To effectively monitor and manage mission-critical SaaS applications, IT needs to be able to identify and isolate problems that may exist outside the infrastructure they own and operate. But how?

Bring on the Crowd

SaaS applications are by definition shared by a global community of customers. So it stands to reason that monitoring of these services could and should be done in a shared manner as well.

There are certainly examples of the crowd monitoring the cloud already happening in informal ways through Twitter. It's not uncommon for users to check Twitter when they are having problems with a cloud service. Twitter in effect becomes an impromptu global network of monitors, watching the service from hundreds of thousands of access points.

The problem with Twitter though is that it is primarily anecdotal and qualitative information and generally does not give organizations using mission-critical SaaS applications the fidelity needed to fix issues impacting users.

Despite Twitter's limitations as an IT tool, there is a lot to be said for the "power of the crowd" that is so fundamental to Twitter. What if IT could take that same model and use it to proactively monitor SaaS applications?

First, you need to go from ad hoc qualitative observations (e.g. "My email seems slow today") to consistent collection of performance data from a broad user community. This requires some type of active monitoring at the locations where users access their SaaS applications. Monitoring from the organization's points of access is critical. A solution that monitors from arbitrary points on the Internet will still be blind to local or ISP issues affecting a specific office.

Monitoring from a single location gives you real-time data for that location, which is certainly an improvement over the service provider dashboards, but that isn't enough. From a single point of access, an outage will look much the same regardless of whether it's local, in the network, or as the provider. This is where the crowd model comes in. By aggregating data from multiple locations, you can start to see trends and spot anomalies between them.

But why stop there? Why not aggregate data across all users of the SaaS service? The greater the number of monitoring points, the more accurately you can detect and isolate specific problem spots. Think of it like GPS for the cloud, pinpointing the issues that degrade service levels and user experience.

Armed with this level of visibility, IT could do a better job of optimizing their environment and minimizing the time to resolution of any service impacting issues. In doing so they regain the ability to ensure their users get consistent service and a high quality user experience.

A Call to Action

Obviously, no single consumer of a SaaS application can expect to gather all this data themselves. Cobbling together measurements from multiple office locations would be challenging enough and collecting data from other organizations would be downright impractical. This is where the industry needs to innovate and bring new SaaS solutions to market that enable IT organizations to realize the benefits of the cloud without losing the visibility and control they've had with their traditional systems.

The power of the crowd is a pervasive and growing force enabled by cloud-based technologies. Virtual crowds come together every day to do everything from building software to funding start-ups, from collecting funny cat pictures to overturning oppressive governments. Maybe it's time IT was able to leverage the power of the crowd to help manage the ever more complex array of cloud applications and services they depend on.

Patrick Carey is VP Product Management & Marketing at Exoprise.

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...