Skip to content
stubbedevPublic

About

A self hosted nix cache in a single Go binary.

Resources

Security policy

Stars

30 stars

Watchers

0 watching

Forks

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Repository files navigation

xilo

CI coverage release

A self-hosted Nix binary cache in a single Go binary. One static executable is the server, the admin dashboard and the push client. It needs no other services.

The xilo dashboard: dedup ratio, storage, caches and tokens

Why xilo

  • One binary, no dependencies. SQLite or PostgreSQL for metadata, local disk or any S3-compatible bucket for data.
  • Deduplicated storage. Content-defined chunking (FastCDC) shares bytes across every path and every cache, and compresses them with zstd at rest.
  • Fast pushes. The client uploads only the chunks the server is missing, and can skip paths an upstream cache such as cache.nixos.org already signed.
  • Safe by default. Tokens are scoped to a single cache and revoked immediately. Signing keys never leave the server, and incomplete data fails with an error instead of a truncated download.
  • Multi-tenant. Workspaces, organizations, roles, quotas and optional self-service signup.
  • A real dashboard. Caches, tokens, users, live status and an activity log, in six languages, light and dark.

Quick start

Run the server:

docker run -d -p 8080:8080 -v xilo-data:/data \
  -e XILO_ADMIN_PASSWORD=change-me ghcr.io/stubbedev/xilo:latest

Open http://localhost:8080/admin, sign in as admin, then create a cache and a push token. On the cache's page you can copy the setup snippets.

Push to it:

xilo login http://localhost:8080 --token <token>
xilo push myteam/mycache ./result

Pull from it by adding the cache to nix.conf. xilo use myteam/mycache adds it for you:

extra-substituters = http://localhost:8080/c/myteam/mycache
extra-trusted-public-keys = localhost/myteam/mycache-1:<public-key>

Prebuilt binaries, the Nix flake, and the NixOS and home-manager modules are covered in Install.

Screenshots

A cache page with its dedup ratio and nix.conf, flake and CLI setup snippets

Cache: dedup and setup snippets

The status page: health, uptime, hit rate and live request, latency, throughput and storage charts

Status: live health and traffic

The activity log of every admin and API change, filterable by method and status

Activities: every admin and API change

The instance console listing every workspace with its storage and lifecycle controls

Console: every workspace on the instance

Performance

Same machine, same closure (93 paths, 646 MB of NAR), same load script. GitHub ubuntu-latest runner, 2 cores, 2026-11-18.

Bar charts comparing xilo with other self-hostable Nix caches on 8 measures, xilo highlighted. The table below holds every number.

Each chart has its own scale. A missing bar is a target that does not do that thing, not a zero.

Stored on disk: a host store keeps the closure unpacked, a cache stores it compressed.

The same numbers as a table
Measure xilo attic harmonia nix-serve-ng Garage + nix copy
narinfo throughput (requests/s, higher is better) 10,148/s 1,718/s 6,952/s 3,092/s 4,352/s
NAR pull throughput (MB/s, higher is better) 1083 MB/s 151 MB/s 1271 MB/s 31 MB/s —
Memory under pull load (peak RAM in use, lower is better) 89 MiB 130 MiB 25 MiB 42 MiB 19 MiB
CPU per MB/s served (% of a core per MB/s, lower is better) 0.16 1.10 0.16 3.82 —
Cold push of the closure (seconds, lower is better) 3.0 s 6.6 s — — 79.6 s
Repeat push of the closure (seconds, lower is better) 0.0 s 0.5 s — — 0.1 s
Stored on disk (bytes for this closure) 225 MB 212 MB 654 MB 654 MB 157 MB
Image or closure to deploy (bytes, lower is better) 11 MB 87 MB 78 MB 220 MB 28 MB

Bold is the best value of a measure that has a better direction; — is a target that does not do that thing.

CI measures these numbers and commits them; none are typed in by hand. Benchmarks explains the method, and Features compares xilo with the alternatives feature by feature.

Documentation

Install Docker, binaries, Nix flake, first run
Usage pulling, pushing, GitHub Actions, CLI, tokens, organizations
Configuration config file, environment, S3, PostgreSQL, NixOS and home-manager modules, TLS
Operations garbage collection, quotas, fsck, backups, upgrades, metrics
Features the full feature list and a comparison with other caches
Benchmarks how xilo compares with other caches, and the regression gate
How it works request path and what a push avoids doing
Development dev shell, recipes, UI stack, test suites

Development

nix develop    # go, templ, air, just, golangci-lint, ...
just dev       # live-reload server with demo data on :8090 (admin / demo)
just check     # everything CI runs

Run just to list every recipe. Development has the rest, including the UI stack and the test suites. RELEASING.md covers releases and SECURITY.md covers vulnerability reports.

License

MIT

About

A self hosted nix cache in a single Go binary.

Resources

Security policy

Stars

30 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages