# Pre-release software

Pre-release software is still under development and testing. It may contain [bugs](https://en.wikipedia.org/wiki/Software_bug) and missing features. Sometimes, pre-release software includes [experimental features](https://help.sbtinstruments.com/encyclopedia/software/bactobox-r-software-changelog/experimental-feature).

## Availability

Pre-release software is not generally available. We offer pre-release software to selected users.

{% hint style="success" %}

## Want to test pre-release software?

[Reach out to us](mailto:customersupport@sbtinstruments.com)! Make sure to mention if there is a specific [experimental feature](https://help.sbtinstruments.com/encyclopedia/software/bactobox-r-software-changelog/experimental-feature) that you are interested in.
{% endhint %}

## Support

We offer *limited* support for pre-release software. We can not guarantee to address issues in a timely manner.

Use released software to *full* support. We fix issues in a timely manner (sometimes same-day fixes) for released software.

## How to install pre-release software

The procedure is the same as regular software releases. See [update-bactobox-r-software](https://help.sbtinstruments.com/getting-started/best-practices/update-bactobox-r-software "mention").

{% hint style="success" %}

## Installing an alpha or beta version? Create a backup first!

[Create a backup](https://help.sbtinstruments.com/encyclopedia/software/access/pages/backup-and-restore) before you install [pre-release software](https://help.sbtinstruments.com/encyclopedia/software/bactobox-r-software-changelog/pre-release-software). This ensures that your data is safe from any [bugs](https://en.wikipedia.org/wiki/Software_bug) in the pre-release software.
{% endhint %}

## Alpha, beta, and release candidate

At SBT, pre-release software goes through an *alpha*, *beta*, and *release candidate* phase. The corresponding [software version](https://help.sbtinstruments.com/encyclopedia/software/bactobox-r-software-changelog) uses this terminology. Examples:

* `v2026.02-alpha.7` 
* `v2026.02-beta.3`
* `v2026.02-rc.5`  (`rc` is short for release candidate)

Once development and testing is done, the final software version looks something like `v2026.02` . Sometimes, we issue a [hotfix](https://en.wikipedia.org/wiki/Hotfix) version such as `v2026.02a` .

See also [software release life cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle).