How much RAM does Unbound need?

Plan on 512 MB–1 GB for typical use; add headroom if you expect many concurrent users.

Can I run other things on the same VPS?

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

Networking

A validating, recursive DNS resolver.

Run your own privacy-respecting recursive resolver with DNSSEC validation and local caching.

Your own resolver means no third party sees every domain you look up, and caching makes lookups faster.

1
Provision a VPS
Choose a plan with room for your data as well as the app.
2
Install the stack
Install Single C binary + DNS.
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 Unbound its own database user with rights only on its own schema.
Reverse-proxy Unbound 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 Unbound patched — most self-hosting incidents are unpatched software.

How much RAM does Unbound need?: Plan on 512 MB–1 GB for typical use; add headroom if you expect many concurrent users.
What stack does Unbound run on?: Single C binary + DNS.
Can I run other things on the same VPS?: Yes — size the plan so Unbound plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include AdGuard Home, Pi-hole, BIND — browse all app guides.