Company updates

What changed, and what the evidence says.

Raysor publishes product and engineering milestones when there is something concrete to record. Development status is kept separate from public release status.

Current work

Active milestones.

These notes summarize current repository-backed work across the public product family and the company website.

Website v1.0 corporate redesign enters implementation

The Raysor Technologies website is moving to a unified design system, shared responsive framework, four-product catalog, consistent product pages, and versioned release manifests while preserving the existing Cloudflare Worker platform.

Company

TerritoryHub remains in release preparation

The current repository identifies TerritoryHub 5.0 Alpha as a verified core milestone. Signing, current device validation, TestFlight beta work, and App Store release preparation remain separate gates before public availability.

TerritoryHub

Territory Field develops as the focused field companion

Territory Field continues around its local-first request, receive, work, progress, and return workflow. Cloud synchronization is being layered around offline usability rather than replacing it.

Territory Field

PowerShell Principal continues as a Windows workflow platform

Principal is being organized around reusable automation, visual pipelines, runtime profiles, controlled execution, logs, artifacts, diagnostics, and a dependable Windows release lifecycle.

Principal

Deep Orbit is in validation and defect isolation

The standalone recovery product is focused on validating analyzer parity, durable recovery missions, SAFE STOP behavior, packaging, independent launch, provenance, and evidence safety before broader release.

Deep Orbit

Status discipline

A development milestone is not a release.

Raysor product pages and manifests distinguish Developer, Beta, and Stable channels. A channel is published only when an actual versioned artifact and release evidence exist.

DEVELOPER

Engineering evidence

Active product work, internal builds, source validation, and developer testing.

BETA

Controlled distribution

Signed candidate builds distributed under a defined test boundary.

STABLE

Public release

Supported artifacts with a version, notes, checksum, and official acquisition path.

Release details

Need the machine-readable version state?

The downloads system exposes product manifests for the same Developer, Beta, and Stable channels used by the website.