# Pre-production and development releases

To test any pre-production or development release:

### One-line install

The simplest way to test the latest development or pre-release version is to use one line installation method with the appropriate argument. More on that in [the one-line install documentation](https://docs.defguard.net/2.0/getting-started/one-line-install).

### Binaries and packages

Each GitHub repository ([core](https://github.com/DefGuard/defguard/releases), [gateway](https://github.com/DefGuard/gateway/releases), [proxy](https://github.com/DefGuard/proxy/releases), and [client](https://github.com/DefGuard/client/releases)) has its **pre-release versions** available on the GitHub release page. This is where you can download binaries or packages with the pre-release, e.g.:

<figure><img src="https://content.gitbook.com/content/qPYuWxfmxFk6sz1LLLwd/blobs/1IZXUuDVR4Nut3C6OHWH/Screenshot%202025-08-01%20at%2013.38.44.png" alt=""><figcaption></figcaption></figure>

### Docker images

Each Docker image for [core](https://github.com/DefGuard/defguard/pkgs/container/defguard), [gateway](https://github.com/DefGuard/gateway/pkgs/container/gateway) and [proxy](https://github.com/DefGuard/proxy/pkgs/container/defguard-proxy) has the following tags:

* `pre-release` – this tag is for the **latest pre-production release** - which also contains a version in form of `vX.Y.Z-alpha/beta/rcX` from the `main` branch
* `dev` – this tag is for the latest development release from the `dev` branch.

#### Docker compose

Please change the Docker compose file to match the version or tags as stated above.