Development
Self-host Nexus Repository on a VPS
A universal artefact repository manager.
Store and proxy artefacts for many ecosystems — npm, Maven, PyPI, Docker, apt and more — from one server.
Why self-host Nexus Repository?
For polyglot teams, one proxy/cache for every package format keeps builds fast, reproducible and independent of public registries.
How to install Nexus Repository
- 1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
- 2
Install the runtime
Install Java + blob store.
- 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 Nexus Repository its own database user with rights only on its own schema.
- Reverse-proxy Nexus Repository 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 Nexus Repository patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Nexus Repository need?
- Plan on 4 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Nexus Repository run on?
- Java + blob store.
- Can I run other things on the same VPS?
- Yes — size the plan so Nexus Repository plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Verdaccio, Harbor, Artifactory (commercial) — browse all app guides.