Aller au contenu principal
Networking

Self-host Blocky on a VPS

A fast, lightweight DNS ad blocker.

A Go-based DNS proxy and ad blocker that runs happily on tiny hardware with a simple config.

Why self-host Blocky?

Blocky is a lighter, config-file-driven alternative to Pi-hole for people who prefer YAML to a web UI.

How to install Blocky

  1. 1

    Provision a VPS

    Choose a plan with room for your data as well as the app.

  2. 2

    Install the stack

    Install Single Go binary + DNS.

  3. 3

    Deploy the application

    Follow the project’s official install guide for your distribution.

  4. 4

    Enable HTTPS

    Serve it on your own domain behind a reverse proxy with a certificate.

  5. 5

    Back it up

    Schedule a database dump plus a copy of any uploaded files to an off-box location.

Practical tips

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

Frequently asked questions

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

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