Databases: Engineering Signals & Deal Flow

OLTP, OLAP, vector stores, embedded engines, and the storage layer underneath every modern app. At VC Deal Flow Signal we map databases companies, funds, and engineering leaders and score their public GitHub acceleration, so investors can spot momentum before a round is announced.

On our 14-day commit-velocity change signal, the databases companies accelerating fastest right now include Convex, Neon, Turso, among others. Rankings come from public GitHub activity, not fundraise press.

Commit velocity is the total commits to a startup's most active public repository over a rolling 14-day window. Its rate of change is our primary ranking signal: sustained acceleration has historically preceded fundraise announcements by three to six weeks, which is why investors watch it for databases sourcing and diligence.

The breakout names in databases are the companies showing the steepest GitHub commit-velocity acceleration and contributor growth over a rolling 14-day window, the same pattern that has historically preceded fundraise announcements by three to six weeks. This hub lists 20 curated databases companies; the full signal list, filterable by sector, is at /signal, and every ranking number links back to a public GitHub repository.

By watching the engineering signal rather than the press release. Public GitHub activity (commit velocity, contributor influx, and new-repo creation) starts accelerating three to six weeks before most databases fundraises are announced. The four primitives we track and the six-signal panel are documented at /methodology and tied to fundraise probability in SSRN preprint 6606558. A weekly digest of databases companies matching a fund's stage and check-size filters is available at /firstlook.

We currently track 20 curated databases companies whose GitHub orgs are self-published on their homepage, devrel blog, or hiring page. The full list with per-company signal pages is at /signal (filter by sector). We do not track private orgs, leaked employee data, or LinkedIn-inferred profiles.

43 funds in our /fund/ corpus publish databases as part of their stated thesis. Each /fund/[slug] page is an independent summary of the fund's public thesis mapped against our engineering-acceleration signal panel. The corpus is not exhaustive. It is the seed set we built around Marcus 100 (Corp Dev, PE operating partners, non-engineer tech VPs).

Two workflows. (1) Source: weekly digest of databases companies whose engineering acceleration matches your stage and check-size filters, delivered before competitive rounds form (see /firstlook). (2) Validate: given a deal already in your pipeline, retrieve the public engineering trajectory via the public MCP server at /api/v1 or the openapi.json at /api/openapi.json.

No. This is a curated seed corpus, not a Crunchbase-scale database. We add companies, funds, and founders deliberately when they meet our public-source threshold (self-published GitHub handle, public thesis, well-documented role). For the full open-source coverage of every databases startup we score, see /stage/[stage]/database, the scraped leaderboard.