PUBLIC / NODE APP

Download the node app

Check the release status and checksums first, then install and bind. Only inference capacity is shared by default — never your storage.

Internal build v0.2.0 Manifest generated 2026-11-05T06:16:02Z Unsigned, internal use only; never install when the checksum is empty.

Platforms

Five platforms, one version and one checksum source (local artifacts)

  • Windows

    Available

    Windows 10/11 · x64

    Version
    0.2.0
    Architecture
    x64
    Package
    Portable one-file zip
    Size
    24.7 MB
    Signature
    Unsigned internal build

    Test build, unsigned (no EV certificate). Portable one-file zip; the desktop app needs an interactive desktop session.

    SHA256 dd028272a94b218ff8f71b1075ba7a0d419196a01fa11d3f92ba36cf07f11e24

    Windows Download

  • Linux

    Available

    glibc 2.31+ · x64 / arm64

    Version
    0.2.0
    Architecture
    x64
    Package
    Source tarball
    Size
    392 KB
    Signature
    Unsigned internal build

    Test build, unsigned. Source tarball, not a binary: unpack and run ./djb; needs Python 3.10+; the client has no third-party runtime dependencies.

    SHA256 0ec08a9f4ef22b1a0cdd7046e0c6937aaa14a337d3fdcce348838113adad3997

    Linux Download

  • macOS

    Available

    macOS 13+ · Apple Silicon first

    Version
    0.2.0
    Architecture
    arm64
    Package
    notarized-dmg
    Size
    12.3 MB
    Signature
    SHA256 52117c7eaaad6cc9e1852050f24c3dc39880bdde8c3023c0c882f50eb32fcf37

    macOS Download

    macOS · Source tarball · universal ↓

  • Machine room

    Available

    Self-hosted machine room · offline bundle

    Version
    0.2.0
    Architecture
    any
    Package
    Offline tarball
    Size
    434 KB
    Signature
    Unsigned internal build

    Machine-room offline bundle: wheel + install.sh + verify.sh + manifest.json + sha256sums; install offline with pip --no-index, no third-party runtime dependencies; no inbound port (the daemon binds 127.0.0.1:1717 only); unsigned test build.

    SHA256 7411069a2e000b96d2159eaa168d28b354f87289cfc5f618897238cdeaf6a80b

    Machine room Download

  • Official supply edition

    Pending

    Linux · x64 · source tarball

    For B2B multi-model suppliers (several upstream aggregators on one node)

    Multiple upstreams · Automatic quoting · Enablement granted server-side

    Not published yet · no installerOfficial supply bundle not published yet (source tarball + preset profile + systemd unit; available once enabled server-side).

Checksums and source

Verify each package

Every installer ships a SHA256 and a source link; the checksum comes from the same local artifacts directory as the file — copy it and verify; do not install on mismatch.

  • Windows · x64 dd028272a94b218ff8f71b1075ba7a0d419196a01fa11d3f92ba36cf07f11e24 · Unsigned internal build · 24.7 MB
  • Linux · x64 0ec08a9f4ef22b1a0cdd7046e0c6937aaa14a337d3fdcce348838113adad3997 · Unsigned internal build · 392 KB
  • macOS · arm64 52117c7eaaad6cc9e1852050f24c3dc39880bdde8c3023c0c882f50eb32fcf37 · · 12.3 MB
  • macOS · universal 6d229775acd44c8b832e84958dc6966ea71dc909ebf06b17adc26ca1cc3eb452 · Unsigned internal build · 803 KB
  • Machine room · any 7411069a2e000b96d2159eaa168d28b354f87289cfc5f618897238cdeaf6a80b · Unsigned internal build · 434 KB

After installing

Three steps

  1. 01Sign in to the web console and generate a one-time binding code on the Nodes page (10 min)
  2. 02Paste the code in the client under Account → Bind web console
  3. 03Read the receipt (dispatched / awaiting node), then set guardrails and share

Bind the web console

The client only takes work once it is bound to your account: the web console issues the code while you are signed in, and the client pastes it. Signing in is not the same as binding.

  1. 01Sign in to the web console, open the Nodes page and generate a binding code (single use, 10 minutes, shown once).
  2. 02In the client open Account → Bind web console and paste the code (or run djb auth --bind <code>).
  3. 03Back on the Nodes page, enter the node ID, client key and code, then submit.
  4. 04Read the receipt: dispatched / awaiting node (offline, effective once online). Offline does not mean unbound.
  5. 05Once bound, set budgets and guardrails on the Account page, then start sharing.

Command-line equivalentdjb auth --bind <one-time code>

The code is single-use and expires in 10 minutes; regenerate it on the Nodes page. Never enter an upstream API key in the web console — upstream keys stay on your machine.

Before you install

  • Shares inference capacity only — no storage, no silent kernel extensions or GPU driver installs.
  • Yields actively: it releases resources as soon as it detects games, calls, renders or full-screen apps.
  • The client key stays on your device; the platform does not custody, echo or download it.
  • Uninstall leaves nothing behind: local config and cache can be cleared in one step.