For those who don’t know the tool: Comp is an early node-based compositing application for Windows and Apple silicon, by Senior Lighting Artist Yuri Radaev. It combines CPU-based image processing with an optional network worker for AI-assisted segmentation and mask refinement.
A new compositor appears
Comp v0.1.1 is now available as a public alpha (GitHub) for Windows x64 and macOS arm64. The application has been developed as a personal project for more than a year and a half and is now being opened to the VFX community for testing and feedback. A Linux version is planned after the current builds reach a stable MVP.

The space occupied almost entirely by Nuke for the better part of a decade has become considerably livelier. Autograph, Silhouette, Fusion and the still very much alive Flame give artists more options than they had a few years ago. Now Comp is entering from the side. Maybe Foundry needs to up its game.
CPU compositing and a separate AI worker
Compositing operations currently run on the CPU. GPU acceleration is limited to drawing images in the viewer while the developer evaluates possible backends for GPU compositing. An optional Comp AI Worker Service runs separately from the main application and processes queued requests locally or across a network. Its current modules provide rough image segmentation using SAM3 and mask-edge refinement using MatAnyone2. The service supports CPU, CUDA and Apple MPS targets, although transferring frames across a network may cost more time than the processing itself.

Separating inference from the compositor should help isolate crashes and workload requirements. It also allows artists to continue editing while a queued AI task runs. The trade-off is a more involved setup, including separately downloaded model weights and substantial memory requirements.
This is the useful part of an alpha
This is the point at which compositors can influence the development of a tool they may eventually use, unlike stuff from the Foundry. Download it, break it, report what happened and request the feature you actually need. During an early alpha, there is at least a realistic chance that useful professional feedback will become part of the application instead of disappearing into a product-management spreadsheet.

The published roadmap starts with collecting feedback and fixing bugs before a second alpha, a Linux reference build and eventually GPU rendering. The direction and development pace are explicitly open to community input.


Test it, but keep it out of production
The developer warns that Comp is at a very early stage and may contain critical bugs and security vulnerabilities. The Windows package is also unsigned, so the operating system may block it until the user explicitly allows it to run.
If your studio has already moved its production pipeline to this alpha and everything seems fine, something is probably wrong with your studio.
https://github.com/ukmsz/Comp-releases
https://www.reddit.com/r/vfx/comments/1uwfvqh/comp_app_alpha_release/
