jasperx · install

Install JasperNode

Linux (native)

Install · Linux
curl -sSL https://dl2.jasperx.io/jn/install.sh | sudo -E bash -

Prefer to read before you run? View the install script. Fair enough; we'd do the same.

macOS / Windows (Docker)

Install · macOS
curl -fsSL https://dl2.jasperx.io/jn/docker.sh | bash
Install · Windows (PowerShell)
irm https://dl2.jasperx.io/jn/docker.ps1 | iex

Then open http://localhost:9009 and claim the node.

First run at localhost:9009 · claim the node
The JasperNode first-run setup screen in the browser: name the node and complete setup

First run at localhost:9009 · claim the node

Requirements

Linux (production)Windows (development)
Architecture ARM64 (e.g. Quad-Core Cortex-A53) or x86_64x86_64 (Intel Core i3/i5 or newer Atom/Celeron)
Operating system Debian-based Linux (e.g. Ubuntu; Debian 12 recommended)Windows 10/11 Pro or Windows 10 IoT
Memory 2 GB minimum (4 GB recommended)8 GB minimum (16 GB recommended)
Storage 16 GB eMMC or industrial SSD minimum64 GB industrial SSD minimum
Connectivity 2x 10/100/1000 Mbps Ethernet ports2x 10/100/1000 Mbps Ethernet ports

Updates

A native Linux node updates itself in place; a Docker node updates when you pull the newer image. How updates work.

Deployed logic executes on the node and keeps running without the cloud. What an update can change: platform features, the AI's behaviour, and interfaces between releases. What we don't do: silently change deployed logic, or push a change to a running node without the update flow.

Handing this to your integrator or your team to run with? This page and the docs are everything they need; there's no account of yours they have to go through.