Cloning Paid Software Is Getting Easier
Maintaining It Is Another Story
Full Article
Read the complete article, including examples, background, practical insights, and technical details.
A familiar paid application gets an open-source alternative. The screenshots look promising, the feature list is ambitious, and someone asks the inevitable question: why are we still paying a subscription?
It is a reasonable question. But before cancelling anything, read the section of the repository that explains what happens after installation. That is often where the comparison becomes more interesting.
Two projects illustrate this gap: Mailcheap, Marc Lou’s self-hosted newsletter application, and PhotoCraft, an open-source photo editor. Their documented status tells a more useful story than the claim that someone has made another expensive product obsolete.
Why it matters
The cost of producing an initial implementation and the cost of keeping software dependable are different expenses. AI-assisted development can accelerate parts of the first, while the second involves an ongoing commitment to users.
There is an important evidence limit here. Claims about AI building these particular projects come from social posts supplied with this story; they have not been independently established here. The repositories support a discussion about ownership and maturity, rather than a precise claim about development speed or AI authorship.
Key highlights
1. Mailcheap makes the ownership trade-off explicit
Mailcheap is a self-hosted newsletter app built around Amazon SES. Its README describes an editor, subscriber management, signup forms, campaign statistics, and handling for unsubscribes, bounces, and complaints.
It also states that this is a one-time release: support is unavailable, issues are disabled, pull requests may not be reviewed, and updates are not planned.
That is a clear offer. You receive code you can run and modify, with responsibility for its future resting with you or whoever maintains your fork.
2. A low sending cost is only one part of the bill
Mailcheap’s README estimates SES sending at approximately $0.10 per 1,000 emails. That figure describes sending costs, rather than the complete cost of operating the application.
The documented setup also involves hosting, MongoDB, and background delivery through QStash. For an adopter, the broader calculation includes those services and the time spent operating them.
A technically capable newsletter owner may find that trade worthwhile. Someone who needs a service they can use without managing infrastructure may reach a different conclusion.
3. PhotoCraft is an ambitious project with an explicit maturity limit
PhotoCraft describes itself as a clean-room, open-source reimplementation of Photoshop in Rust. Its README lists familiar capabilities such as layers, masks, brushes, and PSD support.
However, it also identifies the project as early alpha and says it is not yet a replacement for daily professional Photoshop work. It distinguishes having commands connected to menu items from reproducing their behaviour fully.
That distinction matters when your work depends on accurate results.
4. These projects have different maintenance positions
PhotoCraft should not be described as another unsupported one-off release. Its README points to a roadmap, contribution guidance, issue reporting, and a community.
Mailcheap illustrates an explicit handover of responsibility. PhotoCraft illustrates the distance between an ambitious implementation and professional readiness. Neither repository alone establishes that nobody wants to maintain open-source software.
Industry context
Open-source alternatives existed long before AI coding assistants. The emerging business question is how much easier implementation becomes, and where value moves when more developers can reproduce a useful slice of an established product.
Consider a hypothetical small business replacing its newsletter subscription. A successful first campaign is encouraging. Six months later, an integration changes, a dependency needs attention, or delivery failures require investigation. Someone still needs to diagnose the problem and take responsibility for the fix.
AI may help with that work too. It does not, by itself, establish who reviews the changes, tests the outcome, or responds when something breaks.
The same reasoning applies to creative software. A convincing editing demonstration is valuable, but dependable behaviour across a professional’s actual files and workflows takes further validation.
Apptastic Insight
For developers, these projects offer useful starting points for experimentation, customization, and learning. For businesses, adoption should include a concrete answer to one question: who owns this after deployment?
Paid software vendors still need to justify their prices. An open-source alternative may genuinely be the better choice, especially when its scope matches your needs and you can support it.
But compare the responsibilities alongside the features. The ownership bill includes hosting, maintenance, compatibility, recovery, and your time.
AI can make the first version easier to produce. Software people rely on still needs someone willing to look after the next version—and the problem that arrives before it.
Sources
Repository documentation reviewed on October 12, 2026. This article is business analysis based on the projects’ stated scope and status, rather than an independent assessment of their reliability or AI development claims.
