Alternatives
Products that do what Logseq does
A privacy-first, open-source knowledge base
- 1AT
Creator here. I built lsq to solve a simple but annoying workflow problem: having to leave the terminal just to make quick notes in Logseq. Technical details: - Written in Go using Bubble Tea for the TUI - Reads Logseq's config.edn for format preferences - Supports both external editor ($EDITOR) and TUI modes - Handles both Markdown and Org formats Core design decisions: 1. Zero-config default installation (uses standard ~/Logseq path) 2. Single command to open today's journal (just 'lsq') 3. TUI mode for Logseq-specific features (TODO/priority cycling) The project started as a…
2024 · github.com
- 2SO
We just released a major upgrade to SigNoz with support for Logs management based on ClickHouse. Would love to get any feedback from the community here on what you think and any questions you may have for us Many big companies like Uber and Cloudflare have been shifting to ClickHouse as their main workhorse for Logs management seeing much better performance. for e.g Cloudflare recently shifted from Elastic to ClickHouse and are seeing 8x improvement in memory/cpu resource requirement in ingestion. This is our first release with Logs support and we have added support for: - Filtering…
2022 · github.com
- 3LC
2021 · logtail.com
- 4
- 5
- 6
A native macOS Logseq — no Electron, no cloud, just markdown
Mar 2026
- 7JL
There have been a few times I wanted the ability to select some text out of a Markdown doc. For example, a GitHub CI check to ensure that PRs / issues / etc are properly formatted. This can be done to some extent with regex, but those expressions are brittle and hard to read or edit later. mdq uses a familiar pipe syntax to navigate the Markdown in a structured way. It's in 0.x because I don't want to fully commit to the syntax being stable, in case real-world testing shows that the syntax needs tweaking. But I think the project is in a pretty good spot overall, and would be…
2025 · github.com
- 8
- 9EL
Jun 2026 · github.com
- 10
- 11
- 12
- 13
- 14TA
Hey everyone! I’m working on Telescope - an open-source web-based log viewer designed to make working with logs stored in ClickHouse easier and more intuitive. I wasn’t happy with existing log viewers - most of them force a specific log format, are tied to ingestion pipelines, or are just a small part of a larger platform. Others didn’t display logs the way I wanted. So I decided to build my own lightweight, flexible log viewer - one that actually fits my needs. Check it out: Video demo: https://www.youtube.com/watch?v=5IItMOXwugY GitHub:…
2025 · github.com
- 15WB
Hey hn! I'm one of the co-founders of highlight.io, an open source monitoring tool. Today we're sharing a ClickHouse-based logging solution we've been working on. We wanted to showcase how we built it and share how you could try it out to give feedback. Since we started working on highlight.io, we've been hyper-focused on "cohesion", or ensuring that when you install your monitoring stack, all of the resources in that stack (user interactions, requests, traces, logs, etc.) are connected in a consumable way. We've written up more about our philosophy on this here [1]. We started building…
2023 · github.com
- 16LO
I don't like the existing query languages for Elasticsearch and Grafana Loki, because they are too awkward to use for typical logs' investigation cases. So I designed new query language - LogsQL - and wrote reference implementation for it as a part of VictoriaLogs - an open source database for logs. LogsQL is based on the following principles: - Simplicity. It is easy to write typical queries over logs in it. For example, a single word `error` is a valid LogsQL query, which returns all the logs with the `error` word. Another example is `_time:5m error`, which returns all the logs with the…
2024 · docs.victoriametrics.com
- 17
- 18GA
We built Gonzo to make log analysis faster and friendlier in the terminal. Think of it like k9s for logs — a TUI that can ingest JSON, text, or OpenTelemetry (OTLP) logs, highlight and boil up patterns, and even run AI models locally or via API to summarize logs. We’re still iterating, so ideas and contributions are welcome!
2025 · github.com
- 19LD
2024 · logdy.dev
- 20BO
Hi HN, we are Deepak and Sama, co-founders of BoxyHQ (https://boxyhq.com/). BoxyHQ provides an open-source platform for developers to quickly integrate enterprise features into their software solutions. These include SAML Single Sign-On (SSO), Audit logs, with more to come :) Every B2B startup faces a common challenge when it comes to selling into the Enterprise; they need to allocate time and resources to support all the requirements to make their offering enterprise-grade. Supporting these requirements is a significant undertaking for the engineering team, especially since…
2022 · boxyhq.com
- 21SE
I have been working on SQL Explorer, an open source, Django-based reporting and query tool for (gulp!) almost ten years. It's a tool that fits just right for me and many others, and I love and use almost every day. Write SQL, share results, do some analysis, get insight. No surprises. A live demo instance is here (no login or anything required): https://demo.sqlexplorer.io/ And here's a fairly unprofessional, but very enthusiastic, video tour: https://sql-explorer.s3.amazonaws.com/Sql+Explorer+5.mp4 The UI is constrained enough that there's very little to learn,…
2024 · github.com
- 22
- 23WO
2023 · writedown.app
- 24LS
Hey HN! I’m Karan, creator of Logchef (https://logchef.app), an open-source log viewer built specifically for exploring logs stored in ClickHouse. This tool grew directly out of my $day job managing massive log volumes. Like many orgs, we migrated our log workloads to ClickHouse for its performance, but found the ecosystem lacked dedicated UI tooling for actually browsing and analyzing those logs effectively. We were using Metabase, and while great for general BI, it wasn't designed for log exploration workflows. Common pain points included: - Clunky Ad-hoc Querying:…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →