AdGuard Home VPS plans currently listed

ProviderPlanvCPURAMDiskRegionsBillingPrice
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesFixed price$5.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAmsterdam, NetherlandsFixed price$5.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAmsterdam, NetherlandsFixed price$9.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesFixed price$9.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAmsterdam, NetherlandsFixed price$16.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAshburn, United StatesFixed price$16.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAmsterdam, NetherlandsFixed price$32.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAshburn, United StatesFixed price$32.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesHourly$0.007/hr
EnzonixShared Compute - General Compute12 GB40 GBAshburn, United StatesHourly$0.01/hr
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesHourly$0.015/hr

AdGuard Home Instant App

Self-hosted AdGuard Home VPS hosting

AdGuard Home is an open-source DNS server that blocks ads and trackers for every device that uses it. Compare live VPS prices, CPU, RAM, disk and regions, launch AdGuard Home on the plan you choose, and keep root access so filter lists and query logs stay on your server.

AdGuard Home

Instant App on marketplace VPS

Live marketplace offers

Compare AdGuard Home VPS plans

Choose billing and size, compare providers side by side, pick a location, then launch.

Enzonix

Shared Compute - General Compute

$5.00/mo

1 vCPU · 1 GB · 20 GB

Choose location

Ashburn, United States

1 provider

Inside AdGuard Home

AdGuard Home is a self-hosted DNS server for network-wide ad and tracker blocking. Use it instead of paying for NextDNS or AdGuard DNS. Point phones, laptops, smart TVs and IoT devices at the resolver to sinkhole known ad domains, watch query stats, and tune filter lists from a web UI. Sign in as admin with starter blocklists already enabled. No Instant App form fields are required at create time.

  • AdGuard Home dashboard with DNS query and block statistics

    Dashboard with live DNS stats after login

    Open AdGuard Home and see queries, blocked requests and top clients. The dashboard shows real traffic density instead of an empty first-run screen.

  • AdGuard Home query log with filtered DNS requests

    Query log for every lookup

    Inspect which devices asked for which domains, what was blocked, and which upstream answered. Useful when a site breaks and you need to whitelist fast.

  • AdGuard Home filters page with enabled DNS blocklists

    Filter lists you control

    Starter AdGuard and community lists are already on. Add more Hostlists Registry feeds or custom rules when you want stricter blocking.

  • AdGuard Home settings and DNS configuration

    Admin account ready after boot

    The first admin user is created for you. Sign in with the username and password from your server notes, then point routers or devices at the VPS DNS address.

Why use the NodeRings marketplace?

Compare live AdGuard Home VPS plans from independent providers, then self-host network-wide DNS ad blocking on the offer you pick. Use it instead of paying for NextDNS or AdGuard DNS.

  • Compare AdGuard Home VPS offers in one place

    See live prices, regions and plan sizes before you buy. Shop DNS ad-blocking hosts across independent providers, including 1 GB boxes that fit a household resolver.

  • Self-host AdGuard Home without a manual install

    Pick a plan and AdGuard Home is prepared on that VPS for you, including the admin account and starter blocklists. You still get root access.

  • Place DNS where you need it

    Compatible offers list cities and countries. Put the resolver close to home, behind a VPN, or on a LAN-facing VPS you control.

  • Own the filters and the query log

    Blocklists, custom rules and query history live on your VPS volume. You control SSH, who can sign in, and which devices use the resolver.

AdGuard Home hosting as a marketplace, not a single hoster

Most AdGuard Home VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted DNS offers by price, size and region, then launch on the one that fits.

AdGuard Home Instant App prepares AdGuard Home on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.

Single-provider AdGuard Home hosting

  • One company catalogue and renewal pricing
  • One set of regions and support paths
  • One vendor panel for that host only

NodeRings marketplace

  • AdGuard Home VPS offers from independent providers
  • Compare resources, prices and regions side by side
  • Deploy AdGuard Home on the plan you pick

How it works

Compare plans, pick a provider offer, and launch AdGuard Home on that server.

  1. 01

    Compare AdGuard Home VPS plans

    Browse live offers below. A 1 GB plan is a solid start for household DNS. Sort by provider, size, price and region.

  2. 02

    Pick the offer that fits

    Choose the provider plan and region. There are no Instant App form fields to fill for AdGuard Home.

  3. 03

    Deploy and sign in

    Confirm checkout and wait for the server. Then open the site URL and sign in with the admin username and password from your server notes. Point devices at the DNS IP. You keep root SSH.

On the VPS after AdGuard Home deploys

NodeRings Instant App brings AdGuard Home up with Docker Compose and creates the first admin account for you. Use the sections below to reach the UI, find passwords, and operate the stack.

Open the admin UI

  • In a browser, go to http://YOUR_SERVER_IP/ using the IPv4 from your order.
  • You get the login screen. This Instant App skips AdGuard Home's first-run wizard.
  • Use the admin username and password from the credentials file in the next section.
  • For filtering, set that same VPS IP as DNS on a router, device, or VPN profile that you trust.

Where the password is

Credentials are written on first boot to:

/root/.noderings_password

Read them over SSH:

cat /root/.noderings_password
  • Keys in that file include adguard_admin_user, adguard_admin_pass, site_url and dns_ip.
  • SSH in as root with the create-flow password or key, then run the command above.
  • Change the AdGuard Home admin password after you first sign in.

Where files live

Compose project directory

/opt/noderings/adguard-home
/opt/noderings/adguard-home/docker-compose.yml
/opt/noderings/adguard-home/.env

Working directory for compose, the stack file, and generated secrets.

AdGuard Home config

/opt/noderings/adguard-home/conf
/opt/noderings/adguard-home/conf/AdGuardHome.yaml

Admin user hash, upstream DNS, filters and related settings.

Runtime data

/opt/noderings/adguard-home/work

Query log, stats and downloaded filter data.

Credentials file

/root/.noderings_password

Written once on first boot.

Boot unit

/etc/systemd/system/noderings-adguard-home.service

Brings compose up after Docker is ready.

What runs in Docker

A single Compose service runs AdGuard Home. The admin UI is on HTTP port 80. DNS is on port 53 (TCP and UDP). AdGuard Home also applies a per-client rate limit of 20 queries per second; that slows abuse a little but does not replace a firewall or client allow list.

  • adguardhome

    DNS resolver plus web admin UI.

Container status

cd /opt/noderings/adguard-home && docker compose ps

Live logs

cd /opt/noderings/adguard-home && docker compose logs -f

Restart containers

cd /opt/noderings/adguard-home && docker compose restart

systemd unit status

systemctl status noderings-adguard-home

Add HTTPS with Cloudflare

Your AdGuard Home admin UI starts on http://. Cloudflare can give the UI a padlock without installing anything on the VPS.

  1. Add your domain

    Sign up at Cloudflare and add the domain you want to use.

  2. Point it at your VPS

    Create an A record to your server IP and leave the orange cloud on.

  3. Open the https site

    Visit https://your-domain for the admin UI and sign in with the credentials from your server notes. Keep DNS on the raw VPS IP (do not send port 53 through the Cloudflare proxy).

  4. Only allow Cloudflare

    Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:

    curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done

That is enough for a first secure visit. You can tighten SSL in Cloudflare later if you need it. Keep port 22 allowed for SSH; leave other ports denied except this Cloudflare allow for 80 and 443.

More detail

  • First boot turns off the Ubuntu systemd-resolved stub listener so AdGuard Home can bind port 53.
  • NodeRings does not sell AdGuard Home as a product and is not the AdGuard Home project.

AdGuard Home VPS requirements and sizing

AdGuard Home is light. Public measurements show roughly 45 MiB idle and about 130 MiB under a heavy query flood for a single container with default filters. More lists, longer query logs and many clients raise RAM and disk. These are starting points, not guarantees.

Illustrative starting points for AdGuard Home VPS sizing
WorkloadIllustrative starting pointNote
Home or small office1 vCPU / 1 GB RAM / 20+ GB diskSuggested Instant App floor for household DNS with starter blocklists.
Many devices or longer logs1–2 vCPU / 2 GB RAMHeadroom when dozens of clients and multi-day query history stay online.
Large custom listsWatch RAM and disk as lists growExtra Hostlists Registry feeds and long retention cost memory and storage.
PlacementLAN or VPN, not an open resolverPrefer private DNS for household devices. Do not expose recursive DNS to the whole internet.

These are starting points, not guarantees. Needs depend on client count, filter size, query rate and how long you keep logs.

Root access and who does what

This is self-hosted AdGuard Home on a provider VPS, not NextDNS or AdGuard DNS SaaS. You pick the plan. AdGuard Home is prepared on that server. Day-to-day care stays with you.

  • What you get ready

    AdGuard Home is prepared on the VPS with no Instant App form variables. The admin account and starter filter lists are created for you.

  • What you keep

    Root SSH on the VPS. You own filter lists, custom rules, query logs, DNS, TLS, OS updates and backups unless a provider product says otherwise.

  • What is not included

    Managed DNS routing, automatic TLS, VPN concentrators and hands-off OS patching are not bundled in. Point clients and finish TLS after the server is up if you need them.

  • Support boundaries

    NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after AdGuard Home on the server is yours.

AdGuard Home VPS FAQs

What is AdGuard Home?

AdGuard Home is a free, open-source DNS server that blocks ads and trackers network-wide. Devices that use it as their DNS resolver stop resolving known ad and tracker domains.

Do I need to fill Instant App variables for AdGuard Home?

No. AdGuard Home Instant App asks for no form variables at create time. After the VPS is ready, sign in with the admin username and password from your server notes.

Does NodeRings run the AdGuard Home server?

No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, AdGuard Home is prepared on that provider server, and you manage DNS from there.

Is this managed AdGuard Home hosting?

No. You get a virtual machine with AdGuard Home prepared for you, plus root access. That is different from a managed product that owns updates and support for you.

What is AdGuard Home Instant App?

It prepares AdGuard Home on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.

How do I sign in after deploy?

Open the site URL from your server notes and sign in with adguard_admin_user and adguard_admin_pass from /root/.noderings_password. Nothing was collected from you at checkout for AdGuard Home.

How do devices use AdGuard Home?

Set the VPS IP as DNS on your router, VPN profile or individual devices. Household filtering only works for clients that send DNS to this resolver.

Should I expose DNS port 53 to the public internet?

Prefer LAN or VPN access for recursive DNS. An open resolver on the public internet can be abused. Many operators reach AdGuard Home over WireGuard or Tailscale instead.

What size AdGuard Home VPS do I need?

A common starting point for household DNS is about 1 vCPU, 1 GB RAM and 20 GB disk. Larger lists and longer logs usually need more RAM and disk. Use the sizing guide above and compare plans in the list.

What happens after I click Deploy AdGuard Home?

You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes, then point devices at the DNS IP.

Can I choose the server region?

Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and where your clients will reach the resolver.

Back to live AdGuard Home plans

Compare provider offers, then launch AdGuard Home on the plan that fits.