Skip to content

Deployment & topologies

The suite scales from one console on a desk to a hall full of stations, a stream and several displays. The building blocks stay the same. Only the number of stations changes and where each service runs.

Topology A: Minimal (demo / practice)

One Windows PC runs everything. One station captures one NES.

flowchart LR
    NES["<span style='color:#f8fafc'>🎮 NES</span>"]:::hw --> CAP["<span style='color:#f8fafc'>USB capture</span>"]:::hw --> ST["<span style='color:#111111'>nestris-station<br/>(Debian mini PC)</span>"]:::core
    RD["<span style='color:#111111'>RFID reader</span>"]:::rfid --> ST
    subgraph PC["Windows PC"]
        LTM["<span style='color:#111111'>NestrisLTM</span>"]:::ltm
        MQ["<span style='color:#ffffff'>Mosquitto</span>"]:::ext
        PG[("<span style='color:#ffffff'>PostgreSQL</span>")]:::ext
        OBS["<span style='color:#ffffff'>OBS</span>"]:::ext
    end
    ST -- MQTT + HTTP --> MQ & LTM
    MQ --> LTM <--> PG
    LTM -- overlay --> OBS

    classDef ltm fill:#f5b800,stroke:#7a5c00,color:#111,stroke-width:2px
    classDef core fill:#22d3ee,stroke:#0e7490,color:#111,stroke-width:2px
    classDef rfid fill:#f472b6,stroke:#be185d,color:#111,stroke-width:2px
    classDef ext fill:#64748b,stroke:#334155,color:#fff,stroke-width:2px
    classDef hw fill:#1f2937,stroke:#94a3b8,color:#f8fafc,stroke-dasharray:4 3

No station hardware yet?

The desktop tools in nestris-core (CLI, egui/Qt GUI, browser GUI) run the same recognition engine on a capture card, webcam or video file. Use them to try recognition before you build a station.

Topology B: Full tournament hall

A dedicated host PC, one station per console, a registration terminal, a stream PC and screens in the hall. Everything sits on its own switch or VLAN.

flowchart TB
    subgraph LAN["Tournament LAN (closed network)"]
        direction TB
        SW{{"<span style='color:#f8fafc'>Switch</span>"}}:::hw

        subgraph ST["Stations × n"]
            direction LR
            S1["<span style='color:#111111'>Station 1</span>"]:::core
            S2["<span style='color:#111111'>Station 2</span>"]:::core
            S3["<span style='color:#111111'>Station 3</span>"]:::core
            S4["<span style='color:#111111'>Station …</span>"]:::core
        end

        subgraph HOST["Host PC (Windows)"]
            LTM["<span style='color:#111111'>NestrisLTM :7990</span>"]:::ltm
            MQ["<span style='color:#ffffff'>Mosquitto :1883</span>"]:::ext
            PG[("<span style='color:#ffffff'>PostgreSQL :5432<br/>local only</span>")]:::ext
        end

        TERM["<span style='color:#111111'>Registration terminal<br/>nestris-terminal + reader</span>"]:::term
        STREAM["<span style='color:#ffffff'>Stream PC<br/>OBS browser sources</span>"]:::ext
        WALL["<span style='color:#ffffff'>Hall screens<br/>/view/highscore</span>"]:::ext
        ADMIN["<span style='color:#ffffff'>Admin laptop<br/>browser</span>"]:::ext
        DECK["<span style='color:#ffffff'>Stream Deck</span>"]:::ext
    end

    S1 & S2 & S3 & S4 --- SW
    SW --- HOST
    SW --- TERM & STREAM & WALL & ADMIN
    DECK -.-> STREAM
    STREAM -- "rounds API" --> LTM

    classDef ltm fill:#f5b800,stroke:#7a5c00,color:#111,stroke-width:2px
    classDef core fill:#22d3ee,stroke:#0e7490,color:#111,stroke-width:2px
    classDef term fill:#a78bfa,stroke:#6d28d9,color:#111,stroke-width:2px
    classDef ext fill:#64748b,stroke:#334155,color:#fff,stroke-width:2px
    classDef hw fill:#1f2937,stroke:#94a3b8,color:#f8fafc,stroke-dasharray:4 3

Typical sizing. A live stream with the full playfield is about 18 KB/s per station. Even a dozen stations use only a fraction of a 100 Mbit/s network. The host's main load is the database and serving the overlays.

Topology C: Split services

Every service can be moved. PostgreSQL and Mosquitto can run on another machine, and NestrisLTM can run headless on a Linux server:

flowchart LR
    ST["<span style='color:#111111'>Stations</span>"]:::core --> MQ["<span style='color:#ffffff'>Mosquitto<br/>(server A)</span>"]:::ext
    MQ --> LTM["<span style='color:#111111'>NestrisLTM --headless<br/>(server B)</span>"]:::ltm
    LTM <--> PG[("<span style='color:#ffffff'>PostgreSQL<br/>(server C)</span>")]:::ext
    TERM["<span style='color:#111111'>Terminal</span>"]:::term --> LTM

    classDef ltm fill:#f5b800,stroke:#7a5c00,color:#111,stroke-width:2px
    classDef core fill:#22d3ee,stroke:#0e7490,color:#111,stroke-width:2px
    classDef term fill:#a78bfa,stroke:#6d28d9,color:#111,stroke-width:2px
    classDef ext fill:#64748b,stroke:#334155,color:#fff,stroke-width:2px

Untick PostgreSQL and Mosquitto in the NestrisLTM installer to use servers elsewhere, then point the [database] and [mqtt] sections of the config at them.

Hardware & software requirements

Item Requirement
OS Windows 10/11 x64 (the headless core also runs on Linux)
Database PostgreSQL 14+ (the installer can install PostgreSQL 18)
Broker Mosquitto 2.x (the installer can install 2.1.2)
Network Fixed IP on the tournament LAN; TCP 7990 and 1883 open to the local subnet
Tip A wired network connection; the screens and OBS connect to this PC
Item Requirement
Computer Small x86-64 or ARM64 PC running Debian 12 or 13
Capture USB capture stick (v4l2), or a network stream (RTSP/SRT through go2rtc)
Reader Retroverse RFID reader on USB
Console NES / Famicom running Classic Tetris; modded ROMs with hex scores are supported
Item Requirement
Computer Windows 10/11 x64 touch PC, 1920×1080 recommended (1280×800 works)
Reader Retroverse RFID reader (CP210x or CH340 USB-serial driver)
Network Reaches the host on TCP 7990
Item Requirement
Board ESP32 DevKit (ESP32-WROOM-32)
RFID RC522 module (SPI)
Display SSD1306 OLED 128×32 or 128×64 (I²C), optional
Cards MIFARE Classic 1K / 4K

Network & security checklist

  • Run the tournament on its own network. Never forward ports 7990 or 1883 to the internet.
  • The installer limits its firewall rules to the local subnet.
  • Mosquitto allows anonymous clients by default. On a shared network, create MQTT users and set them in the NestrisLTM config and in every station.
  • Create separate API tokens for the stations (stations scope) and the terminal (terminal scope).
  • Back up the database before and after every event day. The update manager also takes a backup before each update.

See Network & ports for the full port matrix.