ASL Render or run Python
Use the Blender installed on the receiving computer. Choose CPU-only work, or request GPU memory through that computer’s own rBroker lease. Blender Python is a separate local permission and starts off.
Your computers · Your tools · Your permission
Send the project.
Use the right machine.
ASL rBroker moves complete Blender, Android and Windows projects between computers you control, runs a reviewed job type with the receiving computer’s own tools, and returns a verified result. It also coordinates owned GPU leases, real CPU workers and private fleet reporting.
Version 1.5.2 keeps local physical ADB and the direct-only ASL Tunnel Android target as independent receiver choices, with typed project transfer, setup and the 49-section guide in 14 languages. Microsoft Store submission, certification and public availability are separate stages; the Store page shows the version currently available to install.
Built-in project jobs
One transfer flow, three development toolchains.
Build, emulate or use a device
Use the receiving computer’s JDK, Android SDK and project Gradle wrapper. A named emulator is optional. Local physical ADB and direct-only ASL Tunnel Android each have their own checkbox; enabling one never authorizes the other.
Build MSIX and Store candidates
Use local MSBuild with a solution, project or packaging project. Store-ready MSIX output is separately enabled. A certificate thumbprint is selected locally; signing identity and secrets never travel with the project.
Set up once on each computer
rBroker tells you
what is missing.
Open Host & setup → Project tools on every computer that should receive work. Detect installed tools, review the paths and enable only the capabilities you want. The readiness report explains missing Blender, Java, Android SDK, emulator, ADB, MSBuild or GPU-broker requirements in plain language.
An AI assistant such as Claude or ChatGPT can use rBroker’s local MCP tools to read readiness, guide the same setup on both ends and send a reviewed project after you confirm it. The assistant gets the same consent boundaries as the desktop app.
What to install
Every computer: rBroker from Microsoft Store. A receiving computer additionally needs only the development tools for the jobs it accepts.
Blender: Blender for Windows. A supported GPU and local broker configuration are needed only for GPU-mode recipes.
Android: a JDK, Android SDK/platform-tools and a Gradle wrapper in the project. Install an emulator and AVD only for emulator jobs.
Windows/MSIX: Visual Studio 2022 or Build Tools with the workloads and packaging tools required by your project.
Private fleet, clear boundaries
Useful across two PCs or a whole fleet.
CPU, GPU and project work stay distinct
System RAM, physical GPU memory, owned GPU leases and Parallel worker slots are accounted for separately. CPU-only Blender does not require a GPU. Android and Windows builds do not acquire GPU leases. Existing local brokers remain authoritative.
Nothing is enabled by installation
First launch starts no services, opens no firewall ports and shares no computer data. Joining, reporting, accepting a dispatcher and enabling each handler are separate choices. Busy accepted work is not silently discarded during shutdown or upgrade.
In your language
App and full help in 14 languages.
English, Polish, Spanish, Chinese (Simplified), Tagalog, Vietnamese, Arabic with right-to-left layout, French, Korean, Russian, Portuguese (Brazil), Haitian Creole, German and Hindi. rBroker starts in a supported Windows display language, and you can switch from the header at any time.