Windows control center

One trusted front door for Raysor software.

Raysor Hub is the Windows product center for discovery, installation, updates, repair, recovery, Developer builds, health evidence, and existing-machine migration.

How it works

01

Install once

Start with Raysor Hub instead of collecting unrelated installer links.

02

Trust before mutation

Acquisition, package trust, health checks, side-by-side versions, and rollback are separate failure boundaries.

03

Developer without chaos

Developer Mode can build explicit branches while Stable remains isolated and fail-closed.

Lifecycle

Hub decides what. The updater decides how.

Discover

Explore the Raysor library.

Organizer, RAYSOR AI, TerritoryHub, StriveLoop, Tactical Tower, and future managed products share one lifecycle authority.

Verify

Downloaded does not mean trusted.

Stable candidates require signed catalog evidence, exact release identity, SHA-256, architecture, package kind, and publisher policy before installation authorization.

Recover

Known-good stays known-good.

Candidates must pass health before activation. Failed candidates preserve or restore the prior known-good version.

Existing machines

No ceremonial uninstall required.

Upgrade Hub first. Hub can inventory declared Raysor installations, verify their identity, preserve external data boundaries, adopt them as legacy baselines, and migrate lifecycle control one product at a time.

Privacy

Software health, not private content.

Platform telemetry is designed around versions, crashes, health, lifecycle failures, typed errors, and correlation IDs. Product content and user-created data are outside the default telemetry contract.

Requirements

Production users should not need a developer workstation.

No Git

Production acquisition is native to Hub.

No PowerShell installer

PowerShell remains a Developer/CI tool, not a consumer requirement.

No SDK

Users receive built packages rather than source checkouts.

FAQ

Important boundaries.

Stable

Why might download be unavailable?

Public distribution fails closed until an owner-promoted release has an approved HTTPS host, version, architecture, and exact SHA-256. Workflow artifacts are not silently substituted.

Developer

Does Developer Mode disable security?

No. It allows unfinished Raysor builds under explicit developer control while keeping package and data boundaries intact.

Data

Will updates erase my data?

Binary lifecycle and user-data lifecycle are intentionally separate. Product data remains outside disposable version directories.