Packyard is a Composer v2 registry written in Go. One binary, embedded admin dashboard, SQLite/MySQL/Postgres for metadata, local disk or any S3-compatible bucket for package storage. AGPL-3.0 licensed, no SaaS lock-in.
These docs cover everything you need to run Packyard in production: installation, configuration, connecting Composer, and managing organizations. Pick a guide from the sidebar or the cards below.
If you're new, start with the installation guide — the happy path is one curl command and an interactive wizard, done in about five minutes.
Guide
Installing Packyard
One-line install, interactive setup, and recipes for unattended automation, air-gapped hosts, reverse proxies, upgrades, and uninstall.
Guide
Configuration
Every PACKYARD_* environment variable, what it does, what defaults look like, and which ones the server refuses to start without.
Guide
Connecting Composer
Configure composer.json, mint a token, and authenticate Composer against your Packyard registry.
Guide
Organizations
Per-org packages, tokens, members, and isolation. Every install ships with a `default` org; add more for per-team or per-customer isolation.
Guide
Developer Notes
Notes for contributors working on Packyard internals, including dashboard internationalization.