Product

How Vesana works.

One server, three ways to get data in, one data path that consolidates everything.

System map

Every part, every connection.

This is the whole system as it runs after installation. Pick a route to follow it, or click a part to see what it does.

YOUR NETWORK VESANA SERVER HTTPS config 60 s SNMP · SSH · API HTTPS /receiver/ /api/ · /ws/ XADD group state SQL group outbox config 5 s checks secret profiles releases pull Community hub device profiles License portal releases · compose Image registry ghcr.io Browser web app · PWA API FastAPI · watchers Updater Docker socket Agent Go · Windows, Linux nginx TLS :443 · routing Receiver POST /api/v1/results Redis vesana:check_results Worker consumer · thresholds PostgreSQL TimescaleDB Collector Go · Linux VM Active collector systemd · on host Worker scheduler fallback · outbox Devices switch · NAS · UPS Targets websites · certificates Channels mail · push · chat

Route

A result

Agents, collectors and the active collector send results to nginx. The receiver checks who sent them and appends them to the Redis stream. Workers evaluate them and write state and history to PostgreSQL.

Part

Click a part of the map

Each box is a real component of a Vesana installation. The labels on the lines are the actual paths and names used between them.

    Three modes

    Each mode fits a
    different situation.

    Vesana treats them all the same: data comes in, gets consolidated, lands in the dashboard. Mix them freely.

    01

    Agent

    On the target system.

    When
    When you want to measure on the machine itself — CPU, RAM, disk, services, processes, event logs.
    What runs
    Lightweight single binary in Go. No runtime, no dependencies. Runs on Windows and Linux.
    Auth
    Token, stored hashed. One token per host.
    Transport
    HTTPS outbound, no inbound port required.
    02

    Collector

    In your (or your customer’s) network.

    When
    When you want to monitor devices that can’t or shouldn’t run an agent — switches, firewalls, UPS, NAS, printers.
    What runs
    Single binary in Go on a Linux VM. SNMP, SSH, ping, HTTP/S — plus anything you upload as a custom script.
    Auth
    API key, stored hashed. Multiple collectors per tenant.
    Transport
    HTTPS to the Vesana server. Outbound-only.
    03

    Active

    From the Vesana server itself.

    When
    When you want to measure something reachable from the server — public APIs, DNS, status endpoints, certificates.
    What runs
    The collector binary, installed on the Vesana server as a service. If it is offline, the worker runs the checks instead.
    Auth
    None — the server is the source.
    Transport
    Outbound from the Vesana server to the target.

    Setup

    Three steps, <15 minutes.

    Vesana is built as a self-hosted product. There is no cloud edition, so there is no cloud onboarding flow. You install, you start, you use it.

    1. 01

      Run the installer.

      One command as root on a 4 GB VM or any Linux host. It installs Docker if needed, pulls the stack, generates secrets and brings everything up. No Kubernetes required.

      curl -fsSL https://vesana.org/install | bash
    2. 02

      Finish setup in the browser.

      A web wizard walks you through admin account and organization. The check executor installs itself right after, and Vesana scans your network once — the first devices appear on their own.

      # in your browser
      https://your-server/setup
    3. 03

      Add more hosts.

      Download the agent or collector from the UI, paste token + URL. Done.

      # on the target host
      wget -qO- https://your.vesana/agent/install.sh | \
          bash -s -- TOKEN https://your.vesana