# Umami: your first steps

> Sign in, add a website, paste the tracking script and keep Umami current.

Source: https://veldhost.eu/docs/umami-getting-started

Picked Umami? Your site came with Umami installed on the Node.js runtime — simple, privacy-friendly analytics without cookies, so no consent banner is needed for it.

## What gets installed

- **Umami** built from the pinned release tag of the official repository (the commit is checked before the build), running as a systemd service on Node.js 22 with its own **PostgreSQL** database in your container.
- The default `admin` account with the well-known default password already **replaced** by a generated one; telemetry and update checks off.
- Settings live in `.env` in the site's code root (Files tab): `DATABASE_URL` and `APP_SECRET`.

## First login

1. Your site page shows the sign-in address (`/login`), the `admin` username and the generated password — we display it for 7 days, so save it now.
2. Sign in, then set your own password under **Profile → Change password**.
3. Add a website under **Settings → Websites → Add website** and copy its tracking script — `<script defer src="https://your-umami/script.js" data-website-id="…">` — into the site you want to measure.
4. Invite colleagues under **Settings → Users**; a Team lets several people share websites.

## Updating

- Press **Back up now** on the Files tab first.
- Check out the next release tag in the code root (SSH: `git fetch --tags && git checkout vX.Y.Z`), then run a deploy: `npm install`, `npm run build` (which applies the database migrations) and a restart. The build needs about 1.5 GB for a few minutes; on the Starter plan we lend it for the first install — for updates, ask support or use a Pro plan.

## Limits

- Umami runs comfortably in a Starter container (768 MB) for a handful of sites; millions of events a month want Pro.
- Country lookup uses the GeoLite2 database downloaded at build time; it is not refreshed until the next build.