Selfhosted

If you are running a conduit fork, what is your reason for leaving conduit, and if you are running conduit, why didn't you switch?

Conduwuit (predecessor of Continuwuity and Tuwunel) hard-forked from Conduit and introduced breaking database changes. That is a significant people don't easily "switch over"

It may be slow in development, taking a bit longer to implement a new feature, but not too much longer.

I would say its pace of development is very slow compared to the pace of Matrix in general. But if you only want the barebones features, you can use it.

Or am I missing something the others have to offer?

Feature-wise, Continuwuity offers email support, single-use registration token, policy server integration, user suspending, a ton more of admin commands, and some extra endpoints for Element Call. It is also actively working on OIDC-OAuth (so you can login with your IDP), and an ecosystem-wide Admin API. It also has an active community. I can't speak for the other fork.

Lastly, I don't think anyone "hate" conduit, the project is alright. It's just not the topmost option.

some ominous comments stating that it is practically unmaintained (which is not true)

Objectively, I can see that the last commit to the default branch was in March 2026, and that the 10th newest commit was back in September 2025. Of these 10, 3 are new features and 6 are fixes and 1 is documentation. I also see in the issue tracker that no project developer replied to the two newest reports, which were reported 2 weeks and 2 months ago.

As a subjective opinion, the explanation that Conduit is essentially rock-solid and this doesn't need much upkeep or commits, that is just not credible. The Git history shows fixes and new features, but at a rate that averages just one commit per month. And some of those commits are literally one-line changes.

But let's suppose that the maintainers are uninterested in small UI or quality-of-life features, and only make changes when it crosses their threshold for what is "important" enough. That's a choice, sure, but let's see if that holds water. Here is the project's response to an issue opened in January, with the response being in February that confirms a logic bug and schedules it for the next release.

That was three months ago. No updates. No mentioned branches or PRs or merges. All while this bug remains in place. And that's understandable for FOSS project developers, for whom the project is not their day job.

But in any circumstances, the totality of the evidence does not inspire confidence, let alone a determination that Conduit is "rock solid". And that's even before looking at the code.

TL;DR: the premise of the question is wrong. Conduit is not maintained.

To my knowledge conduit is basically dead in the water. Very little updates if any.

When I chooses my matrix server, o went with the predecessor of Continuwuity and then migrated to Continuwuity and have been happy ever since....

Tuwunnel don't know, I didn't really appreciated the corporate backing somehow and lack of perceived transparency.

Is conduit actually still in business at all?

I run Synapse currently but last I looked at Conduit it wasn't at feature parity with Synapse (granted, that has been a while). The other two I wouldn't touch with a 50 foot pole because of their stupid-ass names.

I think it's basically that. There's new commits in the conduit repo. But it's like one minor thing each other month. While other projects have a lot if activity and added a ton of features and MSCs. At the same time they're equally as stable and possibly easier to use. So... Why not use one of them? You'll get more features, quicker fixes for annoyances in Matrix. And I always wondered why Matrix doesn't come with threaded conversations by default. SSO/Authentication integrations. And clients which can do multiple accounts.