# Deployments

Devin streamlines how FileMaker projects are deployed and managed across various [**Environments**](https://docs.devin.fm/features/deployments/default-environments), from development to production. Understanding deployments and the strategies for effectively managing them is crucial for maintaining the integrity and performance of your FileMaker applications.

In Devin, any `fmp12` file that exists outside the development server is considered a deployment. These deployments are essentially live versions of your projects, situated in different stages of the development lifecycle (environments). Each deployment links back to a corresponding file in the development environment, as well as a release branch. This way you can link a branch to a specific environment which allows you to setup custom deployment flows. 

For instance, the below image shows an example where a `UAT` deployment is linked to a `test` branch, meaning that whenever there is a new release on the `test` branch, it can be deployed to `UAT`.

<figure><img src="https://3674518083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4WyrF9yRB5bw5h1SRZke%2Fuploads%2FcOgUnb6rQflNsy5vWj4R%2Fdeployments2.jpg?alt=media&#x26;token=a529cc87-9980-4cb5-8f25-f594bcbdf0c3" alt=""><figcaption><p>Example of a Module with a Deployment on two Environments, UAT and PROD, each linking to a respective Branch</p></figcaption></figure>