Corporate GitHub Activity
Most Active Corporations on GitHub, 11 2025
Ranking companies with employees who, during 11 2025, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. ClickHouse | 43% 43% (n=76) of all ClickHouse engineers (n=1771) were active on GitHub. | 18% 18% (n=76) of all ClickHouse employees (n=4152) were active on GitHub. | 76 76 ClickHouse employees were active on GitHub. |
|---|---|---|---|
| 2. Sentry.io | 40% 40% (n=76) of all Sentry.io engineers (n=1883) were active on GitHub. | 18% 18% (n=76) of all Sentry.io employees (n=4264) were active on GitHub. | 76 76 Sentry.io employees were active on GitHub. |
| 3. Vercel | 36% 36% (n=79) of all Vercel engineers (n=2205) were active on GitHub. | 11% 11% (n=79) of all Vercel employees (n=7316) were active on GitHub. | 79 79 Vercel employees were active on GitHub. |
| 4. Grafana Labs | 30% 30% (n=197) of all Grafana Labs engineers (n=6497) were active on GitHub. | 12% 12% (n=197) of all Grafana Labs employees (n=1,5918) were active on GitHub. | 197 197 Grafana Labs employees were active on GitHub. |
| 5. Automattic | 23% 23% (n=159) of all Automattic engineers (n=6799) were active on GitHub. | 18% 18% (n=159) of all Automattic employees (n=88710) were active on GitHub. | 159 159 Automattic employees were active on GitHub. |
| 6. Elastic | 21% 21% (n=278) of all Elastic engineers (n=1,32211) were active on GitHub. | 8% 8% (n=278) of all Elastic employees (n=3,53712) were active on GitHub. | 278 278 Elastic employees were active on GitHub. |
| 7. Kitware | 20% 20% (n=20) of all Kitware engineers (n=9913) were active on GitHub. | 13% 13% (n=20) of all Kitware employees (n=15314) were active on GitHub. | 20 20 Kitware employees were active on GitHub. |
| 8. SUSE | 19% 19% (n=136) of all SUSE engineers (n=71815) were active on GitHub. | 5% 5% (n=136) of all SUSE employees (n=2,66316) were active on GitHub. | 136 136 SUSE employees were active on GitHub. |
| 9. Docker | 18% 18% (n=35) of all Docker engineers (n=19417) were active on GitHub. | 4% 4% (n=35) of all Docker employees (n=94118) were active on GitHub. | 35 35 Docker employees were active on GitHub. |
| 10. Mozilla | 17% 17% (n=107) of all Mozilla engineers (n=64819) were active on GitHub. | 6% 6% (n=107) of all Mozilla employees (n=1,74920) were active on GitHub. | 107 107 Mozilla employees were active on GitHub. |
| 11. Tenstorrent | 14% 14% (n=88) of all Tenstorrent engineers (n=61621) were active on GitHub. | 8% 8% (n=88) of all Tenstorrent employees (n=1,07422) were active on GitHub. | 88 88 Tenstorrent employees were active on GitHub. |
| 12. JetBrains | 12% 12% (n=133) of all JetBrains engineers (n=1,15523) were active on GitHub. | 6% 6% (n=133) of all JetBrains employees (n=2,24524) were active on GitHub. | 133 133 JetBrains employees were active on GitHub. |
| 13. Cloudflare | 9% 9% (n=94) of all Cloudflare engineers (n=1,10525) were active on GitHub. | 2% 2% (n=94) of all Cloudflare employees (n=4,26326) were active on GitHub. | 94 94 Cloudflare employees were active on GitHub. |
| 14. DataDog | 7% 7% (n=211) of all DataDog engineers (n=3,10027) were active on GitHub. | 3% 3% (n=211) of all DataDog employees (n=6,50028) were active on GitHub. | 211 211 DataDog employees were active on GitHub. |
| 15. WSO2 | 6% 6% (n=45) of all WSO2 engineers (n=69429) were active on GitHub. | 4% 4% (n=45) of all WSO2 employees (n=1,16930) were active on GitHub. | 45 45 WSO2 employees were active on GitHub. |
| 16. MongoDB | 6% 6% (n=85) of all MongoDB engineers (n=1,32731) were active on GitHub. | 2% 2% (n=85) of all MongoDB employees (n=5,55832) were active on GitHub. | 85 85 MongoDB employees were active on GitHub. |
| 17. Mapbox | 4% 4% (n=14) of all Mapbox engineers (n=32533) were active on GitHub. | 2% 2% (n=14) of all Mapbox employees (n=83834) were active on GitHub. | 14 14 Mapbox employees were active on GitHub. |
| 18. Snyk | 4% 4% (n=20) of all Snyk engineers (n=46935) were active on GitHub. | 2% 2% (n=20) of all Snyk employees (n=1,27436) were active on GitHub. | 20 20 Snyk employees were active on GitHub. |
| 19. Shopify | 2% 2% (n=98) of all Shopify engineers (n=4,39237) were active on GitHub. | 1% 1% (n=98) of all Shopify employees (n=8,10038) were active on GitHub. | 98 98 Shopify employees were active on GitHub. |
| 20. Odoo | 2% 2% (n=21) of all Odoo engineers (n=96639) were active on GitHub. | 0% 0% (n=21) of all Odoo employees (n=6,65140) were active on GitHub. | 21 21 Odoo employees were active on GitHub. |
| 21. Microsoft | 2% 2% (n=1,717) of all Microsoft engineers (n=80,00041) were active on GitHub. | 1% 1% (n=1,717) of all Microsoft employees (n=228,00042) were active on GitHub. | 1,717 1,717 Microsoft employees were active on GitHub. |
| 22. Confluent | 2% 2% (n=29) of all Confluent engineers (n=1,36343) were active on GitHub. | 1% 1% (n=29) of all Confluent employees (n=3,06044) were active on GitHub. | 29 29 Confluent employees were active on GitHub. |
| 23. Nebius Group | 2% 2% (n=15) of all Nebius Group engineers (n=73145) were active on GitHub. | 1% 1% (n=15) of all Nebius Group employees (n=1,37146) were active on GitHub. | 15 15 Nebius Group employees were active on GitHub. |
| 24. Snowflake, Inc. | 2% 2% (n=46) of all Snowflake, Inc. engineers (n=2,25747) were active on GitHub. | 1% 1% (n=46) of all Snowflake, Inc. employees (n=7,83448) were active on GitHub. | 46 46 Snowflake, Inc. employees were active on GitHub. |
| 25. Okta | 2% 2% (n=34) of all Okta engineers (n=1,79949) were active on GitHub. | 1% 1% (n=34) of all Okta employees (n=5,91450) were active on GitHub. | 34 34 Okta employees were active on GitHub. |
| 26. Progress Software | 2% 2% (n=18) of all Progress Software engineers (n=1,05551) were active on GitHub. | 1% 1% (n=18) of all Progress Software employees (n=2,81552) were active on GitHub. | 18 18 Progress Software employees were active on GitHub. |
| 27. NVIDIA | 2% 2% (n=456) of all NVIDIA engineers (n=27,10053) were active on GitHub. | 1% 1% (n=456) of all NVIDIA employees (n=36,00054) were active on GitHub. | 456 456 NVIDIA employees were active on GitHub. |
| 28. New Relic | 2% 2% (n=18) of all New Relic engineers (n=1,08855) were active on GitHub. | 1% 1% (n=18) of all New Relic employees (n=2,92356) were active on GitHub. | 18 18 New Relic employees were active on GitHub. |
| 29. Alibaba | 1% 1% (n=146) of all Alibaba engineers (n=9,83157) were active on GitHub. | 0% 0% (n=146) of all Alibaba employees (n=126,66158) were active on GitHub. | 146 146 Alibaba employees were active on GitHub. |
| 30. Arm Ltd | 1% 1% (n=98) of all Arm Ltd engineers (n=6,94359) were active on GitHub. | 1% 1% (n=98) of all Arm Ltd employees (n=8,33060) were active on GitHub. | 98 98 Arm Ltd employees were active on GitHub. |
| 31. ESRI | 1% 1% (n=28) of all ESRI engineers (n=2,25861) were active on GitHub. | 0% 0% (n=28) of all ESRI employees (n=7,01162) were active on GitHub. | 28 28 ESRI employees were active on GitHub. |
| 32. Databricks | 1% 1% (n=71) of all Databricks engineers (n=5,74763) were active on GitHub. | 1% 1% (n=71) of all Databricks employees (n=13,67964) were active on GitHub. | 71 71 Databricks employees were active on GitHub. |
| 33. Amazon | 1% 1% (n=586) of all Amazon engineers (n=49,92065) were active on GitHub. | 0% 0% (n=586) of all Amazon employees (n=146,76466) were active on GitHub. | 586 586 Amazon employees were active on GitHub. |
| 34. AMD | 1% 1% (n=230) of all AMD engineers (n=19,69767) were active on GitHub. | 1% 1% (n=230) of all AMD employees (n=28,00068) were active on GitHub. | 230 230 AMD employees were active on GitHub. |
| 35. Adobe | 1% 1% (n=125) of all Adobe engineers (n=11,21369) were active on GitHub. | 0% 0% (n=125) of all Adobe employees (n=30,70970) were active on GitHub. | 125 125 Adobe employees were active on GitHub. |
| 36. Google | 1% 1% (n=874) of all Google engineers (n=81,83771) were active on GitHub. | 0% 0% (n=874) of all Google employees (n=183,32372) were active on GitHub. | 874 874 Google employees were active on GitHub. |
| 37. Stripe | 1% 1% (n=32) of all Stripe engineers (n=3,81673) were active on GitHub. | 0% 0% (n=32) of all Stripe employees (n=12,04974) were active on GitHub. | 32 32 Stripe employees were active on GitHub. |
| 38. Tencent | 1% 1% (n=110) of all Tencent engineers (n=13,12475) were active on GitHub. | 0% 0% (n=110) of all Tencent employees (n=110,55876) were active on GitHub. | 110 110 Tencent employees were active on GitHub. |
| 39. BBC | 1% 1% (n=18) of all BBC engineers (n=2,18877) were active on GitHub. | 0% 0% (n=18) of all BBC employees (n=21,50878) were active on GitHub. | 18 18 BBC employees were active on GitHub. |
| 40. OpenAI | 1% 1% (n=23) of all OpenAI engineers (n=2,84979) were active on GitHub. | 0% 0% (n=23) of all OpenAI employees (n=9,91580) were active on GitHub. | 23 23 OpenAI employees were active on GitHub. |
| 41. Netflix | 1% 1% (n=23) of all Netflix engineers (n=2,95781) were active on GitHub. | 0% 0% (n=23) of all Netflix employees (n=14,00082) were active on GitHub. | 23 23 Netflix employees were active on GitHub. |
| 42. ThoughtWorks | 1% 1% (n=28) of all ThoughtWorks engineers (n=3,81683) were active on GitHub. | 0% 0% (n=28) of all ThoughtWorks employees (n=10,50084) were active on GitHub. | 28 28 ThoughtWorks employees were active on GitHub. |
| 43. Unity Technologies | 1% 1% (n=22) of all Unity Technologies engineers (n=3,21785) were active on GitHub. | 0% 0% (n=22) of all Unity Technologies employees (n=4,98786) were active on GitHub. | 22 22 Unity Technologies employees were active on GitHub. |
| 44. Square, Inc. | 1% 1% (n=23) of all Square, Inc. engineers (n=3,73387) were active on GitHub. | 0% 0% (n=23) of all Square, Inc. employees (n=11,37288) were active on GitHub. | 23 23 Square, Inc. employees were active on GitHub. |
| 45. Meta | 1% 1% (n=225) of all Meta engineers (n=39,05889) were active on GitHub. | 0% 0% (n=225) of all Meta employees (n=74,06790) were active on GitHub. | 225 225 Meta employees were active on GitHub. |
| 46. Broadcom | 1% 1% (n=105) of all Broadcom engineers (n=18,81091) were active on GitHub. | 0% 0% (n=105) of all Broadcom employees (n=33,00092) were active on GitHub. | 105 105 Broadcom employees were active on GitHub. |
| 47. Airbnb | 1% 1% (n=18) of all Airbnb engineers (n=3,54093) were active on GitHub. | 0% 0% (n=18) of all Airbnb employees (n=7,30094) were active on GitHub. | 18 18 Airbnb employees were active on GitHub. |
| 48. Intel | 0% 0% (n=261) of all Intel engineers (n=54,92495) were active on GitHub. | 0% 0% (n=261) of all Intel employees (n=108,90096) were active on GitHub. | 261 261 Intel employees were active on GitHub. |
| 49. Spotify | 0% 0% (n=18) of all Spotify engineers (n=3,94497) were active on GitHub. | 0% 0% (n=18) of all Spotify employees (n=7,69198) were active on GitHub. | 18 18 Spotify employees were active on GitHub. |
| 50. SAP SE | 0% 0% (n=167) of all SAP SE engineers (n=37,59099) were active on GitHub. | 0% 0% (n=167) of all SAP SE employees (n=109,973100) were active on GitHub. | 167 167 SAP SE employees were active on GitHub. |
| 51. Uber | 0% 0% (n=34) of all Uber engineers (n=8,071101) were active on GitHub. | 0% 0% (n=34) of all Uber employees (n=31,100102) were active on GitHub. | 34 34 Uber employees were active on GitHub. |
| 52. Cisco Systems | 0% 0% (n=98) of all Cisco Systems engineers (n=25,256103) were active on GitHub. | 0% 0% (n=98) of all Cisco Systems employees (n=86,200104) were active on GitHub. | 98 98 Cisco Systems employees were active on GitHub. |
| 53. Yandex | 0% 0% (n=39) of all Yandex engineers (n=11,020105) were active on GitHub. | 0% 0% (n=39) of all Yandex employees (n=29,000106) were active on GitHub. | 39 39 Yandex employees were active on GitHub. |
| 54. Apple | 0% 0% (n=155) of all Apple engineers (n=45,226107) were active on GitHub. | 0% 0% (n=155) of all Apple employees (n=166,000108) were active on GitHub. | 155 155 Apple employees were active on GitHub. |
| 55. Autodesk | 0% 0% (n=16) of all Autodesk engineers (n=4,705109) were active on GitHub. | 0% 0% (n=16) of all Autodesk employees (n=15,300110) were active on GitHub. | 16 16 Autodesk employees were active on GitHub. |
| 56. Bloomberg | 0% 0% (n=27) of all Bloomberg engineers (n=8,192111) were active on GitHub. | 0% 0% (n=27) of all Bloomberg employees (n=25,356112) were active on GitHub. | 27 27 Bloomberg employees were active on GitHub. |
| 57. Intuit | 0% 0% (n=18) of all Intuit engineers (n=5,868113) were active on GitHub. | 0% 0% (n=18) of all Intuit employees (n=18,800114) were active on GitHub. | 18 18 Intuit employees were active on GitHub. |
| 58. Salesforce | 0% 0% (n=70) of all Salesforce engineers (n=23,597115) were active on GitHub. | 0% 0% (n=70) of all Salesforce employees (n=76,453116) were active on GitHub. | 70 70 Salesforce employees were active on GitHub. |
| 59. Atlassian | 0% 0% (n=19) of all Atlassian engineers (n=6,906117) were active on GitHub. | 0% 0% (n=19) of all Atlassian employees (n=13,813118) were active on GitHub. | 19 19 Atlassian employees were active on GitHub. |
| 60. Baidu | 0% 0% (n=48) of all Baidu engineers (n=19,500119) were active on GitHub. | 0% 0% (n=48) of all Baidu employees (n=35,900120) were active on GitHub. | 48 48 Baidu employees were active on GitHub. |
| 61. Oracle | 0% 0% (n=81) of all Oracle engineers (n=50,000121) were active on GitHub. | 0% 0% (n=81) of all Oracle employees (n=162,000122) were active on GitHub. | 81 81 Oracle employees were active on GitHub. |
| 62. NetEase | 0% 0% (n=18) of all NetEase engineers (n=12,754123) were active on GitHub. | 0% 0% (n=18) of all NetEase employees (n=26,028124) were active on GitHub. | 18 18 NetEase employees were active on GitHub. |
| 63. Capital One | 0% 0% (n=17) of all Capital One engineers (n=16,727125) were active on GitHub. | 0% 0% (n=17) of all Capital One employees (n=52,600126) were active on GitHub. | 17 17 Capital One employees were active on GitHub. |
| 64. EPAM Systems | 0% 0% (n=51) of all EPAM Systems engineers (n=55,100127) were active on GitHub. | 0% 0% (n=51) of all EPAM Systems employees (n=61,200128) were active on GitHub. | 51 51 EPAM Systems employees were active on GitHub. |
| 65. Ericsson | 0% 0% (n=22) of all Ericsson engineers (n=26,744129) were active on GitHub. | 0% 0% (n=22) of all Ericsson employees (n=94,326130) were active on GitHub. | 22 22 Ericsson employees were active on GitHub. |
| 66. Nokia | 0% 0% (n=24) of all Nokia engineers (n=29,189131) were active on GitHub. | 0% 0% (n=24) of all Nokia employees (n=78,434132) were active on GitHub. | 24 24 Nokia employees were active on GitHub. |
| 67. Samsung | 0% 0% (n=32) of all Samsung engineers (n=88,984133) were active on GitHub. | 0% 0% (n=32) of all Samsung employees (n=262,647134) were active on GitHub. | 32 32 Samsung employees were active on GitHub. |
| 68. Huawei | 0% 0% (n=35) of all Huawei engineers (n=113,000135) were active on GitHub. | 0% 0% (n=35) of all Huawei employees (n=208,000136) were active on GitHub. | 35 35 Huawei employees were active on GitHub. |
| 69. Capgemini | 0% 0% (n=19) of all Capgemini engineers (n=77,872137) were active on GitHub. | 0% 0% (n=19) of all Capgemini employees (n=341,100138) were active on GitHub. | 19 19 Capgemini employees were active on GitHub. |
| 70. IBM | (n=1,171) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=1,171) of all IBM employees (n=270,300139) were active on GitHub. | 1,171 1,171 IBM employees were active on GitHub. |
| 71. ByteDance | (n=122) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=122) of all ByteDance employees (n=NaN0) were active on GitHub. | 122 122 ByteDance employees were active on GitHub. |
| 72. Canonical | (n=98) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=98) of all Canonical employees (n=NaN0) were active on GitHub. | 98 98 Canonical employees were active on GitHub. |
| 73. Software Mansion | (n=72) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=72) of all Software Mansion employees (n=NaN0) were active on GitHub. | 72 72 Software Mansion employees were active on GitHub. |
| 74. Posit | (n=41) of all Posit engineers (n=NaN0) were active on GitHub. | (n=41) of all Posit employees (n=NaN0) were active on GitHub. | 41 41 Posit employees were active on GitHub. |
| 75. Accenture | (n=36) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=36) of all Accenture employees (n=779,000140) were active on GitHub. | 36 36 Accenture employees were active on GitHub. |
| 76. Flant | (n=33) of all Flant engineers (n=NaN0) were active on GitHub. | (n=33) of all Flant employees (n=NaN0) were active on GitHub. | 33 33 Flant employees were active on GitHub. |
| 77. Palo Alto Networks | (n=24) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=24) of all Palo Alto Networks employees (n=16,068141) were active on GitHub. | 24 24 Palo Alto Networks employees were active on GitHub. |
| 78. PostHog | (n=22) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=22) of all PostHog employees (n=NaN0) were active on GitHub. | 22 22 PostHog employees were active on GitHub. |
| 79. ServiceNow | (n=21) of all ServiceNow engineers (n=NaN0) were active on GitHub. | 0% 0% (n=21) of all ServiceNow employees (n=26,293142) were active on GitHub. | 21 21 ServiceNow employees were active on GitHub. |
| 80. @supabase | (n=20) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=20) of all @supabase employees (n=NaN0) were active on GitHub. | 20 20 @supabase employees were active on GitHub. |
| 81. Ant Group | (n=19) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=19) of all Ant Group employees (n=NaN0) were active on GitHub. | 19 19 Ant Group employees were active on GitHub. |
| 82. Juspay | (n=19) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=19) of all Juspay employees (n=NaN0) were active on GitHub. | 19 19 Juspay employees were active on GitHub. |
| 83. @expo | (n=19) of all @expo engineers (n=NaN0) were active on GitHub. | (n=19) of all @expo employees (n=NaN0) were active on GitHub. | 19 19 @expo employees were active on GitHub. |
| 84. Anyscale | (n=18) of all Anyscale engineers (n=NaN0) were active on GitHub. | (n=18) of all Anyscale employees (n=NaN0) were active on GitHub. | 18 18 Anyscale employees were active on GitHub. |
| 85. Sanity | (n=18) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=18) of all Sanity employees (n=NaN0) were active on GitHub. | 18 18 Sanity employees were active on GitHub. |
| 86. Expensify | (n=17) of all Expensify engineers (n=NaN0) were active on GitHub. | (n=17) of all Expensify employees (n=NaN0) were active on GitHub. | 17 17 Expensify employees were active on GitHub. |
| 87. @Kong | (n=17) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=17) of all @Kong employees (n=NaN0) were active on GitHub. | 17 17 @Kong employees were active on GitHub. |
| 88. Yahoo! | (n=17) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=17) of all Yahoo! employees (n=NaN0) were active on GitHub. | 17 17 Yahoo! employees were active on GitHub. |
| 89. @clerk | (n=17) of all @clerk engineers (n=NaN0) were active on GitHub. | (n=17) of all @clerk employees (n=NaN0) were active on GitHub. | 17 17 @clerk employees were active on GitHub. |
| 90. Oddball | (n=16) of all Oddball engineers (n=NaN0) were active on GitHub. | (n=16) of all Oddball employees (n=NaN0) were active on GitHub. | 16 16 Oddball employees were active on GitHub. |
| 91. @zed-industries | (n=16) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=16) of all @zed-industries employees (n=NaN0) were active on GitHub. | 16 16 @zed-industries employees were active on GitHub. |
| 92. @apache | (n=16) of all @apache engineers (n=NaN0) were active on GitHub. | (n=16) of all @apache employees (n=NaN0) were active on GitHub. | 16 16 @apache employees were active on GitHub. |
| 93. @hackclub | (n=15) of all @hackclub engineers (n=NaN0) were active on GitHub. | (n=15) of all @hackclub employees (n=NaN0) were active on GitHub. | 15 15 @hackclub employees were active on GitHub. |
| 94. TUM | (n=15) of all TUM engineers (n=NaN0) were active on GitHub. | (n=15) of all TUM employees (n=NaN0) were active on GitHub. | 15 15 TUM employees were active on GitHub. |
| 95. TU Delft | (n=15) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=15) of all TU Delft employees (n=NaN0) were active on GitHub. | 15 15 TU Delft employees were active on GitHub. |
| 96. Cloudera | (n=15) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=15) of all Cloudera employees (n=NaN0) were active on GitHub. | 15 15 Cloudera employees were active on GitHub. |
| 97. AntGroup | (n=14) of all AntGroup engineers (n=NaN0) were active on GitHub. | (n=14) of all AntGroup employees (n=NaN0) were active on GitHub. | 14 14 AntGroup employees were active on GitHub. |
| 98. @Kong | (n=14) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=14) of all @Kong employees (n=NaN0) were active on GitHub. | 14 14 @Kong employees were active on GitHub. |
| 99. UNSW | (n=14) of all UNSW engineers (n=NaN0) were active on GitHub. | (n=14) of all UNSW employees (n=NaN0) were active on GitHub. | 14 14 UNSW employees were active on GitHub. |
| 100. @input-output-hk | (n=14) of all @input-output-hk engineers (n=NaN0) were active on GitHub. | (n=14) of all @input-output-hk employees (n=NaN0) were active on GitHub. | 14 14 @input-output-hk employees were active on GitHub. |
References
- ClickHouse engineer count: linkedin.com (Retrieved December 2025)
- ClickHouse employee count: linkedin.com (Retrieved December 2025)
- Sentry.io engineer count: linkedin.com (Retrieved December 2025)
- Sentry.io employee count: linkedin.com (Retrieved December 2025)
- Vercel engineer count: linkedin.com (Retrieved July 2025)
- Vercel employee count: linkedin.com (Retrieved July 2025)
- Grafana Labs engineer count: linkedin.com (Retrieved July 2025)
- Grafana Labs employee count: linkedin.com (Retrieved July 2025)
- Automattic engineer count: linkedin.com (Retrieved October 2025)
- Automattic employee count: automattic.com (Retrieved October 2025)
- Elastic engineer count: linkedin.com (retrieved July 2025)
- Elastic employee count: sec.gov (page 15)
- Kitware engineer count: linkedin.com (Retrieved July 2025)
- Kitware employee count: linkedin.com (Retrieved July 2025)
- SUSE engineer count: linkedin.com (Retrieved July 2025)
- SUSE employee count: linkedin.com (Retrieved July 2025)
- Docker engineer count: linkedin.com (Retrieved July 2025)
- Docker employee count: linkedin.com (Retrieved July 2025)
- Mozilla engineer count: linkedin.com (Retrieved October 2025)
- Mozilla employee count: linkedin.com (Retrieved October 2025)
- Tenstorrent engineer count: linkedin.com (Retrieved December 2025)
- Tenstorrent employee count: linkedin.com (Retrieved December 2025)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Cloudflare engineer count: linkedin.com (Retrieved July 2025)
- Cloudflare employee count: sec.gov (page 18)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- WSO2 engineer count: linkedin.com (Retrieved October 2025)
- WSO2 employee count: linkedin.com (Retrieved October 2025)
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- Mapbox engineer count: linkedin.com (Retrieved July 2025)
- Mapbox employee count: linkedin.com (Retrieved July 2025)
- Snyk engineer count: linkedin.com (Retrieved August 2025)
- Snyk employee count: linkedin.com (Retrieved August 2025)
- Shopify engineer count: linkedin.com (Retrieved July 2025)
- Shopify employee count: sec.gov (page 10)
- Odoo engineer count: linkedin.com (Retrieved July 2025)
- Odoo employee count: linkedin.com (Retrieved July 2025)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Confluent engineer count: linkedin.com (Retrieved July 2025)
- Confluent employee count: sec.gov (page 18)
- Nebius Group engineer count: sec.gov (page 55, referred to as employees in 'product development')
- Nebius Group employee count: sec.gov (page 55)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- Okta engineer count: linkedin.com (Retrieved July 2025)
- Okta employee count: sec.gov (page 13)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- New Relic engineer count: linkedin.com (Retrieved July 2025)
- New Relic employee count: linkedin.com (Retrieved July 2025)
- Alibaba engineer count: linkedin.com (Retrieved December 2025)
- Alibaba employee count: data.alibabagroup.com (page 14)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- ESRI engineer count: linkedin.com (Retrieved July 2025)
- ESRI employee count: linkedin.com (Retrieved July 2025)
- Databricks engineer count: linkedin.com (Retrieved December 2025)
- Databricks employee count: linkedin.com (Retrieved December 2025)
- Amazon engineer count: linkedin.com (Retrieved July 2025)
- Amazon employee count: linkedin.com (Retrieved July 2025)
- AMD engineer count: linkedin.com (Retrieved July 2025)
- AMD employee count: sec.gov (page 10)
- Adobe engineer count: linkedin.com (Retrieved July 2025)
- Adobe employee count: sec.gov (page 19)
- Google engineer count: linkedin.com (Retrieved July 2025)
- Google employee count: sec.gov (page 9)
- Stripe engineer count: linkedin.com (Retrieved July 2025)
- Stripe employee count: linkedin.com (Retrieved July 2025)
- Tencent engineer count: linkedin.com (Retrieved July 2025)
- Tencent employee count: static.tencent.com (page 52)
- BBC engineer count: linkedin.com (Retrieved August 2025)
- BBC employee count: bbc.co.uk (page 59)
- OpenAI engineer count: linkedin.com (Retrieved December 2025)
- OpenAI employee count: linkedin.com (Retrieved December 2025)
- Netflix engineer count: linkedin.com (Retrieved July 2025)
- Netflix employee count: sec.gov (page 2)
- ThoughtWorks engineer count: linkedin.com (Retrieved July 2025)
- ThoughtWorks employee count: sec.gov (page 6)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Square, Inc. engineer count: linkedin.com (Retrieved July 2025)
- Square, Inc. employee count: sec.gov (page 20)
- Meta engineer count: linkedin.com (Retrieved October 2025)
- Meta employee count: sec.gov (page 12)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Airbnb engineer count: linkedin.com (Retrieved December 2025)
- Airbnb employee count: sec.gov (page 5)
- Intel engineer count: linkedin.com (Retrieved July 2025)
- Intel employee count: sec.gov (page 10)
- Spotify engineer count: sec.gov (page 65, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 65)
- SAP SE engineer count: sec.gov (page F-24, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 98)
- Uber engineer count: linkedin.com (Retrieved July 2025)
- Uber employee count: sec.gov (page 7)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Apple engineer count: linkedin.com (Retrieved December 2025)
- Apple employee count: sec.gov (page 4)
- Autodesk engineer count: linkedin.com (Retrieved July 2025)
- Autodesk employee count: sec.gov (page 13)
- Bloomberg engineer count: linkedin.com (Retrieved July 2025)
- Bloomberg employee count: linkedin.com (Retrieved July 2025)
- Intuit engineer count: linkedin.com (Retrieved August 2025)
- Intuit employee count: sec.gov (page 11)
- Salesforce engineer count: linkedin.com (Retrieved July 2025)
- Salesforce employee count: sec.gov (page 10)
- Atlassian engineer count: sec.gov (page 8, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 11)
- Baidu engineer count: sec.gov (page 201, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 201)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- NetEase engineer count: sec.gov (page 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- Capital One engineer count: linkedin.com (Retrieved October 2025)
- Capital One employee count: sec.gov (page 18)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 5)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Nokia engineer count: linkedin.com (Retrieved July 2025)
- Nokia employee count: sec.gov (page 70)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- Capgemini engineer count: linkedin.com (Retrieved July 2025)
- Capgemini employee count: investors.capgemini.com (page 4)
- IBM employee count: sec.gov (page 14)
- Accenture employee count: sec.gov (page 3)
- Palo Alto Networks employee count: sec.gov (page 11)
- ServiceNow employee count: sec.gov (page 13)