How much RAM does Greenbone/OpenVAS need?

Plan on 4–8 GB for typical use; add headroom if you expect many concurrent users.

What stack does Greenbone/OpenVAS run on?

Greenbone Community containers.

Yes — size the plan so Greenbone/OpenVAS plus your other workloads fit in RAM with room to spare.

Security

A full-featured vulnerability scanner.

Scan your networks and hosts for known vulnerabilities with a regularly-updated feed.

A self-hosted scanner lets you check your own infrastructure on a schedule without paying per-scan fees.

1
Provision a VPS
Choose a plan with room for your data as well as the app.
2
Install the stack
Install Greenbone Community containers.
3
Deploy the application
Follow the project’s official install guide for your distribution.
4
Enable HTTPS
Serve it on your own domain behind a reverse proxy with a certificate.
5
Back it up
Schedule a database dump plus a copy of any uploaded files to an off-box location.

Give Greenbone/OpenVAS its own database user with rights only on its own schema.
Reverse-proxy Greenbone/OpenVAS 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 Greenbone/OpenVAS patched — most self-hosting incidents are unpatched software.

How much RAM does Greenbone/OpenVAS need?: Plan on 4–8 GB for typical use; add headroom if you expect many concurrent users.
What stack does Greenbone/OpenVAS run on?: Greenbone Community containers.
Can I run other things on the same VPS?: Yes — size the plan so Greenbone/OpenVAS plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Nuclei, Trivy (containers), Nessus (commercial) — browse all app guides.