Is PSU being abandoned ?

Hey @krisr ,

PSU is very much alive!

While you haven't seen me as much, I still very much working on PSU every day. We are, and have been, in the process of onboarding more folks to help take over or assist in many of the roles I was performing myself. This means working with teams like development, support, sales and marketing. It also means onboarding teams we didn't have before like security and quality assurance. As you can imagine, this is very time consuming for me but an investment in PSU's future. I'm beginning to get some head space back to get more involved in the PSU community once again. You'll see me hosting the new PSU Community Call, attending events like PSConfEU and being active on here and Discord.

I know there haven't been many cool features in the past few months. This doesn't mean development has slowed down. We actually have many more folks contributing to the PSU source repository than ever before. We've had to focus on some transitional pieces, like a new build and release pipeline and licensing. We've also been working on some foundational pieces like better automated testing, security fixes found during audits and working through the back log of bugs and quality of life improvements.

We are working on aligning with Devolutions' release schedule so you will be seeing 2026.2 soon and we will be announcing those features at PSConfEU. I have a talk dedicated to it. We've been hard at work on those for the last few months as well. I will be the first to admit that we have had more bugs than I would like, but we're working on improving that through more thorough manual and automated testing to catch issues before they go out the door. We're doing the same with security reviews and it's leading to more secure code as a result. PSU has always been a very complicated product to test and it was, honestly, becoming increasingly difficult to manage by myself before joining Devolutions. While code quality is not something that happens immediately, it's a central focus of what we are doing.

As for the GitHub issue tracker move and new community being quiet, I wouldn't worry about that too much. We've already migrated all the GitHub issues into our internal Jira tracker and have started to prioritize them. We're still trying to figure out what we put into the new forum for those or whether we just let the new forum start to collect new items. The forum itself actually integrates with all our internal tooling so it is way more streamlined than before. Users can still request features and report bugs and we can automatically create tickets to work on those items. When they are released, the forum topics will be updated accordingly. The forum is also quiet since it's only been a week since we switched over. We are still fixing links to it and ensuring people know where it is so it's probably going to take a bit for it to bounce back to previous activity. Eventually, we will redirect from the old forum to the new one and have proper links in the product itself.

I hope that helps understand what's happening with PSU. Devolutions is very much invested. I'm still leading the charge.

Thank you for the transparency @Adam Driscoll I can't imagine how much work it is to merge with another company. I really liked the transparency of the GitHub issues to be able to find bugs that others have reported as well as learning about new things people are using psu for. There is a lot of good information you can get about a product based on how others are using it. That feature also helped involve the community about what was changing and what new features were being worked on.

@michaelhanson1458 We hope to continue that transparency through the bug and feature sections on the forum. Like I said, we are still processing all the existing issues and will see if it makes sense to recreate those here.

Is it just me, or is this project actually dying?
Ever since PSU merged with Devolutions (actually, starting a few months before that), development has seriously slowed down. Adam stopped being as involved, releases got rare, and they had fewer new features and way more bugs.
Now that the whole community got moved to Devolutions, even that's looks dead. There are barely any new posts on the forum, and the issue tracker was shut down without being migrated.
I hope it’s just a temporary, but it doesn't look good...

@krisr
I can see why it feels like the project has been abandoned, especially with releases slowing down and the issue tracker disappearing. A quiet forum alone doesn’t necessarily mean the project is dead, but losing the tracker and seeing fewer updates would definitely make me concerned too. Hopefully they’re just going through a transition period and will share some clearer updates soon.

Are you serious?

Looking at 2026.3.x I see the opposite.
Way too many changes and fixes. I can't keep up with testing ;)
To me it seems the use of AI assisted coding added and changed a lot and introduced a lot of bugs.
To me it seems as well that forum posts get handled partially by AI.

It looks like Devolutions has a bigger workforce set on PSU.
And Adam is still keeping after many support calls in the forum.
While the old and nice chit-chat has vanished, there are still many questions and answers (I am subscribed to anything new, and it is a lot)

So while I personally liked the old style much more and I must admit that I am not a big fan of devolutions,
I don't see the project dying at all.
From a business perspective things seem to go the right direction.

Are you serious?

Looking at 2026.3.x I see the opposite.
Way too many changes and fixes. I can't keep up with testing ;)
To me it seems the use of AI assisted coding added and changed a lot and introduced a lot of bugs.
To me it seems as well that forum posts get handled partially by AI.

It looks like Devolutions has a bigger workforce set on PSU.
And Adam is still keeping after many support calls in the forum.
While the old and nice chit-chat has vanished, there are still many questions and answers (I am subscribed to anything new, and it is a lot)

So while I personally liked the old style much more and I must admit that I am not a big fan of devolutions,
I don't see the project dying at all.
From a business perspective things seem to go the right direction.

I am with @deroppi, we have a ton of new features, small enhancements and bug fixes in the last few months (perhaps too much ;)). But the fact that the public issue tracker is gone is something that i do not like too.

It feels like it's still active, but that QA/the overall quality of the product had dropped. I've been running 2026.1.2 for quite a while as I've ran into bug after bug on newer versions that prevents me from updating our production servers and even in dev as say my RegEx endpoints aren't behaving as they had in versions up to 2026.1.2, or bugs with startup, built-in variables randomly missing, permissions not assigning properly, the list goes on... Some of this may be due to more hands working on it and not knowing how parts work, but some of the issues that have appeared should have been caught in early QA (ie the gRPC stuff that troubled 2026.3.x).