DevGlobe

🌐 DevGlobe

The open-source talent graph for humans and AI agents.

*26,000+ developers · ranked by stars, commits, repo reach & StackOverflow reputation · searchable by skill, location & language*

DevGlobe is the open-source talent graph for humans and AI agents. It combines a 3D developer map with Azure Cosmos DB vector and hybrid search to surface relevant expertise from real contribution signals rather than popularity alone. The long-term vision is a consent-aware discovery layer where AI agents can find the right human collaborators.

The dynamic application is hosted on Azure Container Apps. Product, API, MCP, Agent Skill, and agent-readiness documentation is published separately on GitHub Pages.

[!IMPORTANT]

Connect an AI agent to DevGlobe: MCP-compatible agents can use the hosted endpoint at https://www.devglobe.dev/mcp to search public developer profiles without credentials. Verified agents can also request developer-approved introductions. See the MCP setup guide.

Show up while you code: Install DevGlobe: Live Coding Globe, choose Go Live, and appear on the globe while building private coding stats. The extension never reads source code, file paths, repositories, branches, or keystrokes.

🎬 Watch the DevGlobe Demo

DevGlobe: The Open-Source Talent Graph for Humans and AI Agents

---

✨ Features

• Interactive 3D Globe — Explore developers pinned to their real-world locations using Three.js
• AI-Powered Search — Hybrid + vector search via Azure Cosmos DB (e.g. "AI & deep learning", "full stack JS dev")
• Composite Scoring — Each developer scored 0–100 across 6 dimensions
• Leaderboard — Filter by country, language, or sort by score/stars/commits
• Developer Profiles — Click any pin to see detailed stats, top repos, and contribution breakdown
• Remote MCP Access — Agents can discover developers and request consent-gated introductions through hosted tools
• VS Code Extension — Go live on the developer globe, build private coding stats, search developers, and configure MCP from the editor
• Mobile Responsive — Bottom-sheet filters and full-width search on smaller screens

🚀 Quick Start

Option 1: Zero-config (sample data, no database needed)

git clone https://github.com/sajeetharan/devglobe.git

cd devglobe npm install npm run dev

Open http://localhost:3000

The app automatically falls back to the bundled sample data (20 developers) when no Cosmos DB credentials are configured. No API keys, no emulator, no setup — just clone and run.

Text search works fully offline. Vector/hybrid search requires Azure OpenAI (see Option 3).

---

Option 2: Cosmos DB Emulator (full database experience locally)

For contributors working on the API layer or data pipeline:

1. Install the Cosmos DB Emulator — Download here (Windows, macOS via Docker, or Linux Docker)

1. Start the emulator and wait for it to be ready at https://localhost:8081

1. Seed sample data into the emulator:

   npm run seed-emulator

1. Create `.env.local` (the seed script prints this for you):

   COSMOS_ENDPOINT=https://localhost:8081

COSMOS_KEY=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==

1. Run the app:

   npm run dev

The emulator key above is Microsoft's well-known emulator key — it is intentionally public and only works locally.

---

Option 3: Full Azure backend (vector + hybrid search)

For the complete experience including AI-powered search:

# .env.local

COSMOS_ENDPOINT=https://your-account.documents.azure.com:443/ COSMOS_KEY=your-cosmos-key AZURE_OPENAI_ENDPOINT=https://your-openai.openai.azure.com/ AZURE_OPENAI_KEY=your-openai-key EMBEDDING_DEPLOYMENT=text-embedding-3-small AZURE_OPENAI_CHAT_DEPLOYMENT=gpt-4o-mini

AZURE_OPENAI_CHAT_DEPLOYMENT enables generated fun facts on identity cards. Cards use factual profile copy when the chat deployment is unavailable.

Production serves the Next.js application from Azure Container Apps, high-volume public API reads from Azure Functions, and the developer snapshot from Azure Blob Storage. See docs/azure-backend.md for the resource layout, environment switches, and deployment checks.

npm run dev

🏗️ Tech Stack

📊 Scoring Formula (0–100)

All dimensions are log-normalized to prevent outlier domination.

🔧 Building the Full Dataset

Requires API keys — copy .env.example to .env and fill in your tokens.

npm run fetch-github          # Fetch top devs from GitHub GraphQL

npm run fetch-stackoverflow # Enrich with StackOverflow reputation npm run geocode # Convert locations to lat/lng npm run build-data # Run full pipeline npm run upload-cosmos # Upload to Azure Cosmos DB

Developer credentials

Verified community credentials are stored explicitly on each developer document. Do not infer them from stars, followers, or profile text.

{

"login": "example", "specialTags": ["github-star", "microsoft-mvp", "aws-community-builder"] }

Supported IDs: github-star, microsoft-mvp, google-developer-expert, docker-captain, cncf-ambassador, aws-hero, and aws-community-builder. The legacy docker-champion ID remains supported. The upload script preserves this field from source JSON, and the list, detail, and search APIs project it from Cosmos DB.

Populate exact GitHub-login matches from the official GitHub Stars, Google Developer Experts, and CNCF Ambassadors rosters:

npm run populate-special-tags             # Dry run

npm run populate-special-tags -- --apply # Patch verified matches in Cosmos DB

The command preserves existing tags and is idempotent. Other credentials require an official profile that explicitly identifies the developer's GitHub account; do not populate them by matching display names.

📁 Project Structure

├── index.html                  # Entry HTML

├── src/ │ ├── main.jsx # Application bootstrap │ ├── App.jsx # Root component, data loading │ ├── components/ │ │ ├── Globe.jsx # 3D globe (react-globe.gl) │ │ ├── Leaderboard.jsx # Ranked sidebar with filters │ │ ├── SearchBar.jsx # Hybrid/vector search input │ │ ├── DetailPanel.jsx # Developer detail card │ │ ├── Header.jsx # Top bar with branding │ │ └── LoadingOverlay.jsx # Loading state │ └── utils/ │ ├── scoring.js # Composite scoring algorithm │ └── format.js # Number formatting helpers ├── api/ │ ├── developers.js # List all developers │ ├── developer.js # Single developer lookup │ └── search.js # Cosmos DB vector/hybrid search ├── scripts/ # Data pipeline scripts ├── styles/main.css # Dark theme styles └── data/ └── developers-sample.json # Sample data for local dev

🌍 Deploy to Azure Container Apps

Pushes to main build the standalone Next.js image in Azure Container Registry and deploy it to Azure Container Apps through GitHub Actions OIDC. The deployment identity requires Contributor access scoped to the application resource group and these repository variables: AZURE_CLIENT_ID, AZURE_TENANT_ID, and AZURE_SUBSCRIPTION_ID.

Required environment variables:

Lifecycle emails are transactional and best-effort. Claims use the verified primary email authorized through GitHub OAuth; self-nominations collect an explicitly consented notification address. Addresses are stored only in the private developer-contacts container and are never projected by public APIs or copied into developer documents. Create the container before deployment:

npm run setup-contacts-container

See the [lifecycle email PRD](docs/prd/lifecycle-email-not