What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- What data scales have you tested this design on so far?From this comment
- How useful is the DuckPGQ extension compared to this?From this comment
- How and how much did the listed AI contributor help build it?From this comment
- Does it support backup like Litestream for production single-server use?From this comment
What they doubted or pushed back on our summary
- Embedded databases often struggle with multi-process locking, which graphs make harder.From this comment
- Multi-process access remains unclear: does one process lock the whole database file?From this comment
- Why not fork and build on an existing graph database project instead?From this comment
- Why not simply use another established graph database with faster OLAP queries?From this comment
What the maker answered our summary
18 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Benchmarked up to one million nodes, mostly used at smaller scales for agentic memory experiments.From this comment
- Chose to build from scratch to learn, accepting it may remain just a fun project.From this comment
- Admitted no cross-process safety mechanism and promised a file lock; single writer, multiple readers.From this comment
- Aims for simplicity and single-file use, unlike broader multi-model databases with company backing.From this comment
What a builder can take from it: A builder should state intended scope and limits openly, since clear documentation and honest answers to tough questions earn trust. our reading
The title, taken apart our calculation
This post got 190 points; the median for all 1442 posts is 112. In Developer tools (185 posts) the median is 106 points and 38 comments.
When it was posted our calculation
Tuesday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Tuesdays it was 2.8% of 8,995. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Developer tools teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with