Product FAQs


Can Webscale host my application for me?

Yes, all of Webscale’s solutions come with the ability, either by default or as an add-on option, to host your application in our cloud account. Hosting your application lets you truly focus on managing the functional aspects of your application, rather than managing the infrastructure. Learn more about our product options here.  

How do Webscale solutions differ from traditional appliances like ADC or WAF?

Historically, ADC or WAF functionality was available from many industry vendors as a hardware appliance. This then evolved into a software solution that can be deployed on virtual machines. The common theme around all of this is the complexity and management of the infrastructure is left to you. Webscale is delivered as a true-SaaS, where you do not have to worry about procuring, deploying or maintaining the ADC or WAF. It is cloud-hosted and managed by Webscale through its multi-tenant architecture, delivering all the functionality needed including auto-updates, so new functionality is immediately available without any intervention on your part.

How is Webscale different from a CDN?

Webscale can do most things a CDN can and more, not the other way around.

CDNs (content delivery networks) are a distributed network of servers deployed closer to end users accessing the application over the Internet. Webscale, however, is primarily deployed closer to the application infrastructure (backend or origin), typically in the same cloud availability region or zone. Webscale and CDNs both provide security and performance benefits to web applications, either closer to the origin or to the end user.  

One of the main differences of Webscale from a CDN is the comprehensive insight and control Webscale has over the application infrastructure. This enables Webscale to do things a CDN typically does not control or have visibility over- like auto-scale application infrastructure based on capacity needs,  self-heal the application when errors bring the application down, analyze security violations on the application backend, and more.

How can Webscale protect my application around developer errors?

It is not uncommon for developer errors to bring down applications. Webscale can automatically take scheduled (time-based or event-based) backups of the entire application and validate each backup to make sure they can be restored to a fully functional application.  When an application goes down due to erroneous code changes, the safest recovery option is to restore from a previously validated backup. Webscale enables the administrator to choose from a list of validated backups, and restore the application successfully, preventing further downtime.     

How can Webscale protect my application against cloud outages?

While not very common, wide-scale cloud outages may occur. Such disasters can have significant impact to the revenue and brand reputation of the business. Webscale has disaster recovery solutions (Cloud Mirror and Cloud Rescue) that can replicate a running application in a different cloud region, or an entirely different cloud provider. This ensures there is a redundant, near real-time snapshot of the application always available during a cloud outage. During the disaster, Webscale can then failover the application to the replica location and have the application running back up with its last known available state.      


What is Webscale Shield Mode ?

Often, we see applications facing DDoS (distributed denial of service) attacks from bots, slowing the application down from responding to other valid requests or bringing it down altogether. To get ahead of this problem, the admin can enable Webscale Shield with a single click. Webscale Shield keeps all bots out of the application instantly, and validates users to only allow humans through. This buys the administrators time to identify the pattern causing the attack, permanently block them before disabling the Webscale Shield.

What is App Shield ?

The Webscale data plane includes a WAF (web application firewall) that fronts the application. Through various control mechanisms (blacklisting, Web Controls, DDoS Shield Mode, WAF rules) Webscale can block bad traffic before it gets to the application. But, if the application server IP addresses are discovered, an attacker can bypass the Webscale WAF and directly access and attack the application servers. To solve this security problem, the Webscale App Shield, when enabled, only allows web requests at the application servers coming from the Webscale data plane IPs and rejects all other requests. This ensures the only valid traffic getting through to the application comes via the Webscale data plane, and there is one place to apply all security controls to that traffic.  

What are Web Controls, and how do I use them ?

Web Controls are easy-to use, customizable policies enforced on web requests accessing the application. They are used to control different aspects of web traffic - to tune and enhance performance, uptime and security of the web application. The administrator can configure and enable multiple web controls, and determine the order in which they are executed through the Webscale portal.

Some of the many use cases that are enabled through web controls:

  • Block (or allow) user traffic from a particular geography
  • Enable blue-green testing of different web application designs
  • Enable performance optimizations based on specific request identifiers such as URLs
  • Route application admin page requests to a separate application backend
  • Optimize 3rd party content to speed up page load  

An example of how to configure Web Controls is shown in the user guide here.

What are Cloud Controls, and how do I use them?

Cloud Controls enable you to execute code (javascript) automatically triggered by system or external events, or scheduled by time. Here is a technical deep dive into Cloud Controls. Also, learn more about how to write a Cloud Control here.

What is Dynamic Site Cache ?

Web pages are increasingly personalized and dynamic in nature, and un-cacheable since they change dynamically based on the user who is logged in. For users who are not logged in, enabling Dynamic Site Cache allows caching of web pages outside the application infrastructure, from within the Webscale data plane. This significantly offloads the application to focus on checkouts and cart operations, and leaves generic browsing and bot activity to be handled outside the infrastructure, leading to faster page loads performance and increased cost efficiency of hosting. Dynamic Site Cache is enabled on a per-application basis. Contact us to learn more about how to enable Dynamic Site Cache.

What is Bot IP shield ? How do I get it ?

Webscale Bot IP shield addresses the challenge of identifying known bad attackers through incoming IP addresses. Bot IP shield disables, in real-time, inbound communications from IPs known to be malicious, keeping customer infrastructure secure and efficient. Webscale Bot IP shield is powered by Webroot’s BrightCloud® IP Reputation Service.

Bot IP Shield is available as part of Cloud Bot Manager or Enterprise Cloud Secure. Contact us to learn more about how to enable Bot IP shield in your account.

What is Cloud Bot Manager ? How is if offered ?

Cloud Bot Manager is Webscale's comprehensive multi-cloud Bot management solution to combat the rapidly growing threat of malicious bots, while improving performance and delivering higher RoI.

It includes

Instant Attack Detection

Real-Time Bot Mitigation

Bot IP Directory

Real-Time Monitoring, Reporting
and Management

Intelligent Caching

Cloud Bot Manager can be easily enabled with just DNS changes to protect any application on any hosted environment. It is also available as part of Enterprise Cloud Secure, Webscale's enterprise security suite. Learn more here.


What is the pricing model for Webscale solutions ?

Webscale plans are priced like any SaaS, with monthly recurring fees and sometimes, a one-time setup fee. The plan that you choose choose depends on various factors relating to your needs - the need for Webscale hosting, number of web applications that need to be managed by Webscale, the average number of visitors to each web application, etc.