Build an image
A build turns a self-hosted backend into an image in your own registry. It takes the backend as it is at that moment: its providers, its storage drivers, your contexts and scenarios, its runtime defaults and its current license.
Build
Open the backend under Self-hosted and choose Build at the top right. The build shows under Builds as Building, then Ready.
Each build makes the image for two platforms, linux/amd64 and linux/arm64, under one version. Docker and Kubernetes pull the one that fits the machine.
The version
A build is tagged with the release it was built from, such as v2026.09.23.3. Each build uses the newest release of the backend's type.
- There is no
latesttag. Your setup names the version it runs. - Building again from the same release replaces that version, the image and its files together. That is how a change to your scenarios or drivers reaches the version you already run.
- A newer release gives a new version. Older versions stay in your registry.
A build's details
Each row under Builds shows:
- The version, and when it was built.
- The license it carries.
- The storage drivers it holds, when you selected some.
- fetches its license, when the image fetches its license from us.
Open a row to see its files: one group per platform, and one for the build as a whole. The same files ship next to the image in your registry.
See Pull your image.
What can stop a build
- The license has used all its builds. A trial has a set number of builds, and a paid license a set number each calendar month, across your organization. Builds shows how many are left, and Build is unavailable once none are.
- Another build of your organization is still running. Try again once it finishes.
A refused build says which one it is.
When a build fails
A platform that fails shows Failed under the build, with a short reason. Build again, and contact us if it fails a second time.