Desktop app · Windows · v1.0.0-beta.5

.hub.shock

The .shock.LAB’s local backbone. The web apps are the view — this is the engine room: one install runs every background server they need (faces, RAW, file store, delivery relay) and bridges hosted cull / tag / publish back to your machine’s GPU, disks and originals.

Download for Windows (.exe) ↓ SHA-256 checksum Installer + guide PDF (.zip) ↓

Windows 10/11, 64-bit · per-user install, no admin needed · macOS build planned.
Beta honesty: this build is not yet code-signed (certificate purchase pending), so SmartScreen will warn — verify the download against the published SHA-256 before running it. It never updates itself silently.

🔒 Sign-in token sealed in the OS vault — used, never shown🖊 Only the Hub writes to disk — gated, logged, undoable📦 Servers provision from your workspace — nothing fetched & executed from the net🗑 Uninstall never touches your RAW or session files

Desktop app · Windows · v1.0.0-beta.5

What one install actually does

one install, all servers

The manifest installs everything

Asset Service (file store), the Dotshock Engine (ArcFace faces, person re-ID backend, publish FTP relay), PHP + database runtimes, AI models — declared in one versioned manifest, installed in one checkpointed pass. If step N fails it stops in a known state and resumes from N, never a silent half-install.

the bridge

Hosted apps, local power

tag.shock on the web reaches your local Engine for real 512-d face embeddings; publish.shock delivers via your machine’s FTP relay. All through one local port — no cloud middleman touches your files.

autonomy

It tells you when you can leave

Every job is classified: needs your machine (local originals, FTP) or server-side. The moment the last machine-bound job finishes it announces it — shut the lid, server work continues.

in development

Serve your portfolio originals

Planned: portfolio.dotshock.ai shows previews; on a sale your machine serves the full original from disk — pushed up once and cached, so later delivery works even with the machine off. Not in this beta; listed so the roadmap stays honest.

Desktop app · Windows · v1.0.0-beta.5

Install

Download the installer above and check it: certutil -hashfile DotshockHubSetup-1.0.0-beta.5.exe SHA256 must match the published checksum.
Run it — per-user install, no admin prompt. SmartScreen will warn because the beta is unsigned: More info → Run anyway, only if the checksum matched.
A ~5-minute first run: sign in once with your dotshock.ai account (same account as the web), point it at your dotshock workspace, review the server manifest, add your watch folders.
Click Install all under Services — the manifest provisions every server with a live progress list.
Keep working in the web apps. They now find the local servers automatically; the tray icon opens the dashboard.

What this beta expects: from beta.5 the Dotshock Engine (faces, person re-ID, the publish relay) installs with no workspace checkout — the Hub downloads it from this site into its own data folder and installs its Python stack there. That is the one server the web apps actually reach, so tag.shock and cull.shock work on a fresh machine. The Asset Service still needs a dotshock workspace and says so in the install list rather than half-installing; point the Hub at a checkout in Settings if you need it.

Only the Hub writes to disk. Apps decide, it writes: one .shock-session.json knowledge file per shoot folder, only in folders you approved, every write logged with a backup ring and an Undo. Your RAW masters are never modified.