Back to documentation

Secure V-Ray render manager

What to look for in a secure local V-Ray queue manager: local operation, signed builds, and clear privacy boundaries.

Who this is for
Users evaluating safety before installing a render tool.
Best fit
Use this checklist before adding any render queue tool to a production workstation.

Workflow

  1. Install from official sources only: the Microsoft Store listing on Windows, or the signed and notarized DMG from the GitHub releases page on macOS.
  2. Confirm the publisher before installing: Adrien LEJEUNE on the Microsoft Store, and the official V-Raykally GitHub repository for macOS releases.
  3. Review the privacy policy and confirm that scenes, paths, outputs, and logs stay on the machine.
  4. Keep V-Ray Standalone and the queue manager updated from their official channels.
  5. Treat the render workstation like any production machine: a local queue needs no inbound network connections.

Where it fits

V-Raykally runs locally, and its builds are code-signed: notarized on macOS and delivered through the Microsoft Store on Windows.

  • Apple notarized
  • Microsoft Store delivery
  • Local-first privacy statement

This is for local V-Ray Standalone queues. It does not provide worker provisioning, central asset sync, accounting, cloud bursting, or facility-wide scheduling.

FAQ

What makes a V-Ray render manager secure?

For a local queue, security starts with keeping files local, using signed and verified app builds, and making network behavior explicit.

Is this a cloud render farm?

No. V-Raykally is designed for local V-Ray Standalone queues on the artist workstation or a local render machine.

What kind of V-Ray files does this workflow target?

The workflow targets V-Ray Standalone scene files such as .vrscene and .vrs, with output and frame options handled around the local V-Ray executable.

Sources