# tazjin/nixery

Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery

Repository: https://github.com/tazjin/nixery
Canonical: https://ross.abutalabs.com/products/nixery
Homepage: https://nixery.dev/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: nix, container-images, docker, container-registry, nixos, kubernetes, broccoli
Last push: 2026-04-08T08:49:31+00:00

## Health v2 (maintenance only)
Score: 66/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 76, release rhythm 35, longevity 100
- inputs: {"age_days": 2592, "days_push": 147, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2017, forks 82 (observed 2026-08-28T04:06:06.094305+00:00)

## What it is
Nixery is a Docker-compatible container registry that transparently builds container images on demand using the Nix package manager. Packages to include are specified as path components of the image name, and layers are cached and served from object storage like GCS or S3.

## Use cases
- pull ad-hoc container images with arbitrary nixpkgs packages without writing a Dockerfile
- run one-off tools in containers like docker run nixery.dev/shell/git/htop
- self-host a private container registry backed by a custom nixpkgs overlay in git
- serve efficiently cached image layers for Kubernetes workloads
- get ARM64 container images without cross-compilation setup

## When to choose
- you want container images built from Nix packages without maintaining Dockerfiles
- you need ephemeral images with arbitrary package combinations on demand
- you want layer caching that shares dependencies across images
- you run NixOS or Nix-based infrastructure and want registry-native delivery

## When to avoid
- you need reproducible, version-pinned images checked into CI
- your packages are not available in nixpkgs and you don't use Nix
- you need Windows container images
- you want a registry with full OCI push support from client-side builds

## Facets
- artifact type: service
- maturity: active
- function: container-runtime, deployment, package-manager, http-server, cloud
- domain: cloud-computing, developer-tools, self-hosted
- platform: cloud, self-hosted, go
- tags: nix, container-registry, oci-images, on-demand-builds, docker-registry, nixpkgs, devops, containers, linux, docker, kubernetes

## Member repositories
- tazjin/nixery (main) score 66

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:06.094305+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:00:41.270196+00:00, confidence not recorded.
  - readme: https://github.com/tazjin/nixery (fetched 2026-08-28T04:06:06.094305+00:00, sha dbdcca59df95)
  - homepage: https://nixery.dev/ (fetched 2026-08-29T10:40:34.206181+00:00, sha bb4b5771d1f4)
- Data as of 2026-08-30T08:39:29.467469+00:00.