Stringers
ShayanAbbas1/dbdelve · ShayanAbbas1

One benchmark table, three posts: a developer rewrote a database client in Rust and got 885 stars in 85 days

What it is A cross-platform desktop database client written in Rust with GPUI, the UI framework from the Zed editor. It supports 11 databases including Postgres, MySQL, SQLite and MongoDB. It's free and open source, and its selling points are fast startup and low memory use.

Why it took off A benchmark table that spells out its methodology (startup 1.1s vs 5.2s for DBeaver, idle memory 133MB vs 606MB), plus a scrolling video of 1M rows, hit developers' frustration with bloated tools. The author posted to r/ZedEditor first, then r/madeinrust to reach the Rust chart, and finally got to #6 on the HN front page with a second Show HN.

BHow to ride it Apply the same playbook to another bloated dev tool: rewrite the common path natively for 90% of the work, publish benchmark charts and stress-test videos against the best-known rival, stay free forever with one-click import, and get the early adopters from the stack's own community before taking it to HN. Don't build yet another GPUI database client.

Grade B: the playbook is clear and transfers to other categories, but doing every step right still only gets you roughly a thousand stars in three months. Four or five projects in the same framework and category already exist, dbflux, nine months older, has only 530, and HN is starting to push back on 'Rust rewrites', while GPUI itself is still unstable. Spreading in a small circle
Data (updated daily) · Repo created 2026-08-17 · 1,584 stars · 7 days +377
GitHub · stars
05001k1.5k10-0910-1910-2911-0911-201.6k
Data 2026-10-09 → 2026-11-20 (43 days, 42 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Nov 9, a fairly unknown developer, Shayan, posted his database client DBDelve to Hacker News for the second time. The first post in September got 3 points; this time it got 97 points, reached #6 on the front page, and gained 168 stars that day. The project itself isn't new: there are over a dozen free, open-source database clients already, at least four others are built on the same Rust + GPUI stack, and one came earlier. He won on a benchmark table, a video, and the order he posted in. Below: what he did, how the stars came in waves, and where you can use the same approach.

Nov 9's second Show HN

2026 Nov 9 16:36 (UTC), Shayan posted 'Show HN: DBDelve – Open-Source DB Client Made with Rust and GPUI' on HN. The opening of the post is about himself:

I used an old machine for years, so any bloat was painfully obvious. I remember DBeaver crashing in front of me several times... I replaced my usual dev tools with performance-focused ones (Zed, Ghostty and so on), and the only thing missing was a database client.

Next came a benchmark table: the same Postgres table, each run 5 times with the median taken, with machine and versions clearly stated (M1 Pro 32 GB, DBDelve 0.3.6 vs DBeaver 25.3.1, measured with 10-11):

DBDelveDBeaver
Startup1.1 s5.2 s
Idle memory133 MB606 MB
Query 1,000 rows0.21 s1.96 s
Fetch 1M rows56 s208 s
1M rows memory usage4.9 GB17 GB

He also attached a YouTube video: 1M rows with 100 columns per row, scrolling without stutter. The post stayed on the front page for about 9 hours, peaking at #6 with 97 points and 34 comments. The repo gained 168 stars that day (Trendshift). By Nov 10, it had 885 stars and 46 forks (GitHub).

What it is

A cross-platform (macOS, Windows, Linux) desktop database client written in Rust. The UI uses GPUI, Zed's own UI framework, which draws directly on the GPU instead of going through a browser engine. It supports Postgres, MySQL, SQLite, SQL Server, MongoDB, Redis, ClickHouse, Snowflake and 11 others, and anything else (like Oracle) goes through ODBC.

A few small design choices make it worth trying: one-click import of all connections from DBeaver and TablePlus (including passwords and SSH), themes importable from Zed and VS Code, connections set to read-only, read-write or full-access, and every keyboard shortcut is remappable. The README says 'No feature is ever going behind a paywall,' and it relies only on voluntary Patreon support. In Oct 18, the license changed from MIT to GPL-3.0 to stop others from closed-sourcing and reselling it.

The builder: on GitHub as ShayanAbbas1, with 3 followers and a dozen-odd public repos totaling 3 stars. First commit was Aug 17, when the project was still called Slate and was only meant to be a native Postgres client for macOS. The repo shipped design docs and an AGENTS.md for AI coding agents from day one. Then it moved fast: Sep 20 v0.1.0, by Nov 9 v0.7.1, 33 releases and 152 merged PRs in 50 days, and nearly all 393 commits are his. My guess: most of the code was written by an AI agent. In his HN post he even said agents work well with GPUI.

How the stars came in waves

No big-account reposts, no media, no ads. Three growth waves, each tied to one post:

TimelineWhere it was postedResult
About 9-20r/ZedEditor, "DB Client made in GPUI", with a 1M-line scrolling video9-20 to 9-22: about +100 stars
9-24First Show HN3 points, 1 comments, barely any traffic
Late September to early Octoberr/SideProject, r/SQL (later deleted)No clear growth seen
About 10-23r/madeinrust, "DB Client Made in Rust + GPUI", 152 upvotes10-25 and 10-26, two days: +157 and +142, landed on Trendshift's Rust chart; on 10-28 it hit #5 on GitHub's daily Rust trending, another round of traffic
11-09Second Show HN#6 on the HN front page, +168 that day

(Reddit post dates are inferred from post IDs, upvote counts come from search snippets; daily star counts come from Trendshift.)

Between the two waves, it gained a dozen or so stars a day on its own. The order matters: first he posted to the people most into this stack (Zed users naturally like "as fast as Zed"), then to the Rust community. Only after getting on the chart, and once the product was mature and the benchmarks done, did he return to HN the second time. The failed first HN post didn't stop him.

There's also a tailwind: in Nov 5, The Verge and others reported that Discord is dropping Electron and rewriting its client in Rust + GPUI. Shopify CEO tobi's GPUI-built tool disktree picked up over 4 thousand stars in late September. "Electron eats too much memory, native is faster" has been the hot topic in dev circles these past few weeks, and the second Show HN landed right in the middle of it. How many stars the wave actually brought is unclear (inference, no direct evidence).

One number to read alongside the others: the GitHub Release installers have had roughly 3,200 downloads in total (excluding Homebrew, AUR, and Snap). Stars mostly mean "looks good"; far fewer people actually use it.

Same idea, others got 0 to 530

Database clients are an extremely crowded category of open-source projects:

ProjectApproachstarCompared with DBDelve
DBeaverJava, the most feature-complete52.4KDBDelve's benchmark target
t8y2/dbxTauri, 100 database types, built-in AI29.7K (2026-04 created), still gaining over a thousand a day in the last ~7 days, 1The biggest winner of the period; someone on HN directly asked "what makes it better than dbx?"
Chat2DBAI-first28.4K
Beekeeper StudioElectron, advanced features paid23.9K
TableProNative Swift, macOS-focused6.4K (2025-12 created)Also "native and fast", seven times DBDelve's stars
0xErwin1/dbfluxRust + GPUI, keyboard-first530 (built by 2025-12)Same framework, nine months earlier, since overtaken
SQLlyRust + GPUI, closed source, $100 one-time purchaseUnknownSame framework; around the HN day it published a "DBDelve vs SQLly" comparison page to ride the traffic
Cellar, onetcli, tablex, TupleBase, and othersGPUI or native0–153Small projects in the same space

(Star counts are GitHub data from early November.)

The dbflux row is the one to look at. Same framework, same approach, nine months earlier, and still 530 stars. Someone on HN posted its link and said "there are many database clients already, some written in GPUI." What DBDelve added wasn't technology, it was packaging: a benchmark table against an established tool with the method spelled out, a video that explains itself in seconds, a "never paid" promise, one-click migration, and 50 days with 33 releases that signaled "this won't be abandoned."

What the HN commenters are saying

34 comments, with a few clear camps:

  • Agreeing that everything is bloated. "Every DB client I've used is bloated" and "the memory footprint versus DBeaver is too hard to resist." Others keep looking for a cross-platform replacement for MySQL Workbench, saying today's tools all end up "adding cloud features, then forcing you to log in."
  • Questioning whether speed matters. "Most of the time you're waiting on the database to run the query, so is a fast client hard to sell?" The author's answer: with the same result set, other clients crash, while this one scrolls smoothly; drawing the UI after a query is much faster too.
  • Asking how long it can last. "Features never paid, so how do you keep developing after two weekends?" The author: through voluntary sponsorship, and he has been shipping continuously for months.
  • Doubting the stack itself. "I'm sick of this 'rewrite everything in Rust' AI slop movement." Others say the GPUI official repo hasn't released in a long time, and "everyone has a vibe-coded GPUI fork, so you either build your own or build on quicksand."
  • Asking for concrete features. Smart completion like DataGrip's, AI writing SQL, native Oracle support. Someone hit an error with Postgres composite types, and someone else said .sqlite files in WSL won't open while "dbx can."

The first three are where this playbook worked, and the fourth shows its limit: "rewritten in Rust" is already starting to annoy people on HN.

Where else this playbook could work

Broken down, DBDelve used a combination you can copy:

  1. Pick a tool developers open every day that is widely known to be bloated (Electron or Java) and good but paid;
  2. Rewrite the most-used 90% in a native framework, without chasing full feature parity;
  3. A benchmark table against the most famous rival, with machine, versions, and method stated;
  4. A video of an extreme scenario (1M lines);
  5. "Never paid", plus one-click import from the rival;
  6. Post first to the small circle most into the stack, and go to HN only after getting on the chart.

But more people are walking this path. Four or five database clients already use GPUI; the Git client rgitui (GPUI, created in March this year, 276 stars); and on Reddit people are already building GPUI versions of API debugging tools and Docker desktop apps. Judging by DBDelve's results, this playbook's ceiling is roughly a thousand stars in three months, not tens of thousands. dbx, which really did reach tens of thousands, got there on feature breadth, built-in AI, and the Chinese developer community.

If it were you

Verdict: B. Worth trying: the playbook is clear and transferable to other categories, but the payoff is limited, and this path is getting crowded. DBDelve did every step right and got 885 stars in three months; the same-framework, earlier dbflux is at 530, and the other peers are in single digits. "Rust rewrite" is starting to get criticized on HN, and GPUI itself is still unstable.

Good fit for: developers who know Rust or a native UI framework (Swift, GPUI) and have been frustrated by a bloated tool themselves; people willing to sustain two or three releases a week with an AI agent for three months or more; people who want an open-source project worth putting on a résumé.

Bad fit for: anyone wanting to build yet another GPUI database client (at least four are already at it, and the leader has emerged); anyone planning a demo and one post and then walking away; anyone expecting a thousand stars a month.

How to do it, ranked by worth:

  1. Switch categories. First search GitHub for "gpui + category" and "native + category" to confirm nobody has claimed it, then pick a rival famous enough that a benchmark can show a clear gap: for example, categories where only old tools remain like MySQL Workbench, desktop viewers for huge log or JSON files, or desktop browsers for message queues and object storage. The more famous the rival, the more convincing the benchmark table.
  2. Switch the framework or the platform. TablePro is Swift and macOS-only, and it has 6.4K stars, more than the GPUI versions. "Native" is the selling point itself, so you don't have to use GPUI. One platform done extremely well is easier to remember than three platforms done halfway.
  3. Build the part DBDelve hasn't done well. The clearest demand in the HN replies is DataGrip-style smart completion and AI help writing SQL. Ship it as a standalone library or editor component (e.g. SQL completion for GPUI) that those clients can also adopt. That stands out more than another full client.

How to get users: follow DBDelve's sequence. From day one, put the benchmark table on the first screen of the README and spell out the method (machine, version, runs, median). Post the first thread in the communities that most share your stack (r/ZedEditor, r/madeinrust, r/swift), with a video of an extreme use case. Once you get on Trendshift or the GitHub language daily chart, write a Show HN about why you built it, with the benchmarks and limitations laid out. If the first HN post doesn't take off, post again once the product is more mature and the benchmarks are updated. Use titles that say "faster for X by Y" rather than "rewritten in Rust."

When to move: the "native vs Electron" wave was ignited by Discord's news, and the GPUI toolkit is taking shape over these months. Ideally ship the first version before Q1 of 2027. Once GPUI has a stable official release and more templates, similar projects will pop up all at once and a benchmark table won't stand out.

Signs this call is wrong: ① DBDelve passes 3,000 stars by year-end and keeps growing steadily. This category's ceiling is higher than estimated here, so raise the grade. ② Someone uses the same playbook in another category and passes 1,000 stars within a month. The playbook is replicable, so raise the grade. ③ Over the next few months, "Rust/GPUI rewrites X" posts on HN generally get single-digit points. The community is tired of it, so lower the grade.

Data and sources

GitHub: the ShayanAbbas1/dbdelve repo page, README, commit history, Release download counts, and the author's profile 11-10 (checked live). Stars of similar repos in the table (early November). Daily stars: Trendshift. Hacker News: the body and comments of the 11-09 Show HN (item 50427934), and the first Show HN (item 9-24 49834132). Reddit: posts in r/ZedEditor, r/madeinrust, r/SideProject, r/SQL (dates inferred from IDs, upvotes from search snippets). The SQLly website comparison page. The Verge 11-05 report on Discord moving to GPUI. Anything marked "inferred" is inference.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
DBeaverOpen sourceRepo 2015-1052.4K starsJVM, full-featured but heavy; the benchmark target for DBDelve, and its connections can be imported in one click
t8y2/dbxOpen source2026-04-2929.7K stars, +7 in the last 1,057 daysTauri, 100+ databases, built-in AI/MCP, Chinese-speaking community; DBDelve only differentiates on "GPUI is faster than Tauri"
Beekeeper StudioOpen source201923.9K starsElectron, advanced features paid
Chat2DBOpen source202328.4K starsAI-first, heavyweight
TableProOpen source2025-126.4K starsNative Swift, mainly macOS/iOS
TabularisOpen source2026-015.4K starsPlugin-driven, MCP, SQL notebook
0xErwin1/dbfluxOpen source2025-12-30530 starsAlso Rust + GPUI and earlier; DBDelve overtook it with benchmarks, videos, more engines, and faster releases
alpcanaydin/tuskOpen source2026-09-28431 starsmacOS-only, with an AI assistant
vicanso/zedisOpen source2025-112.2K starsGPUI, but Redis only
SQLlyOther2026Unknown (closed source, $100 one-time / $200 lifetime)Same framework and drivers, paid, focused on smart completion and DBA tools; DBDelve is free and open source with more engines (Mongo/Snowflake/ODBC)
TablePlus / DataGrip / DB ProOtherYearsLarge (commercial)Native or JVM, paid; DBDelve's "Stop paying for your DB Client" is aimed squarely at them
Where users come from
  • Verified Reddit r/ZedEditor (with a 1M-line scrolling video): post 1wlqx62, ID-based estimate of about 9-20, matches Trendshift 9-20~22 +100 stars; upvote count not verified
  • Verified Reddit r/madeinrust: post 1xdfz4u, search snippet shows 152 upvotes and 17 comments, estimated date 10-23/24; 10-25/26 +299 stars
  • Verified Organic chart traffic (Trendshift Rust Top 25, GitHub Rust daily chart): Trendshift 10-25 #10, 10-26 #12; our github library shows 10-28 at #5 on the Rust daily chart
  • Verified Hacker News Show HN (second attempt): 11-09 item, 50427934,97 points, 34 comments; our hackernews database logged it reaching #6 on the front page at best; +168 stars that day. The first post on 9-24 only got 3 points
  • Verified Aggregators / reposts / SEO articles: r/BestGitHubRepos, @betterhn20/@betterhn50 X bot, promptzone, ic.work Chinese long-form review, Luca Tariciotti blog (11-02), directory sites like libhunt and repoinsider, YouTube channel 59 views
  • Inferred Platform event: GPUI wave / Discord dropping Electron for GPUI: covered by The Verge and heise 11-05; tobi/disktree at 4K stars, gpui-kit +7 in the last 1,187 days; timing close to 11-09 front-page hit on HN, but no direct evidence of referral traffic
  • Inferred Ads / big X accounts / Product Hunt / media: none found; no related posts in our x library

ShayanAbbas1/dbdelve: a native database client written in Rust + GPUI

Research date 2026-11-10 (Beijing time). Repo github.com/ShayanAbbas1/dbdelve, website dbdelve.github.io/, GPL-3.0 (MIT before 10-18).

Bottom line

DBDelve is a cross-platform database client built in just over two months by indie dev Shayan Abbas, who used an AI coding agent to write it. The repo is his only one on GitHub, and he has 3 followers. It didn't blow up in one shot. Instead, he kept posting in small Rust / Zed / GPUI communities: a 1M-line scrolling video on r/ZedEditor in September brought the first wave (about +100 stars), a r/madeinrust post in late October (152 upvotes) pushed it onto Trendshift and GitHub's Rust daily trending (+300 over two days), and a second Show HN post, on 11-09, hit #6 on the HN front page (97 points), adding +168 that day. The hook is a benchmark table showing DBeaver starting in 1.1s vs 5.2s, idle memory 133MB vs 606MB, plus a pledge to never charge, riding the GPUI wave (Zed, tobi/disktree, and 11-05 announcing its client rewrite in GPUI). It's still small: 884 stars, while the Tauri client t8y2/dbx in the same niche already has 29.7k stars.

1. Data

  • Stars (data card / our GitHub repo repo_day, Beijing time dates): 10-21 210 → 10-25 238 → 10-26 349 → 10-27 535 → 10-28 589 → 11-09 679 → 11-10 773; GitHub API live: 11-10 884 stars, 46 forks. gain_7d 127, gain_30d 591.
  • Trendshift daily (https://trendshift.io/repositories/250700, US dates): 9-20 +16, 9-21 +57, 9-22 +27 (first wave); 10-23 +14, 10-24 +15, 10-25 +157, 10-26 +142 (Trendshift Rust chart #10, #12); 11-09 +168, 11-10 +33. 53 days with merged PRs: 152.
  • GitHub trending: our trending table has only one entry, 2026-10-28 at #5 on the Rust daily chart (period_stars 25 that day); it has never made the overall chart.
  • Releases: 9-20 v0.1.0 to v11-09 over 0.7.1,50 days, 33 releases in total; cumulative GitHub Release asset downloads 3,223 (GitHub API, excluding the AUR / Snap / AppImage channels outside Homebrew cask). Downloads are far below the star count, which suggests most stars are "looks good" rather than real installs.
  • Contributors: the author has 393 commits, and the other 12 contributors have 1–5 each (GitHub API). The first commit (8-17) reads "Slate is a native macOS Postgres client in Rust on GPUI", with a design spec and AGENTS.md: the project was structured for AI agents from the start, which is why the ic.work comment says it "shipped four major versions in 25 days".
  • Monetization: None. The README says "No feature is ever going behind a paywall", and the only support is voluntary Patreon sponsorship. 10-18 switched from MIT to GPL-3.0 to block closed-source clones.

2. Competitors

NameWhereLaunchedScaleHow DBDelve differs
DBeaverOpen source (JVM)2010 era, repo 2015-1052.4K starsFull-featured but heavy; DBDelve's benchmark target is exactly this, and it can import DBeaver connections in one click
t8y2/dbxOpen source (Tauri)2026-04-2929.7K stars, +7 in the last 1,057 daysThe biggest winner of the same period: 100+ databases, built-in AI / MCP, Chinese-speaking community. On HN someone directly asked "what makes it better than dbx?", and the author answered "Tauri isn't as fast as GPUI"
Beekeeper StudioOpen source (Electron) + paid tier201923.9K starsElectron, advanced features paid
Chat2DBOpen source + commercial202328.4K starsAI-first, Java/Electron lineage
DbGateOpen source20197.4K starsElectron / Web
TableProOpen source (native Swift)2025-126.4K starsNative macOS/iOS, also Linux; no Windows
TabularisOpen source2026-015.4K starsPlugin-based drivers + MCP + notebook
0xErwin1/dbfluxOpen source (GPUI)2025-12-30530 starsSame framework, earlier, keyboard-first. DBDelve caught up and passed it on benchmarks, videos, engine count, and release pace
alpcanaydin/tuskOpen source (native macOS)2026-09-28431 starsmacOS-only, with an AI assistant
vicanso/zedisOpen source (GPUI)2025-112.2K starsRedis only
Cellar / onetcli and othersOpen source (GPUI)202637–153 starsSmall projects in the same space, showing several teams already building GPUI database clients
SQLlyClosed-source paid (GPUI)2026UnknownSame framework and drivers; $100 one-time / $200 lifetime, focused on completion and DBA tools. 11-09 published a "DBDelve vs SQLly" comparison page the same day to ride the traffic
TablePlus / DataGrip / DB ProClosed-source, paidYearsBigNative or JVM, paid; DBDelve's "Stop paying for your DB Client" is aimed squarely at them
VS Code / Zed plugins, harlequin, rainfrogEditor plugins / terminal—2.9K–6.5K starsNot a standalone GUI

Bottom line: DB clients are an extremely crowded category, and even the "Rust + GPUI" niche has at least 4 players, including dbflux, SQLly, and Cellar. DBDelve is neither the first nor the largest, only the open-source project with the most stars in this niche right now.

3. Where users came from (by time)

  1. r/ZedEditor "DBDelve, DB Client made in GPUI" (u/blueingreennn, with a 1M-line scrolling video). The Reddit post ID is 1wlqx62; by ID the post was published around 9-20, which lines up with the +100 stars between 9-20 and 22. Reddit is 403 to our machines, so the upvote count is unverified.
  2. r/SideProject (about 9-26), first HN post (9-24, item 49834132). HN only got 3 points and 1 comments, so it brought almost no traffic. The recall reason on the data card, that "10-27's surge came from this Show HN," is wrong.
  3. r/SQL (about 10-07, later deleted by the author).
  4. r/madeinrust "DBDelve: DB Client Made in Rust + GPUI": the Reddit sidebar in Brave search showed 152 upvotes and 17 comments. Based on the ID 1xdfz4u, it was posted around 10-23/24. Two days later, 10-25/26 gained +299 stars, entered Trendshift's Rust Top 25, and reached #5 on GitHub's daily Rust chart in 10-28. The charts brought another round of organic traffic. Whether it was also posted to r/rust is unverified.
  5. r/BestGitHubRepos reposts (about 10-30), plus automatic listings on directory sites such as cli.masoko.net, repoinsider, libhunt, and gitdiscover.
  6. 11-02 Luca Tariciotti blog (an SEO-style introduction post).
  7. 11-09 Second Show HN, "DBDelve – Open-Source DB Client Made with Rust and GPUI": 97 points and 34 comments. Our hackernews library's front_snap recorded its best front-page rank as #6 (on the front page from 11-10 02:17–11:17 Beijing time). It was then picked up by the X bots @betterhn20 and @betterhn50, followed by promptzone, ic.work (a long Chinese review), and a YouTube alt account (Alex Hitt, 59 views). That day it gained +168 stars.
  8. Background events: 11-05 The Verge, heise, and others reported that Discord dropped Electron and rewrote its client in Rust + GPUI (290MB idle). Shopify CEO tobi's GPUI tool disktree picked up 4K stars from late September. gpui-kit gained +1,187 stars over the last 7 days. "Electron eats too much memory, native GPUI is faster" was a hot topic, and the HN post's title and benchmark table tapped directly into it. There is no direct evidence of referral traffic, but it was a tailwind.

Not found: paid ads, large X accounts, Product Hunt, media coverage (ic.work is an aggregator of reviews), or signs of star-buying. No posts about dbdelve appear in our x library.

4. Why it took off

  • Specific, verifiable hook: a benchmark table against DBeaver (startup 1.1s vs 5.2s, idle 133MB vs 606MB, 1,000 rows in 0.21s vs 1.96s) plus a 1M-row scrolling video at 120 fps. Developers already resent bloated Electron and JVM tools, and HN comments included lines like "all db clients feel bloated" and "memory impact too good to resist."
  • Found the right communities: it posted to Zed users first (GPUI is Zed's UI framework, so users naturally identify with "fast like Zed"), then to the Rust community, and only then to HN. In the HN post, the author also positioned the project alongside good tools like Zed and Ghostty.
  • Free forever + one-click migration: it counters the paywalls of TablePlus and DataGrip. It can import all connections from DBeaver and TablePlus (including passwords and SSH), and themes can be imported from Zed or VS Code, so switching costs almost nothing.
  • Release speed signals it won't be abandoned: 50 versions and 152 PRs in 33 days, with the engine count expanded from 3 to 11 plus ODBC. On HN someone asked whether the author would still maintain it after a couple of weekends, and the author answered with months of continuous updates. The speed comes from AI agents writing code (the repo has AGENTS.md and docs/agents/).
  • Timing: The GPUI ecosystem takes shape in H2 2026 (gpui-pre and gpui-kit let a solo dev ship cross-platform native apps), and GPUI news on the November Discord made "native vs Electron" a hot topic.

5. Differentiation

Among the free and open-source rivals (DBeaver, Beekeeper, dbx, DbGate), it is the one with native GPU rendering, fast startup, and low memory use. Among the native and fast rivals (TablePlus, DataGrip, SQLly, DB Pro), it is the one that is free, open-source, and multi-engine. A few smaller perks: one-click import from DBeaver and TablePlus, glass themes, Zed and VS Code theme import, and three connection permission levels (read-only, read-write, full access).

This differentiation is why it got its first stars: the "Rust + GPUI" label gave it a natural topic in r/ZedEditor and r/madeinrust. But it is not a moat. dbflux, on the same framework, came earlier, and SQLly uses the same framework and drivers. dbx, using Tauri, also reached a 25MB installer and 29.7k stars. HN commenters questioned it too: "query time is mostly spent in the database, so what's the point of a fast client?" and "the GPUI ecosystem is quicksand, everyone has a vibe-coded fork," with others calling it "rewrite everything in Rust AI slop." So DBDelve got ahead of same-framework rivals mainly because of the benchmark-and-video packaging and release speed, not because of any unique technology.

6. How many people can see it

  • Word spread within small circles: several niche Reddit subreddits, one stint on the Trendshift and GitHub daily Rust charts, and #6 (11-09) on HN's front page. No large accounts reposted it and no mainstream media covered it. In the Chinese-speaking community, only one long review on ic.work.
  • Revenue: none. Patreon supporter count is not public.
  • Copycats: no one has copied it yet. But the closed-source rival SQLly published a "DBDelve vs SQLly" comparison page the day DBDelve blew up on HN, riding its traffic. New GPUI and native DB clients (tablex, TupleBase, dbcat, and others, with 0–7 stars) are being built in parallel, not copying it.

7. Takeaways

  • The star playbook of "rewrite a widely-hated bloated Electron or JVM developer tool in Rust/GPUI (or any native framework)" is not yet saturated: a benchmark table against an established tool, a extreme-case video (1M rows), "free forever," and one-click import from competitors.
  • Posting order: post first to the smaller community that most identifies with your stack (r/ZedEditor → r/madeinrust), then post to HN once you have chart traction. If the first HN attempt fails (3 points), you can wait until the product matures and has benchmark data, then try again.
  • Using AGENTS.md and design docs so AI agents handle most of the coding lets a solo developer ship a release every two days, which is itself a signal that the project won't be abandoned.
  • Use MIT to build up popularity first, then switch to GPL-3.0 once it gains traction, to prevent closed-source repackaging.

8. Uncertain

  • The exact dates and upvote counts for the Reddit posts (Reddit is blocking both our servers and the Mac mini, 403). Dates are inferred from post IDs, and the 152 upvotes on r/madeinrust come from the search snippet.
  • Whether there were any r/rust posts or X reposts during the 10-25 wave (our x library received none).
  • Real usage: about 3.2K Release downloads. Homebrew, AUR, and Snap usage is unknown.
  • The author's background and Patreon revenue.

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.