Self-host UpSnap with Levelrail

Web dashboard to wake, shut down and ping devices on your network, with scheduled wake ups and per device ports.

  • Authorseriousm4x
  • LicenceMIT
  • Memory128 MiB
  • Services1

How to self-host UpSnap

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/seriousm4x/upsnap:5.7.3
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8090.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Open the address and create the first admin account. Wake on LAN needs the container on the same network as the devices, so check reachability from a test device.

UpSnap requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8090
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then UpSnap. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the UpSnap docs page.

Deploy UpSnap your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy UpSnap from the CLI

levelrail-cli templates deploy upsnap --name my-upsnap

Deploy UpSnap with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/upsnap/deploy

UpSnap configuration

UpSnap services

ServiceImagePortsVolumes
upsnap ghcr.io/seriousm4x/upsnap:5.7.3 8090 data -> /app/pb_data

UpSnap environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8090
Volumes
1 named mount: data -> /app/pb_data

UpSnap FAQ

How much memory does UpSnap need?

The catalog lists about 128 MiB of memory for UpSnap.

Does UpSnap run on arm64?

For UpSnap, arm64 support is not confirmed; amd64 is unknown.

What licence is UpSnap under?

UpSnap is licensed under MIT, which is permissive, with few conditions on reuse.

Does UpSnap need configuration before it starts?

No. The template fills in its own defaults.

Which ports does UpSnap use?

UpSnap listens on port 8090 inside the stack.

Where does UpSnap keep its data?

In a named volume: data mounted at /app/pb_data.

Can I deploy UpSnap on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id upsnap for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/seriousm4x/upsnap:5.7.3 is what you deploy there.

levelrail-cli templates deploy upsnap --name my-upsnap