Adobe subscribers found out the hard way that leaving wasn’t simple. Annual plans billed monthly could trigger early-termination charges equal to half of all remaining payments, a fee structure the U.S. government alleged was deliberately obscured.
In March 2026, the U.S. Department of Justice announced a proposed $150 million settlement addressing allegations that Adobe obscured those fees and made cancellations unnecessarily difficult. Adobe denied wrongdoing, but the proposed order would require clearer fee disclosures and simpler exit procedures under the Restore Online Shoppers’ Confidence Act.
The Settlement Behind the Frustration
The proposed settlement details what the government says Adobe hid from subscribers at sign-up.
Under the proposed agreement, Adobe would pay $75 million in civil penalties and provide another $75 million in free services to customers. The government alleged that Adobe’s subscription terms buried the cost of leaving in fine print and inconspicuous hyperlinks that users were unlikely to notice before clicking “subscribe.”
Adobe disputed that characterization, saying its cancellation process and subscription terms were transparent. No final court ruling has been issued on the matter as of the available reporting.
“Software is over.”
Brandon Thomas, Artcraft developer
That is Thomas’s position, not an independently verified assessment of the software industry. It does, however, capture the frustration behind his project.
What Artcraft Actually Is
Built as a free alternative to Adobe’s subscription suite, Artcraft is ambitious in scope but early in maturity.
According to reporting by Ars Technica, Thomas created Artcraft as a free, open-source alternative to Adobe’s major creative applications. The suite covers seven tools: Photocraft, Vectorcraft, Filmcraft, Lightcraft, Effectcraft, Designcraft, and Printcraft, targeting Photoshop, Illustrator, Premiere, Lightroom, After Effects, InDesign, and Acrobat Pro respectively.
All seven are distributed under MIT and Apache licenses, allowing users to inspect, modify, and contribute to the code. Thomas reportedly used Anthropic’s Claude Opus 5.5 to assist with development, building the applications in Rust with WebAssembly browser versions also in development.
He describes the project as a “clean-room replacement,” meaning the apps were rebuilt from observed behavior rather than copied source code. That characterization is Thomas’s own; it is not a legal determination that the project is free of intellectual-property risk.
Early-alpha status means Artcraft is an experiment, not a production tool. Users have reported problems with basic functionality, and Thomas revised his initial one-month parity claim downward, saying 99% feature parity will likely take months. Maintaining seven complex creative applications requires continuous engineering, testing, security work, and compatibility updates. The long-term sustainability of a project this ambitious remains an open question.
Legal Considerations
Ars Technica raised questions about whether Artcraft’s visual similarity to Adobe’s products could invite legal review.
According to Ars Technica, Artcraft’s close visual and functional resemblance to Adobe’s products could attract scrutiny over interface similarity and commercial presentation. The available reporting does not identify a filed Adobe legal claim against Artcraft.
What This Actually Means
Artcraft reflects a broader shift in what individual developers can accomplish with AI-assisted coding tools.
AI-assisted coding tools like Claude Opus 5.5 are reshaping what a single person can build. They compress engineering work that once required full teams into timelines a solo developer can manage, though Artcraft’s current state reflects that this compression has limits.
Adobe’s advantages do not disappear because a free clone exists. Mature production pipelines, cloud collaboration, ecosystem integration, customer support, and established industry file standards cannot be replicated in alpha. Artcraft may offer the most immediate value to students, hobbyists, and developers who already know Adobe workflows and want a no-subscription starting point, though no user research from the available sources confirms that assessment. Whether the project can move from an impressive early demonstration to software professionals trust with a client deadline remains the central question.
