Welcome to the home page of the Deckhouse Galleon documentation.
Deckhouse Galleon is an artifact registry that runs inside your own infrastructure. Private packages and container images stay within your perimeter, and external dependencies are cached locally: builds do not depend on the availability and rate limits of public registries, and access to artifacts remains under your control.
Key features
- One registry instead of several services. Container images, Go, Maven, npm, PyPI, RubyGems, and Cargo packages, and arbitrary files are stored and served by a single service — with a single access model and a common web interface.
- Builds do not depend on public registries. Proxy repositories cache dependencies from Maven Central, Docker Hub, and other external registries: once downloaded, artifacts are served from the local cache, unaffected by the rate limits and outages of external sources.
- Publishing with standard tools.
Developers publish and fetch artifacts with the usual commands —
docker push,mvn deploy,npm publish,go get— no extra plugins or tooling. - Access under control. Roles and privileges are scoped down to a single repository and action; CI uses tokens that do not expose passwords, and anonymous read access is enabled only where it is needed.
- Efficient storage. Identical content is stored only once, and the space left after deleting artifacts is reclaimed automatically by the background garbage collection.
Documentation sections
The documentation consists of the following sections:
- Concepts — how repositories, access control, and proxy caching work.
- Administration guide — installation, configuration, repositories, access control, operations.
- User guide — the web interface and client setup for every format.
Questions about the product can be asked in the Telegram channel. For technical support, reach out via support@deckhouse.io.