akaBot's Architecture Overview

In an organization, depending on the targeted users, different akaBot components can be seen working on different layers. We divide the layers into a front-facing layer and a back-facing layer.

The front-facing layer includes the components that interact directly with the client system and applications and can be operated and controlled by the end-users of the products. That includes:

akaBot Studio used by RPA Developers or Business users to create robots to automate business processes.

After the design and develop stage of the automated robots is done and the robots are ready to be deployed, they can be published to akaBot Agent to run locally or to akaBot Center for large-scale deployment.

akaBot Agent is a personal assistant that can be triggered by the users to execute robots on the interface level of the client systems and applications. 

Robots can be published directly from akaBot Studio to akaBot Agent in case of personal creation and usage, or via Akabot Center for large-scaled projects

As they interact directly with the client system and end-users, akaBot Agent and akaBot Studio are typically installed on local machines

Besides akaBot Studio and akaBot Agent, the front-facing layer also includes the browser extension that is added to the web browser for browser automation activities

On the other hand, the back-facing layer includes the components that are working behind the scene that control and monitor the health of the whole project. This layer consists of akaBot Center as well as the database, authentication domain that allows credential and data control.

akaBot Center is responsible for the deployments of robots to multiple client machines within the organization server at the same time.

Moreover, as akaBot Center lies in the server layer, it will interact with the databases;  identity, and access system for large-scale deployment.

This is also the place where Assets which can be URL, credentials or any input data that are common for websites that will be used by the automation process later.

For better words..

Link for reference