> For the complete documentation index, see [llms.txt](https://docs.devin.fm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devin.fm/features/deployments.md). # Deployments Devin streamlines how FileMaker projects are deployed and managed across various [**Environments**](/features/deployments/default-environments.md), 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`.

Example of a Module with a Deployment on two Environments, UAT and PROD, each linking to a respective Branch