Beeble Canvas

Canvas arrives as a node based AI compositor plus automation, with SwitchX and SwitchLight under the hood and an API for pipeline integration.
A digital interface displaying a workflow for video editing. On the left, three clips of a woman with long, wavy hair in a blue top against two different backgrounds are shown. The center section highlights a frame selector and an image generator. The right section features a switch interface, demonstrating how to change backgrounds.

For those who don’t know the tool: Beeble builds AI relighting and video transformation tools for VFX, post, and virtual production, and Canvas is its very new node based environment that wires SwitchX and SwitchLight into repeatable shot workflows.

A node graph, but for AI outputs you can wrangle

Canvas lands as a node based AI compositing environment aimed at complex workflows across VFX, post, and virtual production. The pitch is straightforward: put AI video models, compositing utilities, and workflow automation into one visual system so teams can iterate across multiple shots without rebuilding the same logic over and over.

In practical terms, it targets the part of the job where you already juggle plates, masks, reference stills, and multiple look directions, then repeat that dance across a sequence.

An intricate visual flowchart containing various thumbnails representing different video editing stages. The grid showcases sections labeled 'Source', 'Matte', 'HD frame', 'Composite', 'Keyframer', and 'Red image', connected by lines to demonstrate relationships and transitions in the editing process.

What is actually in the box

Canvas presents itself as a node graph workflow editor for final render, with a catalog grouped into Input, AI Tools, Edit, and Utility. Input supports text prompts plus image files in PNG, JPEG, or WebP, and video files in MP4 or MOV. In other words, it starts where most editorial and comp workflows already start: media in, decisions next.

The AI Tools section includes a node for SwitchX, the same model as the standalone product, with source and alpha handled as video inputs. It also includes an LLM node that can generate files from a prompt with up to four media inputs, plus image generation and video generation nodes that can route to external models. For rotoscoping style work, Canvas includes a Video Matte node that outputs an alpha matte plus RGBA, with an automatic mode and an interactive selection mode, plus options aimed at general footage and green screen keys.

On the classic comp side, the Edit nodes cover the expected utility moves: extract a frame, trim, crop, resize, curves, invert, flip, and morphology operations like erode and dilate. Utility nodes cover housekeeping: sticky notes, routing for cleaner graphs, a viewer, side by side compare, and export. It’s not fully Nuke yet, but…

That combination matters because it lets artists keep the media prep and look development steps next to the model calls, instead of bouncing between separate tools and hoping filenames stay honest.

An interface shows a video editing tool with a still image of two people inside a car. The dashboard is illuminated and the scene appears dynamic, capturing a moment of interaction. Background features a green canvas with multiple layered paths leading to the video player.

Relighting and PBR passes, now wired into the graph

The system includes access to SwitchLight for generating physically based rendering passes. In the Canvas node catalog, the VFX Pass Generator extracts PBR material maps including BaseColor, Normal, Depth, Roughness, Specular, and Metallic from image or video using SwitchLight 3.0.

That puts relgihting adjacent tasks into the same graph where you also assemble mattes, feed references, and generate variations. It also matches the stated intent of supporting controllable, iterative pipelines across multiple shots, not one off experiments.

A dark-themed digital interface displays interconnected nodes and images related to a project workflow. On the left, thumbnail images represent different stages, leading to larger panels with varying visuals, including landscapes and architectural elements, showing a structured process.

Automation, batches, and the part everyone really wants

Canvas claims to be built around repeatability: build workflows once, apply them to shot sequences, and automate iteration without rebuilding node logic shot by shot. It also calls out batch processing and maintaining scene consistency across projects.

Those claims describe the correct pain point. Anyone who has ever reconnected the same five nodes fifty times will understand why a programmable layer matters. Still, treat the automation story like any new tool claim: test it in your own pipeline with your own edge cases before you bet any delivery on it.

The API angle: SwitchX in your pipeline, with pricing details

Alongside Canvas, the SwitchX API is positioned for studios and developers who want to integrate video transformation and relighting capabilities directly into custom pipelines and software environments.

The developer portal offers a REST style workflow with uploads, job creation, and polling, and it explicitly supports 720p and 1080p output. It also has pay as you go credits in US Dollar, and pricing can start at $0.10 per generation. That pricing applies to the API offering as described there, while Canvas pricing is not specified, since it is part of Bebble Online.

Availability, media assets, and credits

Canvas is available now via the Beeble platform, with a launch video hosted on YouTube (The Video we embedded above…) .

The boring but necessary reminder

New tools and innovations should be tested before use in production, especially when they touch shot consistency, automation, and delivery formats. Run a small sequence through, break it on purpose, and see how it fails before you trust it on a deadline.

https://docs.beeble.ai/beeble/canvas
https://docs.beeble.ai/beeble/overview