Loading...
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.
This hub aggregates the fintech surface VC Deal Flow Signal tracks: 12 curated companies with public GitHub orgs, 16 venture funds whose published thesis covers fintech, and notable engineering leaders whose work shapes the category. Fintech engineering signals are SDK-density-driven: number of supported languages, depth of language idioms, breadth of platform integrations. Corp Dev teams at incumbents (Visa, Mastercard, Stripe, Adyen) use this to map the acquisition pipeline of API-first challengers. Use it as a starting point for sourcing, diligence, or competitive scans.
13
Tracked companies
16
Active funds
1
Engineering leaders
In fintech 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.
Fintech engineering signals are SDK-density-driven: number of supported languages, depth of language idioms, breadth of platform integrations. Corp Dev teams at incumbents (Visa, Mastercard, Stripe, Adyen) use this to map the acquisition pipeline of API-first challengers.
later · github.com/stripe
later · github.com/plaid
public · github.com/twilio
public · github.com/Adyen
public · github.com/transferwise
public · github.com/nubank
later · github.com/monzo
later · github.com/n26
public · github.com/coinbase
public · github.com/circlefin
later · github.com/alchemyplatform
series b · github.com/privy-io
later · github.com/gusto
Menlo Park · seed through growth across multiple verticals
Menlo Park · seed through growth across multiple geographies
London / San Francisco · seed through Series B across enterprise and consumer
New York · growth-stage software (Series B through public)
Cambridge / San Francisco · seed through growth across multiple verticals
San Francisco · seed and pre-seed across multiple verticals
San Francisco · pre-seed accelerator (batches)
San Francisco · pre-seed and seed globally
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
New York · seed through series A
San Francisco · series A through growth
Hong Kong / London · growth through pre-IPO
We currently track 12 curated fintech 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.
16 funds in our /fund/ corpus publish fintech 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 fintech 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 fintech startup we score, see /stage/[stage]/fintech — 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.
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.
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.
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.