I had the opportunity to lead the OpenCueWeb development effort, contributing most of the OpenCueWeb implementation and writing all of the OpenCueWeb and OpenCue REST Gateway documentation.

A major milestone for the OpenCue open-source project: OpenCueWeb, the browser-based OpenCueGUI, is now fully available in the OpenCue master branch.

• OpenCue is an open-source render management system used by VFX and animation studios to schedule, monitor, and manage large-scale rendering workloads.
• OpenCueWeb is the browser-based OpenCue interface that brings OpenCueGUI functionality to the web, allowing users to monitor jobs and manage render farms without installing a desktop application.

Why OpenCueWeb

OpenCueGUI is a desktop application: it requires a local install, a graphical environment, and network access to Cuebot. OpenCueWeb removes that friction. Artists and administrators can now monitor and manage the render farm from any modern browser, on any platform, behind standard web authentication. This makes OpenCue easier to access for remote workers, easier to deploy for studios, and easier to integrate into existing web-based pipelines.

OpenCuetopia

Full job, layer, and frame monitoring and management:

• Job menu actions: pause / unpause, retry dead frames, eat dead frames, kill, unbook, request cores, set priority, subscribe to job, email artist, and job comments.
• Min/max cores dialog and batch confirmation for multi-job actions.
• Job dependency graph with an inline panel, a Cuetopia toggle, and a dependency wizard (view dependencies, drop external / internal dependencies).
• CueSubmit in the browser: a job-submission UI that brings CueSubmit-equivalent functionality to the web.
• Frame and layer management: layer property editing, frame state filter chips, human-readable age columns, per-state progress bars, and an enhanced frame log viewer.

OpenCueCommander

The administrative side of OpenCueGUI, fully represented in the browser:

• Monitor Hosts with full CueCommander parity, plus host actions: lock / unlock, reboot, tag editing, and host detail pages.
• Monitor Cue page.
• Shows page with a stats table, Show Properties, and subscriptions, plus a Create Show modal and per-show group tree with drag-to-reparent.
• Subscriptions and Subscriptions Graph pages.
• Services (Facility Service Defaults), Limits, and Allocations pages.
• Stuck Frames and Redirect pages.

Platform Features

Beyond OpenCueGUI parity, OpenCueWeb adds capabilities that a modern web application enables:

• Multi-facility support: Cuebot facility switching with server-side gateway routing and per-facility connection health.
• Authentication and authorization: Okta integration and many other options (LDAP, Google, and more), an optional group-based authorization gate, and admin gating for the full CueCommander and CueSubmit.
• Extensibility: a plugin system with a loader, settings, menu selection, and sample plugins.
• Observability: per-user usage metrics (Prometheus) with a Grafana dashboard, and an audit trail that tracks who did what, when, and with what outcome.
• Workflow: view presets, immersive mode, and split-view workspaces.
• Logs: an optional Loki backend for frame log viewing.

My Contributions

Ramon Figueiredo: 43 commits, including most of the OpenCueWeb code and all of the OpenCueWeb and REST Gateway documentation. Full list of pull requests.

Thank you to everyone who contributed with code, reviews, testing, and feedback.

OpenCueWeb Documentation

• OpenCueWeb Quick Start
• OpenCue REST Gateway Quick Start
• Deploying OpenCueWeb
• OpenCueWeb User Guide
• OpenCueWeb Reference
• OpenCueWeb Tutorial
• Concepts: CueWeb and REST Gateway
• OpenCue REST Gateway User Guide
• OpenCueWeb Development Guide
• REST Gateway Development