Open Source Alternatives to Adobe Apps: Verify First
One documented open source studio, a feature list that overlaps with part of a paid creative suite, and the checks to run before you trust any 'Rust alternative' label.

If you go looking for open source, Rust-based replacements for Adobe's creative apps, you quickly run into a verification problem. 'Written in Rust' gets used as a quality signal in listicles and launch posts, and 'open source' gets applied to everything from fully forkable codebases to free tiers of hosted services. The two claims are independent, and neither tells you whether the tool covers the work you currently do in a paid suite.
This piece is deliberately narrow. It looks at one project in detail: ArtCraft, an open source studio for AI-assisted image and scene composition.
We cover what ArtCraft says it does, where that overlaps with Adobe-style workflows, and how to check the Rust and licensing claims yourself before you plan a migration around them.
The claim to verify first: language and licence
ArtCraft's own page does not state the language it is written in. It says the project builds open source tools for artists, that 'the whole studio is on GitHub', and invites you to 'read it, fork it, make it yours.' Nothing on that page identifies it as a Rust project. If Rust matters to you, perhaps for memory safety, native performance or because your team maintains Rust code, check the repository directly.
Checking is quick. A Cargo.toml at the repository root, or in workspace member directories, means Cargo builds at least part of the project. GitHub's language breakdown bar gives a rough split by file volume, but desktop creative apps are often hybrids. A native core can sit under a web-technology frontend, and the language bar can be dominated by TypeScript even when the performance-critical parts are something else. Read the build files, not the badge.
What ArtCraft actually offers
ArtCraft describes itself as 'controllable AI for artists.' Its pitch is that text prompting alone gives too little control: you compose the shot yourself, then let a model render it. It runs on macOS, Windows and in the browser through a hosted studio at app.getartcraft.com, which the project says needs no install.
The feature list on the site:
- Image to Location: place virtual actors into physical environments, keeping a single location consistent across multiple shots.
- 3D Compositing: build scenes with depth from images, backdrops, foreground elements and props.
- 2D Compositing: layers, background removal and simple drawing tools for precise scene assembly.
- Image to 3D Mesh: turn images into geometry so elements can be positioned deliberately.
- Mixed Assets: combine cutouts, worlds and meshes on one canvas.
- Character Posing: pose characters for scene and camera blocking.
- Background Removal: cut subjects out of images for use as assets.
The page also lists model names, Seedance 2.5 and Nano Banana 2, among its capabilities. That tells you the studio is a front end for generative models rather than a self-contained pixel editor.
Where it overlaps with Adobe workflows, and where it does not
The overlap is real but partial. Layered 2D compositing and background removal are everyday tasks for anyone who works in a raster editor. If most of your editor time goes on cutting out subjects and assembling scenes for concept art, storyboards or pre-visualisation, ArtCraft targets that work directly. Character posing and scene blocking push it towards pre-production rather than final retouching.
What ArtCraft's site does not show is just as important. It makes no mention of colour management, print output, vector tooling, typography, RAW development or timeline video editing. If those are what tie you to a paid suite, nothing here suggests ArtCraft replaces them. Treat it as a composition and generation studio that may take over part of a pipeline, not as a drop-in suite.
What 'no subscription' does and does not cover
The ownership argument is the core of ArtCraft's positioning. The site says 'stop renting from websites': no subscription, no aggregator middleman, no rent payments, and software that is 'yours to own and keep, forever.' Because the code is public, you can fork it and keep running a version even if the project changes direction. That is the practical value of open source over a free-to-use proprietary tool.
Two phrases are worth a closer look before budgeting. The site also says 'free to start', which suggests some usage may not be free. It also says there is no aggregator between you and the models. Read together, these imply the generative models themselves may carry their own access costs, separate from the studio. The page does not spell this out, so confirm how model access is paid for before assuming your total cost is zero.
Where this does not fit, and what to watch for
If your requirement is specifically a Rust codebase, nothing on ArtCraft's own page confirms that it meets it. Verify it in the repository, and be wary of roundup articles that assert a language without linking to source. If you need deterministic, non-generative editing, such as retouching client photos to spec or producing print-ready layouts, a model-driven composition studio is the wrong category of tool, however open its licence.
Also watch the split between the desktop app and the browser studio. The browser version is convenient, but a hosted studio is still someone else's server. The 'yours forever' promise is strongest for the code you can build and run yourself. Finally, check the licence file in the repository rather than relying on the 'open source' label on the marketing page. The licence determines whether you can modify the studio, redistribute it or embed it in a commercial pipeline, and no product page settles that.
This article draws on Open Source Alternatives to Reflector? and answers to it (1, 2), on the Stack Exchange network, licensed under CC BY-SA 4.0.
- #AI image composition
- #Adobe alternatives
- #ArtCraft
- #Open Source
- #Rust
- #background removal



Comments