Lajstrom

Artifact registry on top of any OCI registry.

design phase

One server, many repository formats: apt, rpm, maven, pypi, npm, terraform modules, raw files. Every artifact is stored as an OCI artifact in the registry you already run: ECR, Harbor, Zot, GHCR, docker distribution. Lajstrom owns no bytes, only the index, and the index can always be rebuilt from the registry.

GitHubHow it works

How it works

  1. The OCI registry is the only storage and the source of truth. Lajstrom never stores artifact bytes itself.
  2. The database is a derived, rebuildable index plus a small control plane (repos, users, tokens, permissions).
  3. Clients keep their native tools. apt, dnf, mvn, pip, npm, terraform talk to Lajstrom as if it were their native repository. Protocol emulation is server-side; no client plugins.
  4. Docker images pass through to the backend registry untouched, with Lajstrom's RBAC and audit in front.

Formats

  • apt planned
  • rpm planned
  • maven planned
  • pypi planned
  • npm planned
  • terraform modules planned
  • raw files planned

Install

go install github.com/lajstrom/lajstrom@latest

Lajstrom is in the design phase and there is nothing to run yet. Today this command only prints a placeholder message. Placeholder packages are also reserved on PyPI, npm and crates.io under the name lajstrom.