Blender on the right computer
Render with CPU-only work or an owned GPU lease. Project Python remains a separate receiving-computer choice.
Windows · Subscription access
Send a complete Blender, Android or Windows project to another computer you control, use the tools installed there and receive a verified result ZIP.
Free download on the Microsoft Store; access is $9.99 a month, billed by Microsoft
Choose a project folder, a small reviewed recipe and a ready computer. rBroker transfers the project directly, runs only a task type that computer enabled, and checks the declared results before returning them.
Render with CPU-only work or an owned GPU lease. Project Python remains a separate receiving-computer choice.
Build with the checked-in Gradle wrapper, use one named emulator, explicitly enable one local physical ADB device, or separately enable a direct-only ASL Tunnel Android target.
Build solutions and projects, including Store-ready MSIX candidates, with the receiver's own installed tools and signing identity.
Each receiving computer detects Blender, Android SDK and Java, and MSBuild, then tells its owner what still needs installation or selection.
Encrypted resumable transfer keeps project bytes out of the coordinator. Only declared result paths return in a digest-verified ZIP.
Tool paths, device access, GPU configuration and signing identity stay local. A transferred task cannot provide a shell, password, key or executable path.
What you need. Install rBroker on the computers you want to use. A receiving computer also needs the application for its job: Blender; Android SDK, Java and the project's Gradle wrapper; or Visual Studio Build Tools. The 49-section guide and setup are available in 14 languages.
The upcoming picture setup detects an installed ASL ImageLab library and its NVIDIA CUDA or AMD Vulkan engine. ImageLab remains separately usable. The receiver must have the models installed, local image consent and permission for the named sender. This integration is being tested and is not yet included in the published Store build.
The receiving owner decides whether Blender project Python is allowed. CPU work does not require a compatible GPU. GPU work reserves an owned local lease; rBroker does not pool graphics memory or split one scene across arbitrary machines.
Physical-device access is off by default and accepts only typed APK installation steps on one confirmed non-emulator device. Local physical ADB and ASL Tunnel are independent choices: enabling one never authorizes the other. The Tunnel option starts the installed licensed helper directly, accepts only its versioned direct-only loopback listener, and verifies the saved Android-device serial before every job. It has no relay fallback or arbitrary device shell.
A Windows project can produce normal, MSIX or Store-ready output using only the receiving computer's installed certificate identity. A successful local package is a candidate; it is not a Partner Center submission, Microsoft certification, approval or public release.
Joining a fleet does not authorize execution. The receiving owner enables the exact job types and local limits, and the fleet manager separately grants the named dispatcher. Nothing builds, launches an emulator, connects ADB or starts a project merely because the app opened or setup was saved.
The standalone app is available on Microsoft Store. Master Suite includes the same rBroker workspace alongside AI Hub and PC Steward. Both forms keep the same per-computer tools, permissions and identity boundaries.
Read the complete two-computer setup · Compare ASL apps · Reviewer resources