# Active Web Proxy

This scenario is largely the same as the API Transformation scenario from an installation perspective. The only difference is that **the requests in this scenario comes from end users rather than server applications** and **the target for the requests are existing web applications or Software** as a Service applications.

<figure><img src="https://2423451286-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F42mDa58RoaDxb6t8mbaI%2Fuploads%2Fgit-blob-3c86d5b3374e93578d3398e35e35df22e6ce1256%2Fimage.png?alt=media" alt=""><figcaption><p>Graph</p></figcaption></figure>

This scenario lends itself to a myriad of use cases:

* Digital transformation, where an existing application *(often beyond the control of the business)* is functionally enhanced, without the explicit need for the existing application being aware of these changes
* Bot management, where the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> detects bots and adds policies for how those bots are able to access the underlying application
* Robotic process automation where requests to the existing application results in data also being entered into secondary systems
* Orchestration of multi existing applications that are joined together to form a new experience
* … and many more

This scenario is especially useful for regaining control of web applications that are otherwise difficult, expensive or impossible to change