Installation
Install, update, uninstall, and troubleshoot Raydo Desktop.
Use this section before your first launch, when moving to a new device, or when deciding between official, community, and portable builds.
Install path first, features second
Raydo should start with a clear install path. Runtime payloads, providers, and portable builds matter only after the app can launch.
macOS install
Install the signed app, handle permissions, and keep Raydo updated.
Windows install
Install Raydo on Windows and understand current packaging expectations.
Updates
How Raydo updates and what to do when an update fails.
Portable version
When to use portable builds and what they include.
Install decision
Use this path for the standard Raydo Desktop experience. It is the right default for most users because updates, signatures, and runtime expectations are handled as part of the normal app package.
Use this path when you want a local-first build that does not require the commercial runtime payload. It should still feel like Raydo as a product, but with fewer managed services.
Use this path for controlled environments, offline handoff, or machines where installation is restricted. Keep the package together and use the build that matches the target platform.
Common setup checks
- Raydo should launch before you configure providers or workflows.
- The app should be allowed to open local files and previews when needed.
- Network access may be required for managed providers, updates, and Raydo Link features.
- Community Core should not require Raydo Cloud login for local use.