Connected self-hosted

What you need before you start

• A server, NAS or VM on your network that can run a container (Docker or a Kubernetes cluster), reachable from the subnets you want Totenvis to see.
• A Totenvis account at account.totenvis.com — sign up free, or on your paid plan — with this install's licence key ready to copy.
• Optional, but worth having ready: a read-only SNMP community string for your switches and access points. Without one, those devices still turn up, just without the detail SNMP would add.

The steps to a running install

1. Get the image. There's no self-serve way to pull it yet — the image lives on a private GitHub package today, and the customer registry we're building will let you sign in to your account, copy a pull token and docker login from there. Until it ships, contact us and we'll get you a build directly.

   Screenshot coming soon Your account page: the registry sign-in command and your pull token (coming soon)

2. Start the Totenvis container — on Docker Compose, or the Helm chart if you're on Kubernetes — pointed at the network you want it to discover.

   Screenshot coming soon A terminal starting the container with docker compose up

3. Open it in a browser. A brand-new install shows one screen: create the admin account.

   Screenshot coming soon The create-admin-account screen on first open

4. A short first-run walk-through follows: which of the four ways this install is being run as (choose Connected self-hosted here — it's also the default if you skip the question), an SNMP community string, whether any of your network is cloud-managed, and how your devices are managed day to day. Every one of these is skippable and can be set up later.

   Screenshot coming soon The first-run walk-through's install-kind question

5. Totenvis scans on its own from here. Open the Readiness tab to see what answered and what didn't, then the Topology tab for the map.

   Screenshot coming soon The Topology tab's map after the first sweep

Signing in for the first time

The admin account you create above is this install's own sign-in — separate from your account at account.totenvis.com, which holds your plan, your licence and your invoices rather than anything about your network. After that first screen, every visit to this install needs that admin sign-in (or an account it creates for someone else).

Adding your licence

Sign in at account.totenvis.com and copy this install's licence key. Paste it into the install's Licence panel (on the Readiness tab) — or set it once in the container's environment when you first start it, if you'd rather not do it by hand. From there, the install checks in with your account periodically on its own, which is the only thing that ever leaves your network, and keeps the licence current without you doing anything further. A lapsed check-in gives you a grace period before anything stops working, with the Readiness tab saying exactly how long is left; renewing restores it with no restart.