Cross Platform Flow

PREHEAT · DOWNLOAD LOCKED

Public Beta status and download gates

As of August 30, 2026, CrossFlow 1.0 RC3 has an immutable candidate and dual-platform automated builds, but remains in preheat. There is no public installer and no hidden download route.

Last audited: 2026-08-30
Public release: Not released
Candidate: v1.0.0-rc.3
Next: same-RC physical use and trusted signing

  1. 01 / Current status
  2. 02 / Download center
  3. 03 / Systems and permissions
  4. 04 / Known limitations
  5. 05 / Privacy and license
  6. 06 / Feedback and security
  7. 07 / Changelog

01 / Release authority

Four gates must close on the same candidate.

Current decision: preheat only

Candidate code, a passing automated test, or one private physical demo cannot open downloads. If the candidate bytes change, every build-sensitive check must be accepted again.

Scope locked

Launch systems

One Apple Silicon Mac on macOS 15+ paired with Windows 11 x64. Intel Mac, Windows ARM, and Linux are outside the first public-Beta scope.

Candidate frozen

RC3 automated build

RC3 binds both platform candidate bytes and passes automated builds. Complete physical matrices for input, Portals, clipboard, files, and safe release remain open.

Not passed

Five working days

The final candidate has not completed five working days without replacing the binary or relying on undocumented workarounds.

Not passed

Trusted installation

There is no Developer ID signed, notarized, and stapled macOS image or trusted-signed Windows MSIX/App Installer yet.

02 / Download center

The download center exists. The packages remain locked.

macOS

Apple Silicon · macOS 15+

Public release: Not released
Installer: Unavailable
Size: Unavailable
SHA-256: Unavailable
Signature: Release gate not passed

Windows

Windows 11 · x64

Public release: Not released
Installer: Unavailable
Size: Unavailable
SHA-256: Unavailable
Signature: Release gate not passed

Checking the official Beta release record. Downloads remain locked until verification succeeds.

Do not seek development packages from third parties

RC3 is a frozen automated candidate, but it has not completed trusted signing, the same-candidate physical matrix, or five working days of acceptance. It is not yet a publicly distributable Beta installer.

The planned public-Beta policy is direct download without mandatory registration; any optional update subscription must require separate consent. This is a release policy, not an announcement that download or subscription systems are live.

03 / Requirements and permissions

The permission guide must survive deny-and-recover tests.

macOS release target

Accessibility and local network

The release will explain why input Accessibility and local-network access are needed. Initial denial, recovery in Settings, later revocation, restart, and stale authorization must fail safely without swallowing local input.

Windows release target

Firewall and package identity

The MSIX/App Installer publisher, version, update URI, and capabilities must be frozen. Firewall denial, network loss, upgrade, and uninstall will be rerun on a clean Windows 11 x64 system.

  • Network loss, quit, or permission revocation must release every remote key and pointer button.
  • Emergency pause must return local control immediately and cannot be intercepted by the peer.
  • After reauthorization, the UI must distinguish actual input readiness from pairing alone.

04 / Known limitations

These items block release or remain outside current product claims.

  • Keyboard mapping: per-peer profiles and Caps Lock/Shift IME actions still have an asymmetric physical observation.
  • Topology: free-form Portals have candidate evidence, but dual-visible editing and sustained physical crossing are not accepted.
  • Clipboard: private candidates have partial observations; Windows history selection, pause races, and one-RC acceptance remain open.
  • Files and history: Transfer Shelf, file clipboard, and clipboard history are in the RC3 candidate scope; complete physical transfer, pause, resume, and responsiveness acceptance remains open.
  • Shared folder: copy/add/update and conflict copies are candidates; V1 does not propagate deletion or infer rename, and dual-host plus three-device gates remain open.
  • Native drag: native cross-screen file drag is explicitly outside 1.0. Files use clipboard, Transfer Shelf, shared folders, and OS send actions.
  • Stability and release: the five-day run, emergency pause, and disconnect release must be repeated on the release RC.

05 / Privacy and license

Collect less, and state the license plainly.

License

Currently proprietary

CrossFlow and its source are not open source. Personal covers one account and up to three devices, with one 14-day card-free trial starting on first-device activation. Public pricing will be whatever the future Live checkout displays.

Website privacy

No client analytics SDK

The static product site contains no client analytics SDK, and domain rules disable Zaraz and RUM. The host may still create standard request logs; future download counts are planned as channel, platform, version, and aggregate count only.

There is no downloadable app today, so there is no public-Beta application telemetry. Any future app behavior collection, crash reporting, or update subscription must be enumerated in the privacy notice and separated from download consent.

06 / Feedback and security

Reproduce ordinary issues in public. Report security issues privately.

Use the public repository for compatibility reports, bugs, and feature requests. Include OS version, CrossFlow version, direction, input hardware, and minimal steps—never secrets, LAN addresses, or private clipboard data.

Open feedback

Do not open a public issue for a security, privacy, or abuse-enabling problem. Use GitHub private vulnerability reporting. The staffed security contact path will also be verified before downloads open.

07 / Status changelog

The public page records only auditable changes.

  • 2026-08-30: recorded the immutable v1.0.0-rc.3 candidate and dual-platform automated builds, then refreshed V1, account, and Sandbox commerce status. Physical use, five working days, trusted signing, and downloads remain closed.
  • 2026-08-24: added the preheat download center, locked launch systems, release gates, and known limitations.
  • Next entry: only when gate state, public version, installation trust, or the feedback path materially changes.