Rebuilding the Creative Suite: Veteran Developer Uses Rust and AI to Challenge Adobe’s Hegemony

Main Facts

The landscape of professional design software is experiencing a seismic shift, driven by a combination of rising alternative platforms like Canva and Affinity, widespread user frustration over controversial artificial intelligence (AI) terms of service, and fiercely criticized subscription cancellation policies.

In a bold move that has captured the attention of the software development and design communities alike, a veteran software engineer has successfully built open-source, clean-room replacements for seven of Adobe’s flagship applications: Photoshop, Illustrator, Premiere, Lightroom, After Effects, InDesign, and Acrobat Pro.

The developer behind this ambitious project is Brandon Thomas, a 15-year industry veteran with a background in building mission-critical systems. Using the programming language Rust—renowned for its memory safety and high performance—alongside advanced AI models like Anthropic’s Claude, Thomas managed to replicate the core functionalities of Adobe’s heavily guarded creative ecosystem.

The resulting suite is completely free, open-source, requires no subscription, and grants users full ownership of the source code. Thomas built the project largely as a direct protest against what he terms "dark patterns," specifically targeting Adobe’s notoriously difficult subscription cancellation fees and restrictive user terms.

While the project has been heralded by some as a triumph of modern AI-assisted engineering, it has simultaneously ignited a fierce debate across Hacker News, Reddit, and various tech forums regarding the long-term viability of AI-generated code, the definition of software innovation, and whether professional creatives can ever truly trust a nascent, solo-developed alternative with their livelihoods.


Chronology

To understand how a single developer managed to replicate a multibillion-dollar software suite, it is necessary to examine the events leading up to this point:

  • The Adobe Backlash (2023–2024): Over the past few years, Adobe faced mounting criticism from its user base. Controversies arose regarding changes to its terms of use—specifically clauses that appeared to grant Adobe broad rights to train its Firefly AI models on user content. Simultaneously, public outcry intensified over difficult subscription cancellation processes.
  • The Regulatory Pressure (Mid-2024): Adobe’s business practices drew the attention of regulatory bodies. Notably, the U.S. Federal Trade Commission (FTC) scrutinized the company’s subscription terms, culminating in a significant legal settlement regarding hidden cancellation fees and difficult-to-exit contracts.
  • The Catalyst and Development Phase (Late 2024–Early 2025): Frustrated by being "bit by the dark pattern cancellation fee one too many times," Brandon Thomas decided to take matters into his own hands. Leveraging his decade-long experience with Rust and utilizing AI models like Claude to accelerate coding pipelines, Thomas embarked on a clean-room reverse-engineering project to clone seven core Adobe products.
  • The Public Reveal (Early 2025): Thomas took to Hacker News and the Reddit communities (r/SaaS and r/technology) to announce his open-source suite. The posts immediately went viral, sparking intense debates about the future of software development, corporate monopolies, and the ethics of AI code generation.
  • The Ongoing Industry Debate: Industry analysts, professional designers, and software engineers continue to debate the implications of Thomas’s project, weighing the excitement of free, open-source tools against the practical realities of software reliability, enterprise support, and long-term maintenance.

Supporting Data

The scale of Adobe’s dominance—and the friction points that inspired Thomas’s project—can be understood through several key metrics and technological pillars:

Someone just rebuilt Adobe Creative Cloud with AI – then gave it away for free
  • 7 Core Applications Replicated: The open-source suite covers Adobe’s most essential tools: Photoshop (raster graphics), Illustrator (vector graphics), Premiere (video editing), Lightroom (photography), After Effects (visual effects), InDesign (page layout), and Acrobat Pro (PDF management).
  • 100% Rust Codebase: Unlike web-based wrappers or simple scripts, Thomas utilized Rust, a systems programming language known for preventing memory leaks and concurrency errors. Thomas noted his extensive background, stating he has spent a decade writing production-grade Rust, including six-nines payment rails handling billions in daily transactions, as well as advanced robotics and optics automation.
  • AI-Assisted Workflow (Claude): The rapid development timeline was made possible by pairing human architectural oversight with large language models, specifically Claude, demonstrating how single developers can now achieve development velocities that previously required large engineering teams.
  • Financial and Legal Context: Adobe’s subscription model has been a lucrative engine for the company, but it has alienated segments of its user base. Legal scrutiny, such as a high-profile $150 million FTC settlement regarding subscription cancellation terms, has highlighted consumer resentment toward locked-in software ecosystems.
  • Market Alternatives Growth: Competitors like Serif (makers of the Affinity Suite, recently acquired by Canva) and Canva have seen surging user numbers as creatives actively search for perpetual-license or more user-friendly alternatives to Adobe Creative Cloud.

Official Responses and Industry Reactions

The release of Thomas’s Rust-based clones has polarized the tech and design sectors, drawing sharp contrasts between software engineers and creative professionals.

The Developer’s Perspective

Brandon Thomas has been vocal about his motivations, positioning the project as both a technical proof-of-concept and a philosophical statement against software monopolies. In his announcement on Reddit, he emphasized the liberating nature of the project:

"I’ve created Open Source 100% Rust clean-room replacements for 7 of Adobe’s apps… Free, no subscription, and you own the source code."

Expanding on his frustration with the tech industry, Thomas made a provocative statement on Hacker News: "Software is over." He later clarified that the traditional paradigms of massive software development teams and proprietary lock-ins are fundamentally changing as AI tooling lowers the barrier to entry for complex software architecture.

The Creative Community’s Skepticism

While software developers have marvelled at the technical feat of cloning complex applications using AI and Rust, professional designers and editors have expressed deep reservations. For professionals whose livelihoods depend on stability, file compatibility, and precision, an unproven, solo-developed alternative carries immense risk.

As one prominent commenter on Reddit noted, summarizing the sentiment of many working creatives:

"There is a pretty fricking huge difference between an unproven software that vaguely looks like Photoshop and probably can do some of the things that Photoshop can do and a dependable, robust productivity software that you can count on working right and being maintained long-term."

Someone just rebuilt Adobe Creative Cloud with AI – then gave it away for free

Adobe’s Position

Adobe has not directly addressed Brandon Thomas’s open-source clones. However, the company has consistently defended its Creative Cloud ecosystem, emphasizing the deep integration between its applications, cloud services, and enterprise-grade security. Adobe continues to roll out proprietary AI innovations through its Firefly framework, arguing that its integrated ecosystem provides unmatched value to professional workflows despite the controversies surrounding its subscription and cancellation models.


Implications

The emergence of AI-generated, single-developer replicas of enterprise software suites carries profound implications for the future of the software industry, intellectual property, and professional workflows.

1. Democratization vs. Reliability in Software Engineering

Thomas’s project proves that a single experienced engineer, empowered by advanced AI coding assistants and modern memory-safe languages like Rust, can conceptualize and construct functional equivalents of software suites that historically required hundreds of developers years to build. This suggests a future where niche software monopolies could face rapid disruption from agile, open-source challengers.

However, the transition from a functional clone to enterprise-ready software remains steep. Professional creative software requires continuous bug fixes, hardware driver compatibility (such as GPU acceleration for Premiere or complex color management profiles for Photoshop), and backward compatibility for proprietary file formats (.psd, .ai, .indd). Without a dedicated, well-funded organization behind them, open-source clones often struggle with long-term maintenance.

2. The Backlash Against Subscription Fatigue

The enthusiastic reception of Thomas’s project—even among those hesitant to use it professionally—highlights widespread consumer fatigue regarding software-as-a-service (SaaS) subscription models. When users feel trapped by recurring fees, cancellation hurdles, and restrictive terms of service, the appetite for open-source, perpetual-ownership alternatives skyrockets. This trend may force established tech giants to rethink their pricing flexibility and customer retention strategies.

3. Legal and Ethical Frontiers of Clean-Room Cloning

As developers increasingly use AI models to analyze and recreate proprietary software interfaces and behaviors, legal gray areas emerge. While "clean-room design" (where engineers build functionally equivalent software without copying proprietary source code) has a long legal precedent, the integration of AI trained on vast corpuses of existing software documentation and UI patterns raises novel intellectual property questions. How dominant tech companies will respond to AI-accelerated open-source clones remains one of the most critical legal battles to watch in the coming years.

Ultimately, while Brandon Thomas’s Rust-based Adobe clones may not immediately replace Photoshop on the workstations of high-end Hollywood editors or global branding agencies, they serve as a powerful warning shot to the software industry: the monopoly on complex software creation is cracking, and user resentment over corporate lock-in is finding formidable technical outlets.

Leave a Reply

Your email address will not be published. Required fields are marked *