Is Duplicacy no longer maintained?

Hello,

I have had a Duplicacy personal license for a few years now, and I’m quite happy with it. However, it seems that there no longer is any active development.

Someone will say that it’s good, and that this means that the software is mature and stable. While this is true to a certain extent, the web GUI could do with some improvements, for example, and the last update was two years ago. I also noticed that there are 297 open issues in github, and in the past year there were only two commits (in May 2025, when the latest CLI version was released).

Yes, the software works and it saved my day a couple of times, but I have this nagging doubt that the developer lost interest in this project, and this is not really confidence-inducing for its future.

I don’t really know what to expect with this post. I just wanted to share my thoughts with the Duplicacy user community.

2 Likes

Past topic, answering your question in the comments there:

Another topic:

Both of these threads are years old. Which is quite telling to be honest. 2-3 years ago people were also wondering whether or not the project was dead or not.

Don´t get me wrong. I just renewed my license. It works just fine. But what real progress has been made in the past few years? I know there is a roadmap topic but that also hasn´t been updated in years.

So the question is extremely valid: Is this project still being maintained, yes or no?

Here is another 7 YEAR OLD forum topic with some feature requests: Web GUI Feature Requests - #9 by TheBestPessimist

None got implemented or even acknowledged.

The github repo has SOME activity, the last one being 10 months ago GitHub - gilbertchen/duplicacy: A new generation cloud backup tool. But any mention of the web-ui just goes directly to duplicacy.com so we have nothing else to go on except this forum where not a single question is answered or even acknowledged.

2 Likes

There might be some hope on the horizon:

You beat me to it. These are exactly the points I wanted to make.

If you look at the Duplicacy github, there are 297 open issues, some years old, and never even acknowledged by the developer. If there are comments, they are from other users.

As I wrote above, I have a very strong feeling that the developer lost interest in this project, which does not bode well for its future.

1 Like

Well, hope is the last thing that dies.

Let’s keep our collective fingers crossed. I like Duplicacy very much and it perfectly meets my requirements, so I would like very much to keep using and supporting it, but that implies a certain level of commitment by the developer.

I understand what the developer is saying as I run a business myself and time constraints are real. However, what you do is get help. You are only 1 person and cannot do everything yourself. Running a real business requires some outlay of labor costs.

3 Likes

Nearly another year has passed with no activity on GitHub, a growing list of issues logged, and a feature set starting to lag.

Is it time to consider alternatives such as kopia or restic/rustic?

Oh yes, definitely, it’s high time to switch to alternatives. I was running duplicacy since 2021 when it was great.

Now it seems the dev has completely lost any interest in the project. For example it is still on the B2 API v1, making it virtually unusable.

Sad to see it go, but I’ll ditch it.

The practical workaround would be to use rclone to serve B2 to duplicacy.

At this point, I only use Duplicacy for local backups or SFTP targets. I’m not comfortable relying on its native cloud/API backends for long-term backups, especially since Duplicacy publishes less than one update per year and cloud backends tend to change over time.

At this point I’d question sanity of such backends that introduce breaking changes into their api on an annual basis.

To your point — s3 to AWS and GCS are also safe. It’s various abhorrent providers in the race to the bottom, like B2, E2 and other pclouds and the like are the problem. But I maintain they should not been used in the first place as backup targets (data durability gets defenestrated first when corners get cut). So the issue solves itself.

The fact that there is no official statement regarding the initial question for almost half a year gives me food for thought whether Duplicacy will stay my backup solution for the future.

Until now, I payed for the Web UI edition year to year happily to support the product.

It’d be glad to get some more information about the current status of Duplicacy and it’s future / roadmap. Even 3 sentences would be better than silence.

1 Like