Hey PH, I'm Albert. I built ArcBrush in C++ over the last several months.

ArcBrush is a full image editor: masking, compositing, paint, roto, text, warps, filters, keyers, color grading, AI, exporters. 75 nodes total. What makes it different is that every operation is a node in a graph instead of a layer on a stack, and every operation is non-destructive. Paint strokes, masks, warps, filters, the lot. Every parameter stays tunable, and when you change one, only the affected nodes re-evaluate.

Why I built it: if you've ever exported the same thing twice, this is for you. Layer stacks aren't reusable. Flatten once and the flexibility is gone. A graph stays reusable indefinitely, and the moment that clicks, the tool stops feeling like an experiment and starts feeling like an actual editor.

Three things that become trivial once the work lives in a graph:

Non-destructive masked compositing: remove a background (by hand or with AI), refine the edge, drop onto a new backdrop, color grade the whole thing. Every step stays tunable without redoing the rest.
Define a named palette and produce N recolored variants from one graph run, with every highlight and shadow preserved. (200 icons in 12 tiers is one click, not a week.)
Save the whole workflow as a portable .arcb file and hand it to a teammate on the other OS.

AI is 4 nodes. Background removal, text to image, image edit, 4x upscale. They sit in the graph next to your masks, warps, and color grades. Credits, no subscription, no expiry. 10 free on signup.

The app is free; the 4 AI nodes are the only paid part.

Getting Started Tutorial Video

I'd love honest feedback on three things:

How does the node paradigm feel the first time you open it?
Which nodes do you reach for first?
What's in your current workflow that you wish was a node here?

Happy to answer anything in the comments.