GUIDE Deployment Architecture

The diagram below shows the deployment architecture for GUIDE.

Workspot DaaS (Step 3), Workspot Watch, Workspot Trends, and Workspot Events (Step 6) are existing SaaS services.

Let’s walk through the steps in a GUIDE deployment:

(1) A builder, typically a business technologist, builds a GUI Agent using the GUIDE IDE. The GUI Agent is stored in the GUIDE Service.

(2) Any enterprise user can then invoke the GUI Agent from their desktop, chatbot, etc.

(3) In order to run the GUI Agent, GUIDE Service requests for a virtual desktop for that user.

(4) Once Workspot DaaS returns a virtual desktop - persistent or non-persistent - GUIDE invokes the GUI Agent on the virtual desktop running in AWS, Google Cloud Platform, Azure or Akamai Cloud.

(5) The GUIDE Harness manages the execution of the GUI Agent by interacting with the chosen model - GPT, Opus, Sonnet, Gemini - running on the chosen provider - Amazon Bedrock, Google Enterprise Platform, etc.

(6) Finally, performance, security events, and token consumption data is passed to Workspot Watch, Workspot Trends and Workspot Events. The data can be analyzed either in real-time or historically.