Know your download.

The official installer

Downloads come from the public Cassian release repository on GitHub. The home page checks the exact v8.0.0 tag and its file metadata before enabling either download button. That tag may be marked as a public beta; drafts and other versions are rejected.

If the release has not been published or its files cannot be verified, the buttons stay disabled. Once the verified files are published, opening the page or choosing “Check again” enables the download without a website update.

Check the downloaded file

The optional SHA-256 check confirms that the file on your computer matches the published installer. Open PowerShell in your Downloads folder and run:

Compare the complete result with the installer SHA-256 shown in the download section. Every character should match. Use SHA-256 for integrity checks; the MD5 manifest is included only for legacy comparisons.

Windows publisher signing

Publisher signing is still pending. A matching checksum identifies the file’s bytes; it does not replace a publisher signature or establish that software is safe. Read the matching release report for its actual acceptance results and any unfinished checks.

What the website verifies

The download check validates the repository and release URL, version agreement, uploaded file state, file names, size limits and GitHub-reported SHA-256 digests. Missing, duplicate or unexpected metadata leaves the download disabled.

The release must include the installer, matching portable and source ZIPs, SHA256SUMS.txt, MD5SUMS.txt, RELEASE-READINESS.json and Cassian-Build.json. The separate legacy stable-release validator continues to reject all prereleases.

The website and app are separate

The website does not install or run Cassian, control the app, read your sessions, or provide an automatic updater. You choose to download the installer and run it in Windows.

The site uses local scripts and artwork, a restrictive content policy, bounded release responses and fixed external destinations. It has no visitor upload service, account database, payment form or embedded credentials.

Hosting limits

GitHub Pages does not apply the custom HTTP headers used by the local preview. Framing and device-permission headers are not claimed as deployed protections. Account-level release immutability and publisher access controls require separate verification.

Report a concern

Use the issue tracker for non-sensitive reports. For private support, email support@min10studios.com. Keep passwords and credentials out of reports.