> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/game-hosting/processes.md).

# Processes

This section of the documentation explains processes within the i3D.net ONE Game Hosting service.

A process is a certain aspect of the Platform that you may have to go through and complete before you can use the Platform, such as setting up your [applications](/game-hosting/elements/application.md) and [application builds](/game-hosting/elements/application/applicationbuild.md). Or setting up your [deployment environment](/game-hosting/elements/deploymentenvironment.md) so that our system knows how to deploy your game servers.

Here are all the documented processes where each has a short explanation and a link to the full process documentation.

## Application Management

Application Management is the process of defining and maintaining the applications you want to deploy with the ONE Game Hosting service.

[Continue reading ...](/game-hosting/processes/application-management.md)

## Application Build Provisioning

The purpose of the i3D.net ONE Game Hosting platform is to deploy your applications. Providing your build to the platform therefore is a crucial process.

[Continue reading ...](/game-hosting/processes/application-build-provisioning.md)

## Application Build Management

Application Build Management is the process of creating and maintaining software builds for your Application. An ApplicationBuild defines the software that will be deployed by our system. It can be a game server or a utility (side car).

[Continue reading ...](/game-hosting/processes/application-build-management.md)

## Deployment Configuration

Deployment configuration is the process of setting up how you want your applications to be deployed and where and when.

[Continue reading ...](/game-hosting/processes/deployment-configuration.md)

## Dependency Installation

Dependency Installation is the process of installing software requirements (dependencies) for your applications.

[Continue reading ...](/game-hosting/processes/dependency-installation.md)

## Deployment Process

This chapter describes the process of deploying an ApplicationInstance.

[Continue reading ...](/game-hosting/processes/deployment-process.md)

## Automatic Deployment

Opposite the manual deployment process is the automatic deployment process whereby our platform takes care of deploying game servers and utilities (side cars) for you. This is done according to the Deployment Configuration you have setup for a Fleet.

[Continue reading ...](/game-hosting/processes/automatic-deployment.md)

## Automatic Scaling

This chapter explains the logic behind our automatic scaling process.

[Continue reading ...](/game-hosting/processes/automatic-scaling.md)

## Patching Process

A patching process is the process of updating game servers / utilities to a new version of the software. There are multiple ways in which this can be done.

[Continue reading ...](/game-hosting/processes/index.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.i3d.net/game-hosting/processes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.