I’m answering here as I keep seeing similar questions about when Logseq DB will be ready. But I’m not going to keep answering questions in this thread as the alpha test has just started and I don’t have all the answers yet. Please wait for the blog update once Logseq DB is more stable.
There’s no ETA. It’s done when it’s done.
That’s because we’re now in closed alpha testing, for which there’s an item on the public roadmap:
I’ll ASAP release the blog post with answers to (most of) the questions in this thread. However, there’s still a lot changing in Logseq DB because of the closed alpha test—which only started last week. That means anything I’d publish now could be incorrect or irrelevant next week. So once the state of Logseq DB has settled down a bit and I’ve put my testing hours in, I’m better able to write an informative blog update.
As for seeing Logseq in “the wild”: there’s a very early browser-based demo of Logseq DB, but we don’t recommend it for daily usage as data loss is very much possible and several features are still missing. Use it at your own risk, but please don’t send us any bug reports or feedback.
We only collect feedback from our alpha testers at this moment; they know where and how to report bugs and suggestions. The developers simply cannot handle hundreds of incoming issues all at once. That’s why we have a closed alpha test so things stay manageable.
As everything is still in flux, we cannot give any dates for when we expect it to be ready for general use. What gets added, changed, or removed all depends on the feedback of the alpha testers, which is completely unpredictable.
If you have any specific questions that you really cannot wait to have answered, please send me a DM.