Engineering acceleration & VC anchors at the developer tools × San Francisco intersection.
This page is the editorial composition of two of our hubs: /sector/developer-tools (the curated sector hub) and /city/san-francisco (the local engineering scene). Use it as the lens for readingdeveloper tools signal in San Francisco — local commit cadence, active VCs, scouting context. Live data resolves to coarse continents; this intersection is the editorial reading frame.
Bay Area commits run 09:00–11:00 PST with a sharp second peak between 22:00 and 01:00 PST (founder hours). The signal that consistently leads is *Sunday-night infra commits* — when a frontier-AI org's deploy infrastructure gets a flurry of commits Sunday 21:00–23:00 PST, a Tuesday-morning launch tends to follow.
For broader developer tools interpretation: Developer tools have the cleanest commit-velocity signal because their entire product is the GitHub org. Acceleration shows up as repo creation pulse: new SDK languages, new integrations, new templates. Tech VPs scanning for tooling consolidation use this hub to map vendor density across their stack.
San Francisco is the global high-water mark for code-side engineering signals. Every signal type in the panel reaches its highest absolute values here. The trade-off: the false-positive rate is also the highest (28% in 2025–2026 vs the global median of 22%), because the noise floor of 'launch-week sprint commits' is so loud.
The actual developer tools × San Francisco intersection from our curated company-location map — verified primary-HQ companies, not just cross-sector cross-link aggregation.
later · github.com/vercel
series a · github.com/resend
series c · github.com/linear
series b · github.com/get-convex
series c · github.com/neondatabase
later · github.com/anthropics
later · github.com/openai
later · github.com/stripe
public · github.com/cloudflare
public · github.com/hashicorp
later · github.com/getsentry
seed · github.com/drizzle-team
series b · github.com/clerk
series a · github.com/browserbase
seed · github.com/e2b-dev
series a · github.com/railwayapp
series a · github.com/upstash
series a · github.com/tursodatabase
series b · github.com/stytchauth
series b · github.com/workos
series b · github.com/getcursor
seed · github.com/shadcn-ui
series b · github.com/langchain-ai
seed · github.com/crewAIInc
seed · github.com/letta-ai
seed · github.com/mastra-ai
later · github.com/figma
later · github.com/plaid
public · github.com/twilio
later · github.com/netlify
later · github.com/sourcegraph
later · github.com/dbt-labs
public · github.com/couchbase
seed · github.com/typesense
series b · github.com/oven-sh
series b · github.com/denoland
public · github.com/amplitude
later · github.com/mixpanel
series c · github.com/metabase
series c · github.com/wandb
Broader developer tools roster (not necessarily San Francisco-HQ'd). Use as the cross-reference set when evaluating local San Francisco engineering signals.
Drill into live data
For the live continent-level developer tools signal panel covering North America, see /startups-to-watch/region/us. Combine with the San Francisco signal pattern above to weight local relevance.
Bay Area commits run 09:00–11:00 PST with a sharp second peak between 22:00 and 01:00 PST (founder hours). The signal that consistently leads is *Sunday-night infra commits* — when a frontier-AI org's deploy infrastructure gets a flurry of commits Sunday 21:00–23:00 PST, a Tuesday-morning launch tends to follow. San Francisco is the global high-water mark for code-side engineering signals. Every signal type in the panel reaches its highest absolute values here. The trade-off: the false-positive rate is also the highest (28% in 2025–2026 vs the global median of 22%), because the noise floor of 'launch-week sprint commits' is so loud.
Sequoia, a16z, Founders Fund, Greylock, Benchmark are the publicly identifiable venture firms with named partners and an active engineering-aware lens in San Francisco. We do not claim these funds focus exclusively on developer tools — the list is editorial inference from their published thesis material.
Vercel, Resend, Linear, Convex, Neon, Anthropic, OpenAI, Stripe, Cloudflare, HashiCorp, Sentry, Drizzle, Clerk, Browserbase, E2B, Railway, Upstash, Turso, Stytch, WorkOS, Cursor, shadcn, LangChain, CrewAI, Letta, Mastra, Figma, Plaid, Twilio, Netlify, Sourcegraph, dbt Labs, Couchbase, Typesense, Bun, Deno, Amplitude, Mixpanel, Metabase, Weights & Biases are tracked developer tools companies HQ'd in or near San Francisco per our company-location map. The broader sector roster is at /sector/developer-tools.
San Francisco is the global high-water mark for code-side engineering signals. Every signal type in the panel reaches its highest absolute values here. The trade-off: the false-positive rate is also the highest (28% in 2025–2026 vs the global median of 22%), because the noise floor of 'launch-week sprint commits' is so loud. For developer tools specifically: Developer tools have the cleanest commit-velocity signal because their entire product is the GitHub org. Acceleration shows up as repo creation pulse: new SDK languages, new integrations, new templates. Tech VPs scanning for tooling consolidation use this hub to map vendor density across their stack.
The public dataset resolves to coarse continents (US, EU, APAC, LATAM, Canada). For San Francisco, the relevant live panel is /startups-to-watch/region/us. This intersection page is the editorial lens through which to read that continent panel for developer tools-focused queries in San Francisco.
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.