How to self-host Homepage

Your own start page: one screen of tiles linking to everything in your workspace. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with Homepage

Its configuration is written before the container ever starts, so Homepage comes up already set up rather than showing you a blank first-run form.
Given its own web address, still behind your panel login. Homepage can't live under a shared path, but it can see your files — so the panel gate stays in front of it.

Why run Homepage yourself

Small tools are where a subscription is hardest to justify: a few pounds a month, times a dozen tools, for software that would run happily on a server you already pay for.

What kind of server Homepage needs

Small. These are the sort of app people run on a server they already have, alongside everything else, without thinking about capacity.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run Homepage

Homepage runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so Homepage is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when Homepage should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so Homepage can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing Homepage

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick Homepage from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What's left for you to do

Cresdock does not pretend to do the parts that are genuinely yours to decide. After it's running:

Open it. Your installed apps can be added as tiles in its settings files

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:v1.13.2
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./homepage/config:/config

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Point a DNS record at the server, because Homepage cannot run under a shared path
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, Homepage is one click and none of the above exists.

Common questions

Do I need to know Docker to run Homepage?

No. Cresdock installs Homepage in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. Homepage gets its own web address and its own certificate, because it cannot run under a shared path.

What happens to my Homepage data when it updates?

Cresdock updates the Homepage image and leaves its stored data in place. Homepage keeps its own files in its own folder, which survives an update, a rebuild and a reinstall — and Cresdock never writes into it.

Can I run Homepage at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and Homepage is reachable on your own network first. A rented server is only needed when Homepage must be reachable from anywhere without a VPN.

Can I remove Homepage later?

Yes. Cresdock removes Homepage in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what Homepage itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: IT-Tools · linkding · Migration Tool

Before you start: where to rent a server · what it needs to run · Cresdock vs Cloudron