About Packr
A private npm registry for teams that actually ship.
Why Packr exists
Every existing npm registry was built for interactive human workflows and makes CI painful. Session cookies, captchas, device codes that require a TTY, permission models designed for human organizations rather than ephemeral CI jobs.
Packr exists because modern teams publish packages from CI, not laptops. We needed a registry where a token is just a token — no browser, no refresh flow, no cookies. Where permissions can be split per job (read vs publish), scoped to an org, and rotated without drama. And where AI agents can query the registry the same way they query any other API.
It started as an internal tool at BlueForge Studio when we got tired of the Verdaccio + GitHub Packages duopoly. Source-available, free to self-host, and designed to Just Work.
Design principles
CI is the primary user
Every auth flow must work in a headless environment. Every error must be structured JSON. Every rate limit must return a sensible retry header.
Least privilege by default
Tokens have fine-grained permissions (read, publish, unpublish, admin) and optional scope restriction. A CI token can publish to @myorg and nothing else.
Self-hostable without regret
One Go binary, one SQLite file (or Postgres if you want scale), one S3 bucket for tarballs. Docker, Kubernetes, Fly.io, or bare metal. No license server, no phone-home telemetry.
AI agents are first-class
Agent endpoints return quality scores, capability hints, comparisons, dependency graphs, and AI-generated documentation. An MCP server ships in the box so Claude and Cursor can query your registry directly.
Tech stack
- Registry server
- Go 1.25, stateless, runs anywhere
- Dashboard
- Next.js 16 App Router, React 19, Tailwind CSS
- Database
- SQLite (default) or PostgreSQL with read replicas
- Blob storage
- Any S3-compatible service: AWS S3, Backblaze B2, Supabase Storage
- Auth
- JWT (CI), OAuth device flow (CLI), session cookies (dashboard)
- AI
- Claude API for docs generation, pluggable providers for embeddings
- Deployment
- Fly.io (registry), Vercel (dashboard), Helm chart (K8s)
- CI/CD
- GitHub Actions, Playwright e2e, Go unit tests
The team
Packr is developed by BlueForge Studio, a small independent studio building developer infrastructure. We ship source-available tools that treat CI as a first-class user, not an afterthought.
We also build Forge Auth (centralized OAuth proxy for multi-app BlueForge ecosystems) and a growing set of agent tooling. Packr is part of a bigger picture: the infrastructure that modern AI-assisted teams need but don't want to build themselves.
Get in touch
- GitHub: kristianmandrup/packr-registry — issues, pull requests, and discussions
- Website: blueforge.studio
- Live registry: api.packr.blueforge.studio
See what Packr can do
Browse the documentation, check the pricing tiers, or read the changelog to see what we shipped recently.