JasperX

jasperx · install

Install JasperNode

Linux (native)

Install · Linux · beta channel
curl -sSL https://dl2.jasperx.io/jn/install.sh | JN_CHANNEL=beta 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 · beta channel
docker run -d --name jaspernode -p 9009:9009 \ -v jaspernode-data:/var/lib/jaspernode \ jaspernode/jaspernode:latest-beta
Install · Windows (PowerShell) · beta channel
docker run -d --name jaspernode -p 9009:9009 ` -v jaspernode-data:/var/lib/jaspernode ` jaspernode/jaspernode:latest-beta

Then open http://localhost:9009 and 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

Channels

beta
What you just installed. Open to everyone, updated frequently, features land here first. Your deployed logic runs locally either way; "beta" describes the platform and AI features, not whether your pump keeps pumping.
stable
For production-critical control. Fewer releases, longer soak time, and getting on it starts with an email to [email protected] telling us what it's running. We gate the stable channel on purpose: we want to know what "stable" has to mean for your site before we promise it.

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.

What beta means here, exactly

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