Private Image Delivery

When Soviez installs or updates ERP, it downloads container images through Soviez’s authorized delivery path. You do not manage Docker Hub accounts or long-lived registry passwords on your server.

How it works

You start an authorized operation (--new, --update, or similar).
Soviez verifies your license and release entitlement with Soviez services.
Your server receives short-lived, pull-only access to download the exact approved image.
Soviez pulls the image, verifies it matches the signed release metadata, then removes temporary credentials.
ERP runs from the local copy. Continuous registry access is not required after download.

What you need

Outbound HTTPS from the server during install and update operations
Valid license and update entitlement for the release you are applying
No Docker Hub login on your host
No GitHub account

What stays on Soviez infrastructure

Upstream image hosting credentials remain on Soviez-operated infrastructure. Your server never receives permanent registry secrets.

Offline alternative

Air-gapped sites use signed offline update bundles instead of connected image download. See OFFLINE_UPDATES.md.

After images are local

A running ERP installation does not depend on continuous connectivity to the image delivery service. Temporary outages affect new downloads only, not day-to-day ERP operation.