Voyager Cloud

The fastest way for your agent to render 3D.

CLI & MCP for agents to run Blender or Vork workloads in the cloud. Lease GPUs by the second, preinstalled with Blender or Vork, an asset library and the tooling to render fast. It’s your render farm on tap.

Give this to your agent
Install and set up the official Voyager CLI by following https://voyager.so/cloud/INSTALL.md to render 3D with Blender or Vork on Voyager cloud GPUs. After setup, continue my existing task if I gave one. Otherwise, present the guide's four starter choices verbatim.
Assembly: a miniature world built from Voyager asset library models and rendered in Blender on Voyager Cloud.

A 3D workstation, ready when it starts

Every machine is a creative GPU workstation with nothing to install. Graphics GPUs with ray tracing render your frames, from an L4 for drafts to RTX PRO 6000 for finals.

  • Blender

    Cycles on the GPU and EEVEE, headless, with the render presets and scene templates in the voyager cloud guide.

  • Vork

    Voyager’s headless 3D and VFX engine for agents. Shaders come compiled, and long renders split across the GPUs of a multi-GPU machine.

  • The splat engine

    Voyager’s Gaussian splat engine, for scenes made from video.

  • The toolchain

    PyTorch and CUDA, FFmpeg with hardware encoding, headless Vulkan and EGL, Node.js and Python.

  • The core asset library

    Installed on the machine, so the common models, materials and HDRIs are there before anything downloads.

A 3D library your agent can search

Thousands of free 3D models, materials and HDRIs, browsable by category and mostly CC0 with credits, plus Voyager Packs: curated kits made to work together. Your agent searches the library, places what it picks in the project and pulls it straight onto the machine.

  • Garden and Woodland Plants

    Trees, shrubs, flowers and potted plants.

  • Modern Scandinavian Interior

    Furniture and props, plus a modular room kit.

  • Orbital Station Interior Kit

    A modular sci-fi station interior.

  • assets search

    Ranked, scored matches, filtered by kind, licence, triangle budget and texture resolution, with a contact sheet of previews. No sign-in needed.

  • assets show

    Details, licence and credit, scale and pivot.

  • assets add

    Places a model’s glTF and textures, a material’s maps or an HDRI’s EXR in the project, and records it in voyager-assets.lock.json.

  • assets sync

    Fetches every locked asset on the machine, at the same versions, checked.

Terminal
voyager cloud assets search "fir sapling" --kind model --max-tris 50000 --sheet hits.jpg
voyager cloud assets show vy.model.fir-sapling
voyager cloud assets add vy.model.fir-sapling vy.hdri.studio-small-09 --project scene --lock-only
voyager cloud exec --cwd scene <machine> -- voyager-cloud assets sync

In the Voyager desktop app the same commands are voyager assets …, and Voyager’s own agent can use them directly.

Assets Voyager makes for the library, Voyager Packs included, are under the Voyager Assets Licence: use them in your own projects, commercially too, but don’t resell or redistribute the asset files on their own or use them to train generative AI models. Assets from public-domain (CC0) sources keep their CC0 licence, and every asset’s credit line is shown with it.

Pay for rendering, not for waiting

  • Billed by the second

    A machine bills only while it runs. It pauses by itself after 15 minutes idle, a lease can carry a budget cap, and voyager cloud spend shows what each machine or tag cost over any time range.

  • Assets download on the machine

    Your agent picks assets on your computer and records them in a lock file, and the machine downloads them itself. Nothing large goes up from your laptop.

  • One frame range, many machines

    voyager cloud farm splits a frame range across machines started from one snapshot. Each takes the next chunk from a shared queue, a failed chunk is retried on another machine, and each chunk’s outputs are checked and pulled as it finishes.

  • Set up once with snapshots

    Build the scene and its assets on one machine, snapshot it, and start as many identical machines from that snapshot as you need.

  • Safe for agents

    A lease retried with the same request id never leases twice. At your machine limit it waits and says who holds the machines, and a farm releases every machine it leased when it ends.

Install the CLI

The agent can do this itself. To set it up by hand, install voyager and sign in; login opens your browser.

macOS / Linux Terminal
Terminal
curl -fsSL https://voyager.so/cli/install.sh | sh
voyager login
Windows PowerShell
PowerShell
irm https://voyager.so/cli/install.ps1 | iex
voyager login

Presets

  • Render

    render

    RTX PRO 6000, 96 GB VRAM

    Final renders and heavy scenes. Runs vork.

    Live price on the dashboard

  • Render lite

    render-lite

    L4, 24 GB VRAM

    Cheaper drafts and previews. Runs vork.

    Live price on the dashboard

  • Compute

    compute

    H100, 80 GB VRAM

    CUDA, simulation and training. No ray tracing, so it can’t run vork.

    Live price on the dashboard

Billed by the second. A machine bills until it is released or paused, and idle machines pause by themselves after 15 minutes. Compute (H100) has no ray tracing: use it for CUDA, simulation and training. voyager cloud presets lists every preset and its price.

Or use MCP

The MCP server has the machine steps as tools. Add it to any agent that supports remote MCP servers:

Server URL

MCP URL
https://mcp.voyager.so/mcp/machines

Claude Code

Terminal
claude mcp add --transport http voyager-cloud-gpus https://mcp.voyager.so/mcp/machines

Codex

Terminal
codex mcp add voyager-cloud-gpus --url https://mcp.voyager.so/mcp/machines
codex mcp login voyager-cloud-gpus