> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components.md).

# Components

<figure><img src="https://3117893838-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FepYt9QlYazTOKSlt9tWX%2Fuploads%2FdW7YKeWYsAQ7IGz8x0Az%2FScreenshot%202025-10-30%20at%2014.59.44.png?alt=media&amp;token=b1f53d78-0ba3-4f7a-9ec3-dd2ce144cc2c" alt=""><figcaption><p>High-Level view of the Application Components</p></figcaption></figure>

## Scanner

The scanner is an **on-demand executable binary** that is deployed into an end-client (host) and allows the following:

* Collecting host data like ip address, processor, memory, storage, network interfaces, etc.
* Collecting processes data, network connections and dependencies
* Collecting installed software (applications, packages, libraries)
* Extracting configuration data from running applications
* Extracting byte code from target running applications &#x20;

It is **deployed** and **sent execution commands** via an open connection to the endpoint, using one of the following protocols

* **SSH (Secure Shell)** - for connecting to Unix/Linux-based hosts&#x20;
* **WINRM (Windows Remote Management)** - for connecting to Windows-based hosts
* **AWS-SSM (Amazon Web Services System Manager)** - for connecting to AWS resources

More detailed information is available in [Scanner](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components/scanner.md)

***

## Orchestrator

The **Orchestrator** component is a command-line tool (that can run as a service) that **coordinates** the behaviour of the scanner on-demand agents, defining scanning targets (IP range, systems) and containing credentials for those target systems and controlling how data is collected.

It's a native application that should be **installed in your local machine** and will connect and coordinate with the on-demand scanners being deployed into the endpoints for information gathering. &#x20;

More detailed information is available in [Orchestrator](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components/orchestrator.md)

***

## Frontend UI

The Frontend is a web interface that runs in your browser allowing you to interface with the application and analyse all the data and KPIs collected by the solution.&#x20;

More detailed information is available in [Frontend UI](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components/frontend-ui.md)

***

## Backend Services

Several components compose our backend services, deployed on your cloud environment.&#x20;

More detailed information is available in [Backend Services](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components/backend-services.md)

***

## Target Cloud Service

Once an application has been refactored you can deploy it on a target cloud service. This could be the following:

* AWS Fargate
* Azure&#x20;
* GCP&#x20;
* Your private container solution

More detailed information is available in [Target Deployment Environment](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components/target-deployment-environment.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appfactor.io/52eJroWboQfTwsFl14gL/quickstart-guide/overview/components.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
