# Deployment Templates

A deployment template defines which applications to deploy for a [Fleet](https://docs.i3d.net/game-hosting/elements/deploymentenvironment/fleet).

This section of the documentation elaborates on deployment template elements for game server builds, utilities and dependencency installers.

## GameDeploymentTemplate

The GameDeploymentTemplate indicates which \[game server] [ApplicationBuild](https://docs.i3d.net/game-hosting/elements/application/applicationbuild)s you want to have deployed within a [Fleet](https://docs.i3d.net/game-hosting/elements/deploymentenvironment/fleet).

[Continue reading ...](https://docs.i3d.net/game-hosting/elements/deploymentenvironment/index/gamedeploymenttemplate)

## UtilityDeploymentTemplate

The UtilityDeploymentTemplate indicates which utility / utilities you want to deploy onto each host (bare metal or VM). A utility, also known as a sidecar, is always deployed once per host. You can indicate whether a utility should be deployed only on bare metal servers or virtual machines, or both.

[Continue reading ...](https://docs.i3d.net/game-hosting/elements/deploymentenvironment/index/utilitydeploymenttemplate)

## DependencyDeploymentTemplate

The DependencyDeploymentTemplate enables you to provide scripts that install dependencies onto a Host that are required by your Application(s) to run properly. Besides an installer script, you must also define an un-installer script to remove the dependencies and to allow clean up of a Host after removing all applications running on it.

[Continue reading ...](https://docs.i3d.net/game-hosting/elements/deploymentenvironment/index/dependencydeploymenttemplate)