Enterprise Store Documentation

colin-c · 28 August 2026 14:59

The enterprise-store operator installs and manages the

enterprise-store snap with Juju. Compared to running the bare snap, the charm adds the

ability to run several nodes for high availability and to drive all

configuration declaratively through Juju.

Deployment modes

The enterprise-store lets you run the Snap Store on your own premises, either as

a proxy in front of the global Snap Store or as a fully self-contained store for

airgapped environments.

The default mode. The enterprise-store acts as an edge proxy in front of the

global Snap Store. Devices are pointed at the proxy and all traffic to the Store

flows through it, which lets you cache snaps and override the revisions your

devices receive. The unit needs to be able to reach the Snap Store to install

the snap and to proxy requests. See the Proxy mode deploy guide.

Nothing reaches the internet. The snaps that make up the enterprise-store are

shipped in through the store-bundle resource, and blob storage is provided by

an S3 backend via the s3-integrator charm.

Snaps and brand stores are exported elsewhere and pushed into the store. See the

Offline mode deploy guide.

Either mode can be run with multiple units behind the

haproxy charm, which terminates client TLS at the

edge and load-balances across the units. See the

Mapping table

Path	Location