Development
Self-host Verdaccio on a VPS
A lightweight private npm registry proxy.
Host private npm packages and cache public ones locally, so builds run faster and can survive an npm outage.
Why self-host Verdaccio?
A private npm proxy speeds up CI, keeps private packages off the public registry and insulates you from upstream outages.
How to install Verdaccio
- 1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
- 2
Install the runtime
Install Node.js + filesystem/S3.
- 3
Deploy the application
Net what you need from the project’s official source and run it.
- 4
Put it behind TLS
Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.
- 5
Add it to your backups
Include the data directory and database in your backup routine before you rely on it.
Practical tips
- Give Verdaccio its own database user with rights only on its own schema.
- Reverse-proxy Verdaccio and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Verdaccio patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Verdaccio need?
- Plan on 1–2 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Verdaccio run on?
- Node.js + filesystem/S3.
- Can I run other things on the same VPS?
- Yes — size the plan so Verdaccio plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Gitea Packages, Nexus Repository, GitLab Registry — browse all app guides.