OpenCue is an open source render management system, licensed under Apache-2.0, that visual effects and animation productions deploy to break complex jobs into individual tasks and dispatch them across a render farm.

What it is

OpenCue is a Python render management system for visual effects and animation production. It is the render manager that Sony Pictures Imageworks used in-house on hundreds of films, and it targets the VFX Platform versions 2021 through 2024 with Python 3.6 and later. Jobs are submitted to a configurable dispatch queue that allocates the computational resources those jobs need, and the work runs on a central render farm rather than on the artist's workstation. That central-farm model is the point: artists keep working while the farm absorbs the render load.

The concrete problem it solves is the one every studio hits once shot complexity outgrows a single machine or a hand-rolled queue. A complex job has to be split into tasks, those tasks have to be matched to machines that can actually run them, and the result has to be tracked. OpenCue replaces the internal render manager a studio would otherwise build and maintain itself, and it does so with a scheduler that scales across numerous concurrent machines and across multi-facility, on-premises, cloud, and hybrid deployments.

Key capabilities

• Tagging systems allocate specific jobs to specific machine types.
• A single host can be split into many procs, each with its own reserved core and memory requirements, and there is no limit on the number of procs a job can have.
• Native multi-threading supports Katana, Prman, and Arnold.
• Integrated automated booking handles job scheduling without an external booking step.
• Docker Compose deployment ships with profiles: default for cuebot, db, flyway, and rqd; cueweb for rest-gateway and cueweb; monitoring for db-exporter, prometheus, grafana, and loki; monitoring-full for zookeeper, kafka, kafka-ui, elasticsearch, kibana, and monitoring-indexer; and all for everything.
• A sandbox environment runs a test deployment locally, with all components in separate Docker containers or Python virtual environments.
• The project holds a CII Best Practices badge.

Who uses it and how

• Visual effects and animation studios running production renders, including shops operating multi-facility or hybrid on-premises and cloud footprints.
• Render wranglers and pipeline teams that need to route specific job types to specific machine classes using tags.
• Artists and supervisors who submit work to the central farm instead of rendering locally, keeping their workstations free.
• System administrators deploying the individual OpenCue components and their dependencies, following the getting-started guides.
• Developers and newcomers running the sandbox environment for small tests, development work, and experimentation before committing to a full installation.

Getting started

The quickest path is Docker Compose: create /tmp/rqd/logs and /tmp/rqd/shots, run docker compose up -d, then check docker compose ps, adding profiles such as cueweb, monitoring, or all as needed. For a full deployment, the system administrator guides live under OpenCue Documentation - Getting Started at docs.opencue.io.

How it compares

No comparable or competing products are named in the facts provided, and no list of paid alternatives is given. On the evidence available, OpenCue stands alone in this registry.

When to use it — and when not to

A self-hoster must operate the core services themselves — cuebot, the database, flyway, and rqd at minimum — plus whichever optional stack is enabled, whether that is Prometheus, Grafana, and Loki for monitoring or the Kafka, Elasticsearch, and Kibana set in monitoring-full. This is not a sensible pick for a single artist with no render farm, or for a team that wants a managed service rather than infrastructure it runs. The README is deliberately thin on operation detail and defers to external documentation at docs.opencue.io, so anyone deploying beyond the Compose quick start should expect to work through the full installation guides first.

# Prerequisites
mkdir -p /tmp/rqd/logs /tmp/rqd/shots

# Start core services (db, flyway, cuebot, rqd)
docker compose up -d

# Check status
docker compose ps

# Enable Web UI and monitoring
docker compose --profile cueweb --profile monitoring up -d

# Enable all services
docker compose --profile all up -d

# Stop all profiles (recommended to ensure everything is brought down)
docker compose --profile all down