Skip to content

Introduction

Entrepot is a self-hosted package repository manager for Kubernetes. It hosts your own packages and proxies (pull-through caches) public registries, behind single sign-on — in the spirit of Sonatype Nexus or JFrog Artifactory, but built as one stateless Go binary with Postgres for metadata.

entrepôt — a port where goods are stored and re-exported without duties.

Format Hosted Proxy Group Native clients
Raw files ✅ ✅ ✅ curl, wget, anything HTTP
PyPI ✅ ✅ ✅ pip, twine, uv, poetry
npm ✅ ✅ ✅ npm, yarn, pnpm
Docker / OCI ✅ ✅ ✅ docker, podman, containerd, crane, helm (OCI)
Apt (signed) ✅ ✅ apt-get
Yum / RPM (signed) ✅ ✅ dnf, yum
Helm (HTTP) ✅ ✅ ✅ helm, helm cm-push

Around those formats, Entrepot gives you:

  • Proxies that behave. Proxies revalidate with conditional requests, collapse concurrent misses into one upstream fetch, cache 404s, and keep serving cached content when the upstream is down.
  • Per-repository storage. Every repository is bound to a blob store: a PVC, EBS, EFS or S3. Content is addressed by SHA-256 and deduplicated.
  • Single sign-on from day one. Keycloak or any OIDC provider for people, group-based roles and scoped API tokens for machines.
  • GitLab CI without secrets. Jobs authenticate with their id_token, and trust policies decide which projects, branches and environments may publish where.
  • Vulnerability scanning. Trivy, Grype or a webhook scanner on upload, on proxy fetch, on demand or on a schedule. Repositories can warn or quarantine, with waivers, and results go back to GitLab as commit statuses and MR notes.
  • Hygiene. Cleanup policies, routing rules and groups that prefer hosted packages to defeat dependency confusion. Secrets are encrypted at rest.
  • API first. A spec-first OpenAPI 3 API with Swagger UI at /api/docs, a generated Go client and a Terraform/OpenTofu provider.
  • Kubernetes-native. Stateless pods, a Helm chart, Prometheus metrics and health probes.
  • Web UI. Browse, search, upload, manage repositories, tokens and access control — every repository page has a Set up client panel with ready-to-paste snippets.
  • Getting started — run it locally, create your first repositories and learn the vocabulary.
  • Using repositories — one page per format: setup, client configuration, publishing and troubleshooting.
  • CI/CD — GitLab CI with id_tokens, GitHub Actions and Jenkins with service-account tokens.
  • Security — authentication, authorization, scanning, dependency confusion, secrets and signing keys.
  • Operations — deploying with Helm, configuration reference, storage, backups, scaling and monitoring.
  • Infrastructure as code — the Terraform / OpenTofu provider.
  • API — conventions, curl recipes, the Go client and the full API reference.

Throughout the docs, https://entrepot.example.com stands for your server and $ENTREPOT_TOKEN for a token Entrepot accepts (an API token, an OIDC access token or a GitLab CI id_token).