Welcome back, Nikhil
Here's what your accounts are building right now.
Market pulse
What your watchlist shipped and said, week by week
Stack mix
Confirmed infrastructure signals across accounts
| CI/CD | 8 | 14% |
| Containers & K8s | 12 | 21% |
| Cloud & hosting | 16 | 29% |
| Monorepo tooling | 13 | 23% |
| IaC & observability | 7 | 13% |
Live feed
Across every account, newest first
- 4 days
Shipped a release ·
studio v0.34.0 - 4 days
Shipped a release ·
next.js v16.5.0-canary.13 - 4 days
Shipped a release ·
satori 0.59.2 - 4 days
Shipped a release ·
prisma-cli v8.0.0-rc.23 - 5 days
- 5 days
Shipped a release ·
cli 4.9.4 - 5 days
- 5 days
Shipped a release ·
worldwide v1.30.2 - 5 days
Published a post ·
Steer Your Agents Until They Steer Themselves - 5 days
Published a post ·
Findings from the $1M Vercel Sandbox challenge - 6 days
Published a post ·
Amazon S3 joins the Vercel Marketplace - 6 days
- 6 days
Opened a new repo ·
aws-s3-vectors-demo — Amazon S3 Vectors with Next.js and Vercel - 6 days
In the news ·
Shopify opens its catalog up to more AI agents
Leaderboard
Ranked by engineering complexity — click a row to open the account
| # | Account | Stack | Velocity | Eng. hiring | Buying signals | Reply | Complexity |
|---|---|---|---|---|---|---|---|
| 1 |  Vercel @vercel | TypeScriptVercel | High | 30 roles | 6 | — | 98 |
| 2 |  Supabase @supabase | TypeScriptAWS | High | 23 roles | 6 | — | 90 |
| 3 |  HashiCorp @hashicorp | GoKubernetes | High | n/a | 3 | — | 78 |
| 4 |  Prisma @prisma | TypeScriptCloudflare | High | n/a | 3 | — | 75 |
| 5 |  Netflix, Inc. @netflix | JavaKubernetes | High | n/a | 1 | — | 60 |
| 6 |  Shopify @shopify | TypeScript | High | n/a | 2 | — | 59 |
| 7 |  Postman @postmanlabs | JavaScriptCloudflare | High | n/a | 2 | — | 47 |
| 8 |  Notion @notionhq | Objective-CAWS | Low | 37 roles | 5 | — | 29 |
Accounts
Filter by language, cloud & services, velocity or architecture.
Vercel
Vercel builds agentic cloud and frontend infrastructure primarily in TypeScript, JavaScript, and Rust. Engineering is actively expanding marketplace offerings and AI integrations while recruiting across thirty core engineering roles.
Building now · last 30 days
- Vercel CEO Guillermo Rauch Claims White Hat Researcher Breaks Linux Virtualization Boundaries Using AI Agents
News · ababnews.com · 5d ago
- next.js v16.5.0-canary.13
Release · GitHub release · 4d ago
- Triage GitHub Pull Requests with OpenAI's Decisions API
Hacker News · 6 points · 13d ago
Languages
Infrastructure
Hiring signals
Hiring for: Engineering Manager, CDN · Engineering Manager, Dashboard · Engineering Manager - Next.js
Buying signals (6)
- Hiring a "Software Engineer, Agentic Infrastructure" (greenhouse)
- Hiring a "Software Engineer - Data Platform" (greenhouse)
- Hiring a "Software Engineer, Platform" (greenhouse)
- Microservices likely — next.js: 7 Dockerfiles in separate directories
- Monorepo tooling in public code: Turborepo
- 84 GitHub Actions workflow files across its most-starred active public repos
Why it may matter for your product
Observed Hiring a "Software Engineer - Data Platform" (greenhouse)
Hypothesis Expanding foundational platform teams often indicates an emphasis on streamlining internal developer infrastructure and eliminating shared pipeline bottlenecks.
Observed Microservices likely — next.js: 7 Dockerfiles in separate directories
Hypothesis Multi-container services and distributed component setups may lengthen integration test cycles and slow down pull request feedback loops.
Observed Monorepo tooling in public code: Turborepo
Hypothesis Maintaining large monorepos across dozens of active packages can introduce cache invalidation challenges and elongated CI build times.
Unknown What public data can't tell us
- Actual internal CI queue durations and build times are not public.
- Internal code review latency and PR review workloads across teams remain unobservable.
Outreach Hook
“Does open headcount for a Software Engineer - Data Platform prompt questions about whether internal pipeline turnaround and review queues are keeping pace with delivery demands?”
Buying signal (friction raised only as a question): Hiring a "Software Engineer - Data Platform" (greenhouse)
Supabase
Supabase builds an open-source Postgres development platform primarily in TypeScript and Elixir, while actively expanding its engineering organization around AI and managed database infrastructure following a 150 million dollar raise and the acquisition of Turso.
Building now · last 30 days
- Supabase Raises $150M, Agrees to Buy Turso
News · Quasa.io · 10d ago
- storage v1.81.1
Release · GitHub release · 7d ago
- Supabase is acquiring Turso
Hacker News · 221 points · 17d ago
Languages
Infrastructure
Hiring signals
Hiring for: AI Platform Engineer · Multigres Engineer · Postgres Engineer (AMER)
Buying signals (6)
Why it may matter for your product
Observed Hiring an AI Platform Engineer and 22 other engineering roles
Hypothesis Onboarding multiple engineers into specialized platform tracks could increase code review bottlenecks and pull request cycle times across shared repositories.
Observed supabase repo contains 4 Dockerfiles in separate directories and 8 deployable units under apps/
Hypothesis Maintaining multiple deployable units in monorepos alongside tools like Turborepo and Nx may lead to prolonged CI feedback loops and build caching overhead.
Unknown What public data can't tell us
- Actual CI build and test execution times across their 104 workflow files are not publicly disclosed.
- Internal code review turnaround times and context-switching metrics for their core engineering teams are unknown.
Outreach Hook
“Curious whether your open AI Platform Engineer search reflects plans to isolate AI services, and how that impacts review queues across your shared monorepos.”
Buying signal (friction raised only as a question): Hiring a "AI Platform Engineer" (ashby)
HashiCorp
HashiCorp builds infrastructure automation software with a public stack heavily centered on Go (64.5%) and GitHub Actions. Engineering is currently shipping updates across its provider and orchestrator ecosystem, including recent releases for Terraform providers and Nomad.
Building now · last 30 days
- HashiCorp Releases Terraform Google Cloud Provider 8.0 in General Availability
News · news.lavx.hu · 10d ago
- terraform-provider-tfe v0.82.0
Release · GitHub release · 11d ago
- Terraform 1.16 completes Actions lifecycles and brings imports into child modules
Blog · Company blog · 21d ago
Languages
Infrastructure
Hiring signals
Buying signals (3)
Why it may matter for your product
Observed consul: 4 Dockerfiles in separate directories
Hypothesis Maintaining multiple container configurations across decoupled components can increase test execution overhead, which build acceleration tools often help mitigate.
Observed 170 GitHub Actions workflow files
Hypothesis Managing an extensive suite of workflow files may result in pipeline bottlenecks and lengthened review cycles as test matrices expand.
Observed nomad: pnpm-workspace.yaml
Hypothesis Monorepo workspace structures often introduce dependency resolution latency, where optimized build caching could improve developer feedback loops.
Unknown What public data can't tell us
- Actual CI build durations and pipeline queue times in GitHub Actions are not publicly visible.
- Internal code review turnaround times and developer wait times remain unknown.
- Whether HashiCorp already utilizes internal build caching or remote execution tooling cannot be verified from public data.
Outreach Hook
“Consul's multiple Dockerfiles and Protobuf contracts suggest distributed service boundaries, prompting curiosity whether cross-service integration testing creates bottlenecks in your team's pull request reviews.”
Buying signal (friction raised only as a question): Microservices likely — consul: 4 Dockerfiles in separate directories
Prisma builds database infrastructure and ORM tooling primarily in TypeScript and Rust, currently driving high release velocity across Prisma ORM 8 release candidates and multi-package monorepos.
Building now · last 30 days
- studio v0.34.0
Release · GitHub release · 4d ago
- We closed 330 of your most-requested issues with Prisma ORM 8
Blog · Company blog · 8d ago
Languages
Infrastructure
Hiring signals
Buying signals (3)
Why it may matter for your product
Observed prisma-engines: 3 Dockerfiles in separate directories
Hypothesis Maintaining independent container definitions across multi-container services often increases image build overhead and lengthens CI feedback loops.
Observed web: depends on turbo
Hypothesis Adopting Turborepo in monorepos indicates that optimizing task orchestration and build caching may be an active engineering focus.
Unknown What public data can't tell us
- Internal CI duration and runner wait times across GitHub Actions workflows are not publicly available.
- The extent of remote build caching adoption between local environments and CI is unknown.
Outreach Hook
“Curious whether maintaining multiple Dockerfiles across repositories like prisma-engines introduces container build caching bottlenecks or integration test delays across your daily CI runs?”
Buying signal (friction raised only as a question): Microservices likely — prisma-engines: 3 Dockerfiles in separate directories
Netflix, Inc.
Netflix builds large-scale streaming and developer platform services predominantly in Java and Python. Their open source organization is actively shipping workflow tools like Maestro and Java tooling like jig, alongside ML infrastructure like Metaflow.
Building now · last 30 days
- You've already ingested AI-generated content, boasts Netflix exec
News · A.V. Club · 8d ago
- jig v0.17.0
Release · GitHub release · 8d ago
Languages
Infrastructure
Hiring signals
No public Greenhouse, Lever, Ashby, Workable or Recruitee board found. Set jobs_board (e.g. greenhouse:acme) in Supabase to add one.
Buying signals (1)
Why it may matter for your product
Observed 30 GitHub Actions workflow files across its most-starred active public repos
Hypothesis A high volume of workflow configurations across multi-language projects may introduce build queuing and prolonged feedback loops for developers.
Observed New repos in the last 120 days include jdocserver, jist, jfmt, jig, and ja
Hypothesis Sustained engineering investment in custom Java tooling could indicate an internal focus on resolving developer productivity frictions.
Unknown What public data can't tell us
- Actual CI build times and queue durations are not publicly visible.
- Internal CI and CD infrastructure used for production services may differ from public GitHub Actions workflows.
Outreach Hook
“Across Netflix's active open source repositories utilizing 30 GitHub Actions workflow files, curious whether CI wait times or pipeline feedback loops are impacting developer velocity on core tools.”
Buying signal (friction raised only as a question): 30 GitHub Actions workflow files across its most-starred active public repos
Shopify
Shopify builds commerce primitives, CLI developer tools, and merchant platforms, led by TypeScript (76%) and Ruby (12%) in public repos. Engineering is currently expanding AI agent integrations and migrating mobile applications from React Native to native platforms.
Building now · last 30 days
- Shopify opens its catalog up to more AI agents
News · The Verge · 6d ago
- cli 4.9.4
Release · GitHub release · 5d ago
- ShopGym: Realistic, reproducible sandboxes for shopping agents
Blog · Company blog · 18d ago
Languages
Infrastructure
Hiring signals
Buying signals (2)
Why it may matter for your product
Observed Monorepo tooling in public code: Turborepo
Hypothesis Using Turborepo in repositories like hydrogen indicates multi-package build graphs, where task execution and caching efficiency may impact developer feedback loops.
Observed 36 GitHub Actions workflow files across its most-starred active public repos
Hypothesis A substantial footprint of workflow automation across public projects may create CI queue bottlenecks and test orchestration overhead during frequent pushes.
Unknown What public data can't tell us
- Actual CI build times and test run durations are not publicly visible.
- Internal adoption of Turborepo beyond public projects like hydrogen is unconfirmed.
- Active engineering job openings cannot be determined from their public listings.
Outreach Hook
“Turborepo configurations in the hydrogen repository suggest complex multi-package builds, raising the question of whether build caching and task execution bottlenecks are slowing down your pull request cycles.”
Buying signal (friction raised only as a question): Monorepo tooling in public code: Turborepo
Postman
Postman builds an API collaboration platform with public repositories dominated by JavaScript (79.6%) and Go (15.4%). Engineering is heavily focused on expanding AI agent capabilities and integrating cloud performance testing into continuous integration workflows.
Building now · last 30 days
- Postman Agent Mode on Amazon Bedrock Explained
News · NeoTeo · 9d ago
- postman-insights-agent v0.41.0
Release · GitHub release · 11d ago
- passport-skills
New repo · Shell · 13d ago
Languages
Infrastructure
Hiring signals
Buying signals (2)
Why it may matter for your product
Observed Blog: "Cloud Performance Testing with Postman: From Laptop to CI"
Hypothesis Pushing comprehensive performance testing into continuous integration could increase pipeline execution times and delay developer feedback loops.
Observed schemas: pnpm-workspace.yaml
Hypothesis Maintaining monorepo architectures with pnpm Workspaces often leads to complex dependency graphs that may slow down continuous integration builds if caching is unoptimized.
Unknown What public data can't tell us
- Internal continuous integration cycle times and feedback wait times across proprietary repositories are not publicly documented.
- Actual developer context-switching metrics and pull request review turnaround times inside the organization remain unobservable from public data.
Outreach Hook
“Having adopted pnpm Workspaces in your public schemas repo, how is your engineering team keeping package build and test runtimes down during continuous integration checks?”
Notion
Notion builds collaborative workspace software with hiring showing heavy demand for Python and TypeScript across AWS, GCP, and Azure. Engineering is currently recruiting across 37 open technical positions, including dedicated developer platform and infrastructure roles.
Building now · last 30 days
- Why Notion Focuses on Context Foundation, Not AI Agents
News · ASCII.jp · 12d ago
Languages
Infrastructure
Hiring signals
Hiring for: Software Engineer, Developer Platform · Forward Deployed Engineer, GTM, AMER · Engineering Manager, Mobile AI
Buying signals (5)
Why it may matter for your product
Observed Hiring a "Software Engineer, Developer Platform" (ashby)
Hypothesis Dedicated developer platform hiring often indicates an internal focus on reducing build bottlenecks and developer turnaround times.
Observed Jobs: 4 of 37 engineering postings mention microservices/distributed systems
Hypothesis Distributed architectures may introduce complex integration pipelines that increase CI wait times.
Unknown What public data can't tell us
- Internal CI build and code review cycle times are not publicly available.
- Actual production CI and deployment tooling cannot be confirmed from public repositories alone.
Outreach Hook
“Does your search for a Software Engineer on the Developer Platform team indicate internal initiatives to reduce CI cycle times and streamline engineering review workflows?”
Buying signal (friction raised only as a question): Hiring a "Software Engineer, Developer Platform" (ashby)