TL;DR: This project is like a “younger sibling” trying to challenge Adobe, the “big brother,” with a set of free, open-source tools and AI control. Its strengths are a familiar workflow, but users should be cautious about incomplete functionality, security, and code review.
A solo developer used Rust (a programming language focused on performance and memory safety) and Claude to build a suite of alternatives to several Adobe products, including PhotoCraft, LightCraft, ImageCraft, and FilmCraft. They are available for download, with the goal of reaching 100% feature parity with Adobe within one month.
The selling points are a familiar interface and workflow, along with AI integration through a JSON control channel (a channel for sending commands in JSON format) and an MCP server (a standard server for connecting AI to tools). However, questions remain about missing functionality, the security of software built extremely quickly, and the thoroughness of reviewing such a large amount of code. Regarding intellectual property, the developer states that this is a clean-room reimplementation (rebuilding software by studying its external behavior without copying the original source code) and that no Adobe source code was used or copied.
What does this project include?
This suite includes alternative tools for several Adobe products, available for download from GitHub, such as PhotoCraft, LightCraft, ImageCraft, and FilmCraft, along with other projects in the same suite.
The goal is to bring the user experience of multiple types of creative tools together, rather than requiring users to work with free programs from different developers that each have different workflows.
When free tools still disrupt your workflow
There are many free alternatives, but each program uses a different layout and workflow. Users therefore have to adapt every time they switch tasks—like having to move to a new desk whenever they change programs. Although Affinity has made a strong attempt to compete with Photoshop, it still has a learning curve (the time required to learn how to use it) and does not offer an interconnected suite of programs like Adobe.
The developer’s goal is to combine tools such as PhotoCraft, LightCraft, ImageCraft, and FilmCraft into a unified experience. This could reduce program switching and create a smoother workflow for people familiar with the Adobe suite.
From the Adobe standard to a newly built alternative suite
This project presents itself as a suite of open-source software (software whose source code is publicly available for inspection and further development) that attempts to replicate Adobe’s familiar layouts and functionality. It is built with Rust, from PhotoCraft and LightCraft to ImageCraft and FilmCraft.
The difference is the integration of AI and an agent-native approach (designing tools so AI can work with them directly) into the applications themselves. AI can therefore control tools and menus through a JSON control channel and MCP server, meaning the software is not merely an alternative for people—it is also designed for AI to create work through the same workflow.
The original Adobe suite versus the project’s rebuilding approach
Adobe Creative Suite has long been an industry standard, and many workflows depend on the tools in this suite. This new project attempts to create an open-source alternative that combines familiar interfaces and functionality into a single experience, using Rust as its primary language.
| Factor | Adobe Creative Suite | Newly built project |
|---|---|---|
| Role | Industry standard | Open-source alternative |
| Workflow | Multiple tools in one suite | Attempts to unify the user experience |
| Feature target | No information about the previous version in the article | Aims for 100% parity within one month |
| Direct test results | No information in the article | No information in the article |
Features that could change how people actually work
The multiple tools in the suite could help users work continuously within one system, without switching back and forth between programs from different developers. Meanwhile, the familiar layouts and functions could make it easier for Adobe users to get started.
AI integration opens the door to creating work directly through the software, while the JSON control channel and MCP server allow AI to access various tools and menus and carry out creative tasks on its own—assuming the features actually work as intended.
How is this different from Affinity and other free software?
The project’s selling point is its attempt to bring familiar Adobe layouts and workflows together in one suite, along with AI integration. However, some functionality is still missing and remains under development.
| Factor | This project | Affinity | Other free creative software |
|---|---|---|---|
| Layout and workflow | Focused on Adobe-like familiarity | Still has a learning curve | Often very different |
| Unified suite | Intended to combine multiple tools | No integrated suite | Produced by multiple developers |
| AI integration | Focused on AI and agent-native design | Not specified | Not specified |
| Feature status | Some features are still missing | Not specified | Not specified |
Strengths and concerns to weigh
PhotoCraft, LightCraft, and FilmCraft are available as free downloads, are open source, and are built with Rust. Their strengths include attempting to combine multiple types of tools into a unified approach, while allowing AI to control the tools directly through JSON and MCP.
Pros
- +Free to download and open source
- +Built with Rust and combines multiple types of tools
- +Designed for AI use through JSON and MCP
Cons
- −Security and privacy remain concerns
- −File handling may be unsafe
- −The large volume of code may not be thoroughly reviewed
- −Some functionality may still be incomplete
The costs in time and risk
Free to download does not mean the cost is zero. AI-generated software still requires scrutiny for potentially enormous amounts of code, privacy issues, malicious code, and unsafe file handling—especially when a single developer is maintaining multiple programs.
The uncertainty lies in the possibility that some functionality is still incomplete, along with security risks that need to be assessed before actual use. If it were me, I would recommend testing it with copies of files on a separate machine first, and avoiding it for critical work until the code, file handling, and AI access permissions have been clearly reviewed.