> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/software/miscellaneous/pre-release-software.md).

# 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](/software/miscellaneous/experimental-feature.md).

## 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](/software/miscellaneous/experimental-feature.md) 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® software](/more/software/update-bactobox-r-software.md).

{% hint style="success" %}

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

[Create a backup](/software/access/pages/backup-and-restore.md) before you install [pre-release software](/software/miscellaneous/pre-release-software.md). 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](/software/bactobox-r-software-changelog.md) 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).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/software/miscellaneous/pre-release-software.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.