I’m a Logseq user for a year now and I love it. However, I haven’t seen any improvements for a while now (last update April 23) and I think it’s strange for a software in beta (if I’m not wrong, they got funding). Also, the promised sync feature never arrives. So I’m starting to think that this project has serious problems or is dead. Does anyone have any information about it? If that’s the real status of the project, maybe it’s time to look for another alternative.
1 Like
Hi there
There are several threads about the level of development activity in the forum, which both:
- would have resolved your concern
- show how it is a recurring concern
To summarize, development has focused on the database version: GitHub - logseq/logseq at feat/db.
I am not sure what you mean by the promised sync feature never arrives. A Sync feature exists: How to Setup and Use Logseq Sync
5 Likes
To add another user’s perspective to etc’s answer:
- I’m also kinda alarmed at how long Logseq has gone without significant improvements. There’s a mind-boggling amount of work being done on the
feat/dbbranch, basically rewriting large amounts of Logseq’s internals to store content in a DB format rather than using plaintext markdown files as the source of truth, rewrite sync logic to be massively faster, etc. As of a month ago (??) I understand that this rewrite has been released as private alpha and is deep into testing & bugfixing territory. But it also seems this rewrite has taken substantially longer than was hoped & planned. etcis right that a sync feature exists since over a year ago, however, I and many others find it unusably slow (and a bit buggy, at least for me). Enough so that I’ve given up on syncing content to my phone, because anytime I open Logseq it takes over a minute before sync is complete and the UI is usable. So I’m holding out for the DB rewrite and sync improvements to be merged, and hoping that Logseq will become “fully usable” to me at that point, rather than “halfway usable” as it is to me now.
4 Likes
Don’t get me wrong, this is just my perception as an external user (and it seems I’m not the only one) but I’m not saying that this is the reality. That’s why I’m asking. If many improvements are on the way, I’m very happy about it because I love Logseq.
PS.
If you allow a suggestion from someone who has worked for a few years in a software company, Github is only useful for developers or enthusiasts. The average user will never read the log to see what’s going on because he/she doesn’t understand it or he/she doesn’t care. In my case, I looked for the information about the updates on the website.
6 Likes
Well, I’m a ‘database guy’ can I help out in any way? I’m under-employed for now, and I would love to find out more about your product. Hit me up any time (am I allowed to provide my own PII here, or can someone reach out?)
3 Likes
I sometimes feel the same concern, and sincerely it is not. It would be a great loss for humanity, and I mean it. Perhaps it is suffering from an extreme architectural rework. A thoughtful communication from the dev team about their roadmaps and vision would be very helpful to stay calm.
With love, a Logseq fan!!
2 Likes
I recommend you read Why the database version and how it's going? and check the roadmap Trello
2 Likes
I think you are absolutely right. Logseq has long made it’s way from a insider-tool to a tool used by the broader mass of people. Therefore information must (in a condensed form) be delivered in a easy to digest fashion. Not Github or discord but the main website, this forum maybe, or even youtube. Bas on the ToolsonTech YT channel does a great job of bringing logseq news and updates alive in an entertaining manner, so you might wanna have a look there.
5 Likes
I just started using Logseq and was wondering the same.
The Blog is quiet for >1 year, while being very active before.
Latest release is from April, again with frequent releases before that.
So for a moment, I was wondering if I should instead start with Obsidian, before being locked in too much.
It indeed conincides with the DB/RTC work.
That works sounds great for the future. So I’m a little relieved now.
I guess my only worry is that there will still be a free way to sync files between platforms (via e.g. iCloud).
That was one of my criteria to pick Logseq and would be a bummer if it stops working or if I’d have to get a subscription.
I generally don’t mind paying for great software. However, I’m just a small personal user and would probably look around for free options if sync stops working.
Looking forward to try the DB version once ready!
Good luck with the progress!
4 Likes
I thought Markdown files being the source of truth was one of the desirable features of LogSeq.
I’m doing my own sync which is essentially to use git to sync with a remote on a server, so that I can work on either my laptop or my desktop system. I’m not using a mobile device at the moment and don’t have plans to (phone/tablet). This seems to work fine for me in the meantime. Since the data is in Markdown files, this works fine.
Admittedly, I am not a power user of LogSeq. Essentially, just keeping notes on things and linking the concepts as a 2nd brain.
3 Likes
Can any or all of this be officially confirmed or is it secret knowledge? Or just secret de Polichinelle?
- The current incarnation of Logseq is pretty much abandonware.
No. The so called Logseq DB can run both in MD and DB mode.
- The development of the current version has saturated and Logseq cannot be any faster or safer without changing its core.
performing a graph with MD files as storage has been proven challenging. So, if you optimize your use case around some of the limitation, you have a pleasant time with the app. There are several examples of heavier use cases out there of the MD version. Else, you could potentially go in DB mode where many of the shortcoming will be addressed
- The new version is being re-built from ground up and will be much better.
not entirely true, the MD and the DB are the same App. The DB mode branches out of the MD. Many of the core functionalities are the same between MD and DB
- A graph database functions as a “source of truth” just fine.
the graph portion of the app remains the same. But there have been some iterations on the schema
- The new version will not be out for at least another year.
Per my estimation, Beta in a couple of months, and out of Beta in => 12 months. They have significantly improved the development pipeline, the Testing process, with more automation integration workflow. There is a lot of changes they push each week.
I hope this help clarify a bit.
5 Likes
Thank you for the information. It is much more useful than someone’s fantasies or interpretations.
PS
Your message doesn’t seem to use quoting properly.
1 Like
I think the problem is the lack of project management and a proper communication team.
Updates on either original version or db version is, to be honest, difficult to comprehend. The dev team also seem very dedicated in their own task to develop db, and communication with existing user is surprisingly little.
I’m rather depressed to have the feeling that the final product might not be what most of the users needed and that I will have to search for another tool, moving all my data (which is a excruciating experience) to the new platform.
I think the dev team really need a professional product manager.
3 Likes
First of all, thank you for the very clear update. I’m glad my original post helped clarify the status of this amazing project.
Good luck with the development of the new DB system and happy new year!
1 Like
Here is the recap of the level of activities on the Logseq GitHub repository during the last 24 months
| Month | Commits |
|---|---|
| 2023-11 | 339 |
| 2023-12 | 303 |
| 2024-01 | 540 |
| 2024-02 | 296 |
| 2024-03 | 441 |
| 2024-04 | 488 |
| 2024-05 | 403 |
| 2024-06 | 429 |
| 2024-07 | 362 |
| 2024-08 | 417 |
| 2024-09 | 430 |
| 2024-10 | 263 |
| 2024-11 | 313 |
| 2024-12 | 357 |
| 2025-01 | 236 |
| 2025-02 | 227 |
| 2025-03 | 336 |
| 2025-04 | 477 |
| 2025-05 | 561 |
| 2025-06 | 402 |
| 2025-07 | 302 |
| 2025-08 | 308 |
| 2025-09 | 295 |
| 2025-10 | 168 |
────────────────────
Total: 8,692 commits
Key observations:
- Most active month: May 2025 with 561 commits
- Least active month: October 2025 with 168 commits (partial month)
- Average: ~362 commits per month
- Peak activity period: January-June 2024 and March-May 2025
1 Like
Hi. danzu. Thank you for your details.
Because Logseq DB is not released. We can only download it from Github Action.
It is so normal that most of people think Logseq is dead.
We just want to know when we can see the beta version of Logseq DB.
And when we can get the V1.0 Logseq. Logseq has been in beta version since 2021.
Hope Logseq DB has a stable sync. I’d like to support the development of Logseq.
Also, I hope officials can release more information and communicate with everyone.
For example, we are so happy to see the roadmap in detail
Logseq DB is in beta for the desktop app and web.
The Mobile and RTC(sync between devices and with multiple users) have been looking good and promising.
Here are the major parts of logseq and their release status
3 Likes
Thank you for the update @danzu. It’s very useful.
Only FYI, I keep seeing many comments from people who think that the project is dead. For instance, I read this week on Reddit a guy saying that he moved to Obsidian because he doesn’t see any improvement in Logseq. However, he insisted that he misses Logseq a lot. So, communication issue.
2 Likes
It’s because initially the “release of DB mode” was supposed to happen with just that feature, but then RTC quickly got bundled into it because it’s somewhat coupled with syncing.
But now since AI is the new trend a bunch of AI features “are necessary” for the new version launch, and then publishing, and calendar support, and etc etc. I wouldn’t hold your breath on a new version coming out before Q3 2026.
3 Likes