← Back to Discover

ASL rBroker

ASL rBroker is a paid Windows app that runs Blender, Android and Windows project jobs on another computer you control and returns a verified result ZIP.

Workflow automation
Visit website ↗

What it does

Choose a project folder, a small reviewed recipe and a ready computer. rBroker transfers the project directly to that computer. The receiving computer runs only a task type that its owner enabled. Encrypted resumable transfer keeps project bytes out of the coordinator. Only declared result paths return, in a digest-verified ZIP. Install rBroker on each computer 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. Each receiving computer detects Blender, Android SDK and Java, and MSBuild, and tells its owner what still needs installation or selection. Joining a fleet does not authorize execution, because the fleet manager separately grants the named dispatcher.

Capabilities

  • Blender jobs can render with CPU-only work or an owned GPU lease. GPU work reserves an owned local lease, and rBroker does not pool graphics memory or split one scene across arbitrary machines.
  • Android builds use the checked-in Gradle wrapper. They can use one named emulator, one explicitly enabled local physical ADB device, or a separately enabled direct-only ASL Tunnel Android target.
  • Physical-device access is off by default and accepts only typed APK installation steps on one confirmed non-emulator device.
  • Windows builds cover solutions and projects, including Store-ready MSIX candidates, using the receiver's own installed tools and signing identity. A successful local package is a candidate, not a Partner Center submission, Microsoft certification, approval or public release.
  • Tool paths, device access, GPU configuration and signing identity stay local. A transferred task cannot provide a shell, password, key or executable path.

When to use it

  • You need to send a complete Blender, Android or Windows project to another computer you control.
  • You want a project processed with the tools already installed on another computer.
  • You need a Windows project packaged as normal, MSIX or Store-ready output using the receiving computer's installed certificate identity.