Loading...
OLTP, OLAP, vector stores, embedded engines, and the storage layer underneath every modern app. A single page mapping who builds, who funds, and who leads in databases.
This hub aggregates the databases surface VC Deal Flow Signal tracks: 20 curated companies with public GitHub orgs, 43 venture funds whose published thesis covers databases, and notable engineering leaders whose work shapes the category. Database companies show the most distinctive language-bias signature: Rust + C/C++ dominance with occasional Go infrastructure layers. Acceleration in this sector is typically tied to a new storage primitive (columnar, vector, time-series) shipping behind a public benchmark. Emerging-manager funds scout here for picks-and-shovels AI plays. Use it as a starting point for sourcing, diligence, or competitive scans.
32
Tracked companies
43
Active funds
0
Engineering leaders
In databases we track four engineering-acceleration primitives across every monitored org: commit velocity (rolling 14-day vs trailing 12-week median), contributor influx (new committers in the trailing 4 weeks), repo creation pulse (new public repos shipped in the trailing 8 weeks), and language-bias drift (when a new primary language appears in production code). The six-signal panel published at /methodology is empirically tied to imminent fundraise probability — see SSRN paper 6606558.
Database companies show the most distinctive language-bias signature: Rust + C/C++ dominance with occasional Go infrastructure layers. Acceleration in this sector is typically tied to a new storage primitive (columnar, vector, time-series) shipping behind a public benchmark. Emerging-manager funds scout here for picks-and-shovels AI plays.
series c · github.com/supabase
series b · github.com/get-convex
series c · github.com/neondatabase
series b · github.com/prisma
seed · github.com/drizzle-team
series a · github.com/upstash
series a · github.com/tursodatabase
series c · github.com/planetscale
public · github.com/mongodb
public · github.com/elastic
series c · github.com/ClickHouse
later · github.com/dbt-labs
seed · github.com/duckdb
later · github.com/redis
public · github.com/MariaDB
public · github.com/couchbase
series c · github.com/timescale
series b · github.com/meilisearch
seed · github.com/typesense
series b · github.com/weaviate
series a · github.com/qdrant
series b · github.com/milvus-io
series b · github.com/pinecone-io
later · github.com/cockroachdb
later · github.com/influxdata
later · github.com/dremio
seed · github.com/voyage-ai
series a · github.com/jina-ai
later · github.com/fivetran
series b · github.com/airbytehq
series b · github.com/cube-js
series a · github.com/run-llama
Menlo Park · seed through growth, AI and enterprise software-heavy
Menlo Park · seed through growth across multiple verticals
San Francisco · early-stage (Series A primarily)
San Francisco · seed through growth, contrarian-thesis
Menlo Park · seed through Series B in enterprise and AI
Menlo Park · seed through growth across multiple geographies
Palo Alto · seed through Series B across multiple geographies
Menlo Park · seed through growth, vertical-software-heavy
London / San Francisco · seed through Series B across enterprise and consumer
San Francisco · growth-stage enterprise software primarily
New York · growth through public
New York · growth-stage software (Series B through public)
Cambridge / San Francisco · seed through growth across multiple verticals
Menlo Park · seed through growth across tech and healthcare
Mountain View · seed through Series C across life sciences and tech
San Francisco · pre-seed and seed
San Francisco · seed (rare Series A)
San Francisco · seed and pre-seed
Palo Alto · pre-seed and seed
Distributed · pre-seed (tournament-based sourcing)
San Francisco · pre-seed accelerator (batches)
Distributed (city programs) · pre-seed accelerator
San Francisco · pre-seed and seed globally
San Francisco · pre-seed and seed across verticals
San Francisco · seed primarily
San Francisco · seed primarily
San Francisco · pre-seed
New York · growth through pre-IPO
New York · series A through growth
Palo Alto · seed through pre-IPO
Boston · seed through growth
San Francisco · seed through growth
Menlo Park · seed through growth
San Mateo · series A through growth
New York · seed through series A
San Francisco · series A through growth
Menlo Park · growth through pre-IPO
Seattle · series A through growth
Santa Clara · seed through growth
San Francisco · series A through growth
Denver · pre-seed through Series A, gaming and interactive entertainment
Denver · seed through Series B, gaming and synthetic reality
San Francisco · pre-seed through Series A, interactive entertainment
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.
Compute, orchestration, inference, and the serving layer underneath the model providers. A single page mapping who builds, who funds, and who leads in ai infrastructure.
Frontier labs, model providers, open-weight checkpoints, and the applied-AI layer on top. A single page mapping who builds, who funds, and who leads in ai & machine learning.
IDEs, frameworks, build systems, package managers, and the productivity layer engineers actually touch. A single page mapping who builds, who funds, and who leads in developer tools.
Edge platforms, runtimes, networking, observability primitives, and the platform-as-a-service layer. A single page mapping who builds, who funds, and who leads in cloud infrastructure.
Logs, traces, metrics, error tracking, profiling, and the runtime-visibility surface for engineering orgs. A single page mapping who builds, who funds, and who leads in observability & monitoring.
Warehousing, transformation, BI, and the analyst-facing query surface on top of operational data. A single page mapping who builds, who funds, and who leads in data analytics.
Payments, banking infrastructure, embedded finance, fraud, and the API surface for financial workflows. A single page mapping who builds, who funds, and who leads in fintech.
Documents, collaboration, knowledge management, and the prosumer + team productivity layer. A single page mapping who builds, who funds, and who leads in productivity & knowledge work.
Game backends, multiplayer servers, server orchestration, cross-game avatars, and the live-ops layer beneath studios. A single page mapping who builds, who funds, and who leads in gaming infrastructure.
The free Acceleration Watch: five venture-backed teams accelerating on the engineering signal, translated into plain English — 21 to 47 days before the deck circulates. No code-reading, no card.