A compatible computer you already keep online is the cheapest place to start. If you need a dedicated device, a used thin client can be worth comparing with a Raspberry Pi once power, storage and delivery are included. This tutorial sets up Relay on Linux so it starts automatically after a reboot.
Relay mainly suits personal monitoring and small budgets. For business monitoring, we recommend Enterprise or Ultimate with their included managed connection options. Relay remains available on every plan, including Free; your electricity, bandwidth and normal monitoring limits still apply.
Why use Relay if I can self-host a change monitor?
Even if you are comfortable self-hosting, we recommend Relay for personal monitoring of public pages that need your connection. You get PageCrawl's checks, history and alerts while your computer handles the traffic. Your setup skills go toward a small relay service, with the monitoring application managed for you.
With PageCrawl and Relay, you get:
- Avoid paid proxy bandwidth charges. When your pages work through Relay, replacing 5 GB of optional Web Unblocker traffic at $10/GB avoids $50 in bandwidth charges. See our Residential Proxies and Web Unblocker offering. The Residential options included in Enterprise and Ultimate are separate and do not spend that paid balance.
- Less work for a small computer. It does not need to run a browser to read pages or store growing monitoring history. Resource use still depends on traffic; a device suitable for Relay is not automatically suitable for a full monitoring application.
- Ongoing maintenance handled by PageCrawl. We maintain and update the monitoring service.
- Help when you need it. Paid plans include access to PageCrawl support for setup questions and monitoring issues. The Help Center is available on every plan.
- Keep your PageCrawl workflow. Your existing monitors, history and notifications stay together, with optional AI summaries and filtering subject to your plan's allowances.
Free software does not make fully self-hosted monitoring cost-free. Allow for hardware, electricity, storage and your time for setup, updates, backups and troubleshooting. Using an existing computer reduces the purchase cost. With Relay, PageCrawl maintains the monitoring service and stores your monitoring history.
Fully self-hosting is worth considering if you specifically need all monitoring data kept locally, access to authorized private-network pages, or changes to the monitoring application's code. Those needs go beyond Relay's role of connecting PageCrawl to public pages through your machine.
Relay requires a PageCrawl account, sends monitored content to PageCrawl and uses your normal plan limits. Use the steps below to set up Relay on hardware you already own, then test a few PageCrawl monitors. Check the captured results before adding more monitors; Relay does not guarantee access to every site.
Can I buy the complete setup for under US$30?
Treat US$30 as a total shopping budget, not a guaranteed kit price. A used computer with storage and its correct power supply included may fit. In September 2026, we could not verify a complete, readily available sub-$30 purchase in both the US and Europe. Reusing suitable hardware avoids that purchase.
Before ordering, add up the device, power supply, storage, network cable or adapter, tax and delivery. Include any installation accessories you need to buy. Do not count a multi-device bundle's per-unit price as the amount a reader can actually pay at checkout.
Look for a tested, working unit with an accessible BIOS, USB boot support and the matching power adapter. Avoid listings marked for parts, BIOS locked or missing storage. A return option is useful when buying used hardware. A cheap device with several missing accessories can cost more than a complete one.
Which computer should I use?
Use a computer that can run a supported 64-bit Linux system and matches one of Relay's downloads: AMD64 for Intel or AMD PCs, or ARM64 for compatible Arm boards. A wired connection simplifies setup. Keep existing NAS or Home Assistant installations intact and use their respective Relay installation options instead.
| You have or find | What to check | Installation path |
|---|---|---|
| A spare Intel or AMD computer already running Linux | 64-bit OS, working network and enough free storage | Follow the service steps below |
| A used Dell Wyse 3040 | Working 2 GB RAM, 8 or 16 GB storage, unlocked BIOS and correct power supply included | Install minimal Debian AMD64, then follow the service steps |
| A Raspberry Pi Zero 2 W | 64-bit OS, microSD card, power supply and 2.4 GHz Wi-Fi; check current stock and total cost | Raspberry Pi OS Lite (64-bit), then the ARM64 service steps |
| A NAS or Home Assistant system already running | Compatibility with its supported package | Use the Relay setup guide, without replacing its operating system |
The Wyse 3040 specifications list 2 GB RAM, 8 or 16 GB internal storage and Ethernet. Wi-Fi is optional, so do not assume it is included. There are different power-adapter variants; use the adapter specified for the particular unit. Its display outputs are DisplayPort, which may require an adapter for your monitor during installation.
The Pi Zero 2 W has a 64-bit processor and 512 MB RAM. Its advertised US$15 price covers the board, not a complete setup, and stock varies. The original Pi Zero and Zero W are 32-bit and cannot run the current ARM64 download. Another small board needs its own compatible, maintained 64-bit Linux image; a similar name is not enough.
These recommendations are based on the documented hardware and Relay's published architectures. Start with a few personal monitors and check resource use and connection stability.
How do I prepare Linux?
Start with a minimal, supported Linux installation and a working internet connection. For an Intel or AMD thin client, use the current Debian AMD64 installer without a graphical desktop. For a Pi Zero 2 W, choose Raspberry Pi OS Lite (64-bit). Both provide the systemd service manager used below.
For a spare thin client:
- Download the current Debian AMD64 network installer and follow the installation guide.
- Connect Ethernet, the correct power supply, and a keyboard and display for installation. Use the manufacturer's USB boot instructions. On a Wyse 3040, F12 opens the boot menu.
- Install onto the intended internal drive. This erases the selected drive's existing data. Back up anything needed and check the drive selection before continuing.
- Leave the root password empty if you want Debian to give your first normal user
sudoaccess. Select SSH server and standard system utilities, and leave graphical desktop choices unchecked. After installation, remove the installer USB and confirm Linux boots from internal storage.
Debian's no-desktop requirements recommend 1 GB RAM and 4 GB disk space. An 8 GB thin client may need the installer's small-disk partitioning scheme, and leaves limited room for updates and logs. Choose 16 GB if the price is similar.
For a Pi, use Raspberry Pi Imager and the headless setup guide to select the 64-bit Lite image and configure Wi-Fi and SSH. You can then connect from another computer without buying a dedicated screen or keyboard for the Pi.
The commands below assume your Linux account can use sudo. If it cannot, complete the system setup with an administrator before continuing. Update Linux and install the download tools:
sudo apt update
sudo apt upgrade
sudo apt install ca-certificates curlHow do I install the correct Relay download?
Download a released binary that matches the machine, verify its checksum, and install it with the matching service file. The commands below choose AMD64 or ARM64 automatically and stop on an unsupported architecture or failed download. They install files only; Relay starts after you configure its token in the next steps.
This example uses v0.1.5, the current release when this guide was checked. Review the release notes and change RELAY_VERSION if using a newer release. Run the whole block together:
(
set -eu
RELAY_VERSION=v0.1.5
case "$(uname -m)" in
x86_64) RELAY_ARCH=amd64 ;;
aarch64) RELAY_ARCH=arm64 ;;
*) printf 'Use a supported 64-bit Linux installation.\n'; exit 1 ;;
esac
RELAY_WORK_DIR="$(mktemp -d)"
trap 'rm -rf "$RELAY_WORK_DIR"' EXIT
cd "$RELAY_WORK_DIR"
RELAY_ASSET="pagecrawl-relay-linux-$RELAY_ARCH"
RELAY_RELEASE="https://github.com/pagecrawl/pagecrawl-relay/releases/download/$RELAY_VERSION"
curl -fL --retry 3 -o "$RELAY_ASSET" "$RELAY_RELEASE/$RELAY_ASSET"
curl -fL --retry 3 -o SHA256SUMS "$RELAY_RELEASE/SHA256SUMS"
sha256sum --check --ignore-missing SHA256SUMS
curl -fL --retry 3 -o pagecrawl-relay.service \
"https://raw.githubusercontent.com/pagecrawl/pagecrawl-relay/$RELAY_VERSION/pagecrawl-relay.service"
sudo install -m 0755 "$RELAY_ASSET" /usr/local/bin/pagecrawl-relay
sudo install -m 0644 pagecrawl-relay.service /etc/systemd/system/pagecrawl-relay.service
/usr/local/bin/pagecrawl-relay -version
)The checksum checks the download against the release's checksum file. For additional provenance verification, follow the release verification notes. No local compilation or Docker installation is needed for this path.
How do I connect the machine to PageCrawl?
In PageCrawl, open Settings, then More, then Relays, and add a machine. Give it a recognizable name and copy the token shown once. Store it in a protected local file so Relay can connect after a reboot. Treat the token as a password and keep it out of shared notes.
Relay starts a secure outbound connection to PageCrawl and keeps it open while running. PageCrawl sends website requests through that existing connection; it does not connect directly to your computer from the internet. Relay accesses the website through your internet connection and sends its response back. You do not need to open router ports, configure port forwarding, run a public proxy server, or have a static IP address.
Create a file readable only by the administrator, then open it in an editor:
sudo touch /etc/pagecrawl-relay.env
sudo chown root:root /etc/pagecrawl-relay.env
sudo chmod 0600 /etc/pagecrawl-relay.env
sudoedit /etc/pagecrawl-relay.envAdd this line, replacing the placeholder with your token, then save and close:
PAGECRAWL_RELAY_TOKEN=PASTE_YOUR_TOKEN_HERETell the service to read that file:
sudo systemctl edit pagecrawl-relayAdd these lines in the editable area:
[Service]
EnvironmentFile=/etc/pagecrawl-relay.envSave and close the editor. Do not paste your token into the command line, a public issue or a screenshot. If it is exposed, revoke the machine's access in PageCrawl and enrol it again.
How do I start Relay and check that it works?
Enable the service so it starts on boot, then check its status and the machine's connection in PageCrawl. Next, select that machine as a monitor's Location and inspect a captured result. A running service alone does not show that the target website accepts your connection or that its content was captured correctly.
sudo systemctl daemon-reload
sudo systemctl enable --now pagecrawl-relay
sudo systemctl status pagecrawl-relay --no-pagerIn PageCrawl:
- Confirm the machine appears connected under Settings → More → Relays.
- Choose a public page you can open through the same connection.
- Select the new machine under the monitor's Location, save and run a check.
- Review the captured content. Then reboot the computer when convenient and confirm Relay reconnects automatically.
Start with a few monitors. Watch Linux memory use with free -h, free storage with df -h, and the relay's traffic in PageCrawl. More frequent checks and larger pages use more bandwidth. For service logs, use:
sudo journalctl -u pagecrawl-relay -n 50 --no-pagerWhat should I do if setup fails?
Check the failing stage before changing the setup: Linux must boot, the binary must match its architecture, the service needs a valid token, and the monitor must select the connected machine. Read the service status and recent logs first. Do not remove the service's security settings to make an unexplained error disappear.
| Symptom | What to check |
|---|---|
| Linux does not boot from the internal drive | Use a current installer and the manufacturer's boot instructions. The Wyse 3040 has had an EFI boot-path issue; consult the current Debian guidance if an older installation is affected. |
Exec format error |
Match AMD64 to Intel/AMD or ARM64 to a 64-bit Arm OS. The original Pi Zero and Zero W cannot use the ARM64 binary. |
| Service runs but PageCrawl shows offline | Check the token override, internet access, system time and recent service logs. |
| Relay is connected but a monitor does not use it | Select that machine under the monitor's Location and save. |
| A page still fails through Relay | Check the original public page, captured content and the Relay guide. Relay does not inherit your browser login or reach private-network pages. |
How do I maintain or remove the relay?
Keep Linux and Relay updated, leave the machine online, and choose an offline policy that suits your monitors. Updates and power interruptions can temporarily disconnect the relay. Recheck a monitor after changing the setup, and remember that your machine supplies both download and upload bandwidth while PageCrawl's normal monitoring allowances still apply.
For a Relay update, read the release notes, repeat the installation block with the chosen release, then run:
sudo systemctl daemon-reload
sudo systemctl restart pagecrawl-relay
sudo systemctl status pagecrawl-relay --no-pagerConfigure the offline policy and an optional monthly data limit under Settings → More → Relays. See what happens when your relay is offline before relying on a connection that must always come from home.
To stop using this machine, move its monitors to another Location, disable the service, and revoke its access in PageCrawl:
sudo systemctl disable --now pagecrawl-relay