Corporate GitHub Activity
Most Active Corporations on GitHub, 02 2026
Ranking companies with employees who, during 02 2026, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. ClickHouse | 50% 50% (n=89) of all ClickHouse engineers (n=1771) were active on GitHub. | 21% 21% (n=89) of all ClickHouse employees (n=4152) were active on GitHub. | 89 89 ClickHouse employees were active on GitHub. |
|---|---|---|---|
| 2. Sentry.io | 47% 47% (n=83) of all Sentry.io engineers (n=1783) were active on GitHub. | 20% 20% (n=83) of all Sentry.io employees (n=4224) were active on GitHub. | 83 83 Sentry.io employees were active on GitHub. |
| 3. Vercel | 40% 40% (n=114) of all Vercel engineers (n=2865) were active on GitHub. | 13% 13% (n=114) of all Vercel employees (n=8486) were active on GitHub. | 114 114 Vercel employees were active on GitHub. |
| 4. Grafana Labs | 30% 30% (n=214) of all Grafana Labs engineers (n=7077) were active on GitHub. | 12% 12% (n=214) of all Grafana Labs employees (n=1,7728) were active on GitHub. | 214 214 Grafana Labs employees were active on GitHub. |
| 5. Automattic | 27% 27% (n=179) of all Automattic engineers (n=6619) were active on GitHub. | 12% 12% (n=179) of all Automattic employees (n=1,46110) were active on GitHub. | 179 179 Automattic employees were active on GitHub. |
| 6. Kitware | 22% 22% (n=21) of all Kitware engineers (n=9611) were active on GitHub. | 14% 14% (n=21) of all Kitware employees (n=15112) were active on GitHub. | 21 21 Kitware employees were active on GitHub. |
| 7. Elastic | 21% 21% (n=296) of all Elastic engineers (n=1,42113) were active on GitHub. | 8% 8% (n=296) of all Elastic employees (n=3,53714) were active on GitHub. | 296 296 Elastic employees were active on GitHub. |
| 8. Docker | 18% 18% (n=38) of all Docker engineers (n=20915) were active on GitHub. | 4% 4% (n=38) of all Docker employees (n=94916) were active on GitHub. | 38 38 Docker employees were active on GitHub. |
| 9. SUSE | 17% 17% (n=122) of all SUSE engineers (n=73617) were active on GitHub. | 5% 5% (n=122) of all SUSE employees (n=2,70818) were active on GitHub. | 122 122 SUSE employees were active on GitHub. |
| 10. Mozilla | 14% 14% (n=96) of all Mozilla engineers (n=66819) were active on GitHub. | 5% 5% (n=96) of all Mozilla employees (n=1,76120) were active on GitHub. | 96 96 Mozilla employees were active on GitHub. |
| 11. Tenstorrent | 11% 11% (n=67) of all Tenstorrent engineers (n=61621) were active on GitHub. | 6% 6% (n=67) of all Tenstorrent employees (n=1,07422) were active on GitHub. | 67 67 Tenstorrent employees were active on GitHub. |
| 12. JetBrains | 10% 10% (n=120) of all JetBrains engineers (n=1,19523) were active on GitHub. | 5% 5% (n=120) of all JetBrains employees (n=2,24524) were active on GitHub. | 120 120 JetBrains employees were active on GitHub. |
| 13. PingCAP | 10% 10% (n=20) of all PingCAP engineers (n=20725) were active on GitHub. | 4% 4% (n=20) of all PingCAP employees (n=46726) were active on GitHub. | 20 20 PingCAP employees were active on GitHub. |
| 14. Cloudflare | 9% 9% (n=117) of all Cloudflare engineers (n=1,30827) were active on GitHub. | 2% 2% (n=117) of all Cloudflare employees (n=5,15628) were active on GitHub. | 117 117 Cloudflare employees were active on GitHub. |
| 15. WSO2 | 8% 8% (n=61) of all WSO2 engineers (n=72529) were active on GitHub. | 5% 5% (n=61) of all WSO2 employees (n=1,21530) were active on GitHub. | 61 61 WSO2 employees were active on GitHub. |
| 16. DataDog | 5% 5% (n=213) of all DataDog engineers (n=3,90031) were active on GitHub. | 3% 3% (n=213) of all DataDog employees (n=8,10032) were active on GitHub. | 213 213 DataDog employees were active on GitHub. |
| 17. Snyk | 4% 4% (n=19) of all Snyk engineers (n=46933) were active on GitHub. | 1% 1% (n=19) of all Snyk employees (n=1,27434) were active on GitHub. | 19 19 Snyk employees were active on GitHub. |
| 18. MongoDB | 3% 3% (n=68) of all MongoDB engineers (n=2,20435) were active on GitHub. | 1% 1% (n=68) of all MongoDB employees (n=5,63636) were active on GitHub. | 68 68 MongoDB employees were active on GitHub. |
| 19. Odoo | 3% 3% (n=29) of all Odoo engineers (n=1,07437) were active on GitHub. | 0% 0% (n=29) of all Odoo employees (n=7,81838) were active on GitHub. | 29 29 Odoo employees were active on GitHub. |
| 20. Shopify | 3% 3% (n=118) of all Shopify engineers (n=4,65839) were active on GitHub. | 2% 2% (n=118) of all Shopify employees (n=7,60040) were active on GitHub. | 118 118 Shopify employees were active on GitHub. |
| 21. Confluent | 2% 2% (n=34) of all Confluent engineers (n=1,36741) were active on GitHub. | 1% 1% (n=34) of all Confluent employees (n=3,24142) were active on GitHub. | 34 34 Confluent employees were active on GitHub. |
| 22. Nebius Group | 2% 2% (n=17) of all Nebius Group engineers (n=73143) were active on GitHub. | 1% 1% (n=17) of all Nebius Group employees (n=1,37144) were active on GitHub. | 17 17 Nebius Group employees were active on GitHub. |
| 23. Microsoft | 2% 2% (n=1,783) of all Microsoft engineers (n=80,00045) were active on GitHub. | 1% 1% (n=1,783) of all Microsoft employees (n=228,00046) were active on GitHub. | 1,783 1,783 Microsoft employees were active on GitHub. |
| 24. Snowflake, Inc. | 2% 2% (n=44) of all Snowflake, Inc. engineers (n=2,25747) were active on GitHub. | 1% 1% (n=44) of all Snowflake, Inc. employees (n=7,83448) were active on GitHub. | 44 44 Snowflake, Inc. employees were active on GitHub. |
| 25. Alibaba | 2% 2% (n=166) of all Alibaba engineers (n=9,84749) were active on GitHub. | 0% 0% (n=166) of all Alibaba employees (n=126,66150) were active on GitHub. | 166 166 Alibaba employees were active on GitHub. |
| 26. Progress Software | 2% 2% (n=17) of all Progress Software engineers (n=1,04851) were active on GitHub. | 1% 1% (n=17) of all Progress Software employees (n=2,80152) were active on GitHub. | 17 17 Progress Software employees were active on GitHub. |
| 27. Okta | 2% 2% (n=27) of all Okta engineers (n=1,66653) were active on GitHub. | 0% 0% (n=27) of all Okta employees (n=6,36654) were active on GitHub. | 27 27 Okta employees were active on GitHub. |
| 28. Hyland | 2% 2% (n=19) of all Hyland engineers (n=1,17755) were active on GitHub. | 0% 0% (n=19) of all Hyland employees (n=4,16056) were active on GitHub. | 19 19 Hyland employees were active on GitHub. |
| 29. GitLab | 2% 2% (n=14) of all GitLab engineers (n=90457) were active on GitHub. | 1% 1% (n=14) of all GitLab employees (n=2,37558) were active on GitHub. | 14 14 GitLab employees were active on GitHub. |
| 30. ESRI | 2% 2% (n=35) of all ESRI engineers (n=2,28759) were active on GitHub. | 0% 0% (n=35) of all ESRI employees (n=7,16560) were active on GitHub. | 35 35 ESRI employees were active on GitHub. |
| 31. NVIDIA | 1% 1% (n=455) of all NVIDIA engineers (n=31,00061) were active on GitHub. | 1% 1% (n=455) of all NVIDIA employees (n=42,00062) were active on GitHub. | 455 455 NVIDIA employees were active on GitHub. |
| 32. OpenAI | 1% 1% (n=42) of all OpenAI engineers (n=2,91663) were active on GitHub. | 1% 1% (n=42) of all OpenAI employees (n=7,30364) were active on GitHub. | 42 42 OpenAI employees were active on GitHub. |
| 33. AMD | 1% 1% (n=268) of all AMD engineers (n=21,98465) were active on GitHub. | 1% 1% (n=268) of all AMD employees (n=31,00066) were active on GitHub. | 268 268 AMD employees were active on GitHub. |
| 34. Square, Inc. | 1% 1% (n=34) of all Square, Inc. engineers (n=2,95067) were active on GitHub. | 0% 0% (n=34) of all Square, Inc. employees (n=10,20568) were active on GitHub. | 34 34 Square, Inc. employees were active on GitHub. |
| 35. Amazon | 1% 1% (n=554) of all Amazon engineers (n=49,06669) were active on GitHub. | 0% 0% (n=554) of all Amazon employees (n=153,71070) were active on GitHub. | 554 554 Amazon employees were active on GitHub. |
| 36. Databricks | 1% 1% (n=69) of all Databricks engineers (n=6,20471) were active on GitHub. | 0% 0% (n=69) of all Databricks employees (n=14,59272) were active on GitHub. | 69 69 Databricks employees were active on GitHub. |
| 37. Google | 1% 1% (n=852) of all Google engineers (n=83,31873) were active on GitHub. | 0% 0% (n=852) of all Google employees (n=190,82074) were active on GitHub. | 852 852 Google employees were active on GitHub. |
| 38. Netflix | 1% 1% (n=32) of all Netflix engineers (n=3,13075) were active on GitHub. | 0% 0% (n=32) of all Netflix employees (n=16,00076) were active on GitHub. | 32 32 Netflix employees were active on GitHub. |
| 39. Arm Ltd | 1% 1% (n=69) of all Arm Ltd engineers (n=6,94377) were active on GitHub. | 1% 1% (n=69) of all Arm Ltd employees (n=8,33078) were active on GitHub. | 69 69 Arm Ltd employees were active on GitHub. |
| 40. WIX | 1% 1% (n=23) of all WIX engineers (n=2,42879) were active on GitHub. | 1% 1% (n=23) of all WIX employees (n=4,56880) were active on GitHub. | 23 23 WIX employees were active on GitHub. |
| 41. Unity Technologies | 1% 1% (n=26) of all Unity Technologies engineers (n=2,88781) were active on GitHub. | 1% 1% (n=26) of all Unity Technologies employees (n=4,41282) were active on GitHub. | 26 26 Unity Technologies employees were active on GitHub. |
| 42. Adobe | 1% 1% (n=97) of all Adobe engineers (n=11,43683) were active on GitHub. | 0% 0% (n=97) of all Adobe employees (n=31,36084) were active on GitHub. | 97 97 Adobe employees were active on GitHub. |
| 43. ThoughtWorks | 1% 1% (n=32) of all ThoughtWorks engineers (n=4,00885) were active on GitHub. | 0% 0% (n=32) of all ThoughtWorks employees (n=10,50086) were active on GitHub. | 32 32 ThoughtWorks employees were active on GitHub. |
| 44. Stripe | 1% 1% (n=32) of all Stripe engineers (n=4,27687) were active on GitHub. | 0% 0% (n=32) of all Stripe employees (n=13,72288) were active on GitHub. | 32 32 Stripe employees were active on GitHub. |
| 45. BBC | 1% 1% (n=15) of all BBC engineers (n=2,18889) were active on GitHub. | 0% 0% (n=15) of all BBC employees (n=21,50890) were active on GitHub. | 15 15 BBC employees were active on GitHub. |
| 46. Tencent | 1% 1% (n=90) of all Tencent engineers (n=13,32991) were active on GitHub. | 0% 0% (n=90) of all Tencent employees (n=110,55892) were active on GitHub. | 90 90 Tencent employees were active on GitHub. |
| 47. Spotify | 1% 1% (n=24) of all Spotify engineers (n=3,78793) were active on GitHub. | 0% 0% (n=24) of all Spotify employees (n=7,28794) were active on GitHub. | 24 24 Spotify employees were active on GitHub. |
| 48. Meta | 1% 1% (n=213) of all Meta engineers (n=39,83595) were active on GitHub. | 0% 0% (n=213) of all Meta employees (n=78,86596) were active on GitHub. | 213 213 Meta employees were active on GitHub. |
| 49. Broadcom | 1% 1% (n=100) of all Broadcom engineers (n=18,81097) were active on GitHub. | 0% 0% (n=100) of all Broadcom employees (n=33,00098) were active on GitHub. | 100 100 Broadcom employees were active on GitHub. |
| 50. Intel | 0% 0% (n=231) of all Intel engineers (n=51,69399) were active on GitHub. | 0% 0% (n=231) of all Intel employees (n=85,100100) were active on GitHub. | 231 231 Intel employees were active on GitHub. |
| 51. Yandex | 0% 0% (n=49) of all Yandex engineers (n=11,020101) were active on GitHub. | 0% 0% (n=49) of all Yandex employees (n=29,000102) were active on GitHub. | 49 49 Yandex employees were active on GitHub. |
| 52. Airbnb | 0% 0% (n=16) of all Airbnb engineers (n=3,696103) were active on GitHub. | 0% 0% (n=16) of all Airbnb employees (n=8,200104) were active on GitHub. | 16 16 Airbnb employees were active on GitHub. |
| 53. Bloomberg | 0% 0% (n=36) of all Bloomberg engineers (n=8,344105) were active on GitHub. | 0% 0% (n=36) of all Bloomberg employees (n=25,768106) were active on GitHub. | 36 36 Bloomberg employees were active on GitHub. |
| 54. Booking.com | 0% 0% (n=14) of all Booking.com engineers (n=3,336107) were active on GitHub. | 0% 0% (n=14) of all Booking.com employees (n=24,300108) were active on GitHub. | 14 14 Booking.com employees were active on GitHub. |
| 55. Cisco Systems | 0% 0% (n=94) of all Cisco Systems engineers (n=25,256109) were active on GitHub. | 0% 0% (n=94) of all Cisco Systems employees (n=86,200110) were active on GitHub. | 94 94 Cisco Systems employees were active on GitHub. |
| 56. Autodesk | 0% 0% (n=17) of all Autodesk engineers (n=4,883111) were active on GitHub. | 0% 0% (n=17) of all Autodesk employees (n=15,300112) were active on GitHub. | 17 17 Autodesk employees were active on GitHub. |
| 57. Salesforce | 0% 0% (n=83) of all Salesforce engineers (n=24,359113) were active on GitHub. | 0% 0% (n=83) of all Salesforce employees (n=83,334114) were active on GitHub. | 83 83 Salesforce employees were active on GitHub. |
| 58. Atlassian | 0% 0% (n=23) of all Atlassian engineers (n=6,906115) were active on GitHub. | 0% 0% (n=23) of all Atlassian employees (n=13,813116) were active on GitHub. | 23 23 Atlassian employees were active on GitHub. |
| 59. Uber | 0% 0% (n=28) of all Uber engineers (n=8,759117) were active on GitHub. | 0% 0% (n=28) of all Uber employees (n=34,000118) were active on GitHub. | 28 28 Uber employees were active on GitHub. |
| 60. Apple | 0% 0% (n=142) of all Apple engineers (n=45,932119) were active on GitHub. | 0% 0% (n=142) of all Apple employees (n=166,000120) were active on GitHub. | 142 142 Apple employees were active on GitHub. |
| 61. SAP SE | 0% 0% (n=117) of all SAP SE engineers (n=37,965121) were active on GitHub. | 0% 0% (n=117) of all SAP SE employees (n=111,397122) were active on GitHub. | 117 117 SAP SE employees were active on GitHub. |
| 62. Baidu | 0% 0% (n=39) of all Baidu engineers (n=19,500123) were active on GitHub. | 0% 0% (n=39) of all Baidu employees (n=35,900124) were active on GitHub. | 39 39 Baidu employees were active on GitHub. |
| 63. Oracle | 0% 0% (n=87) of all Oracle engineers (n=50,000125) were active on GitHub. | 0% 0% (n=87) of all Oracle employees (n=162,000126) were active on GitHub. | 87 87 Oracle employees were active on GitHub. |
| 64. EPAM Systems | 0% 0% (n=58) of all EPAM Systems engineers (n=56,600127) were active on GitHub. | 0% 0% (n=58) of all EPAM Systems employees (n=62,850128) were active on GitHub. | 58 58 EPAM Systems employees were active on GitHub. |
| 65. Capital One | 0% 0% (n=17) of all Capital One engineers (n=19,974129) were active on GitHub. | 0% 0% (n=17) of all Capital One employees (n=76,300130) were active on GitHub. | 17 17 Capital One employees were active on GitHub. |
| 66. Nokia | 0% 0% (n=18) of all Nokia engineers (n=31,780131) were active on GitHub. | 0% 0% (n=18) of all Nokia employees (n=78,005132) were active on GitHub. | 18 18 Nokia employees were active on GitHub. |
| 67. Huawei | 0% 0% (n=41) of all Huawei engineers (n=113,000133) were active on GitHub. | 0% 0% (n=41) of all Huawei employees (n=208,000134) were active on GitHub. | 41 41 Huawei employees were active on GitHub. |
| 68. Capgemini | 0% 0% (n=22) of all Capgemini engineers (n=82,175135) were active on GitHub. | 0% 0% (n=22) of all Capgemini employees (n=341,100136) were active on GitHub. | 22 22 Capgemini employees were active on GitHub. |
| 69. Samsung | 0% 0% (n=23) of all Samsung engineers (n=88,984137) were active on GitHub. | 0% 0% (n=23) of all Samsung employees (n=262,647138) were active on GitHub. | 23 23 Samsung employees were active on GitHub. |
| 70. IBM | (n=1,177) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=1,177) of all IBM employees (n=264,300139) were active on GitHub. | 1,177 1,177 IBM employees were active on GitHub. |
| 71. ByteDance | (n=121) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=121) of all ByteDance employees (n=NaN0) were active on GitHub. | 121 121 ByteDance employees were active on GitHub. |
| 72. Canonical | (n=91) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=91) of all Canonical employees (n=NaN0) were active on GitHub. | 91 91 Canonical employees were active on GitHub. |
| 73. Software Mansion | (n=69) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=69) of all Software Mansion employees (n=NaN0) were active on GitHub. | 69 69 Software Mansion employees were active on GitHub. |
| 74. Posit | (n=55) of all Posit engineers (n=NaN0) were active on GitHub. | (n=55) of all Posit employees (n=NaN0) were active on GitHub. | 55 55 Posit employees were active on GitHub. |
| 75. Flant | (n=34) of all Flant engineers (n=NaN0) were active on GitHub. | (n=34) of all Flant employees (n=NaN0) were active on GitHub. | 34 34 Flant employees were active on GitHub. |
| 76. Accenture | (n=32) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=32) of all Accenture employees (n=779,000140) were active on GitHub. | 32 32 Accenture employees were active on GitHub. |
| 77. PostHog | (n=31) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=31) of all PostHog employees (n=NaN0) were active on GitHub. | 31 31 PostHog employees were active on GitHub. |
| 78. Sanity | (n=29) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=29) of all Sanity employees (n=NaN0) were active on GitHub. | 29 29 Sanity employees were active on GitHub. |
| 79. Ericsson | (n=24) of all Ericsson engineers (n=NaN0) were active on GitHub. | 0% 0% (n=24) of all Ericsson employees (n=88,826141) were active on GitHub. | 24 24 Ericsson employees were active on GitHub. |
| 80. @supabase | (n=21) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=21) of all @supabase employees (n=NaN0) were active on GitHub. | 21 21 @supabase employees were active on GitHub. |
| 81. Metabase | (n=20) of all Metabase engineers (n=NaN0) were active on GitHub. | (n=20) of all Metabase employees (n=NaN0) were active on GitHub. | 20 20 Metabase employees were active on GitHub. |
| 82. Supabase | (n=19) of all Supabase engineers (n=NaN0) were active on GitHub. | (n=19) of all Supabase employees (n=NaN0) were active on GitHub. | 19 19 Supabase employees were active on GitHub. |
| 83. Camunda | (n=17) of all Camunda engineers (n=NaN0) were active on GitHub. | (n=17) of all Camunda employees (n=NaN0) were active on GitHub. | 17 17 Camunda employees were active on GitHub. |
| 84. 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. |
| 85. Anthropic | (n=17) of all Anthropic engineers (n=NaN0) were active on GitHub. | (n=17) of all Anthropic employees (n=NaN0) were active on GitHub. | 17 17 Anthropic employees were active on GitHub. |
| 86. Palo Alto Networks | (n=17) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=17) of all Palo Alto Networks employees (n=16,068142) were active on GitHub. | 17 17 Palo Alto Networks employees were active on GitHub. |
| 87. Oddball | (n=17) of all Oddball engineers (n=NaN0) were active on GitHub. | (n=17) of all Oddball employees (n=NaN0) were active on GitHub. | 17 17 Oddball employees were active on GitHub. |
| 88. @zed-industries | (n=17) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=17) of all @zed-industries employees (n=NaN0) were active on GitHub. | 17 17 @zed-industries employees were active on GitHub. |
| 89. @expo | (n=17) of all @expo engineers (n=NaN0) were active on GitHub. | (n=17) of all @expo employees (n=NaN0) were active on GitHub. | 17 17 @expo employees were active on GitHub. |
| 90. Sentry | (n=16) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=16) of all Sentry employees (n=NaN0) were active on GitHub. | 16 16 Sentry employees were active on GitHub. |
| 91. @gravitational | (n=16) of all @gravitational engineers (n=NaN0) were active on GitHub. | (n=16) of all @gravitational employees (n=NaN0) were active on GitHub. | 16 16 @gravitational employees were active on GitHub. |
| 92. @temporalio | (n=16) of all @temporalio engineers (n=NaN0) were active on GitHub. | (n=16) of all @temporalio employees (n=NaN0) were active on GitHub. | 16 16 @temporalio employees were active on GitHub. |
| 93. Juspay | (n=16) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=16) of all Juspay employees (n=NaN0) were active on GitHub. | 16 16 Juspay employees were active on GitHub. |
| 94. @frappe | (n=16) of all @frappe engineers (n=NaN0) were active on GitHub. | (n=16) of all @frappe employees (n=NaN0) were active on GitHub. | 16 16 @frappe employees were active on GitHub. |
| 95. Ant Group | (n=15) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=15) of all Ant Group employees (n=NaN0) were active on GitHub. | 15 15 Ant Group employees were active on GitHub. |
| 96. Redis | (n=15) of all Redis engineers (n=NaN0) were active on GitHub. | (n=15) of all Redis employees (n=NaN0) were active on GitHub. | 15 15 Redis employees were active on GitHub. |
| 97. UIUC | (n=15) of all UIUC engineers (n=NaN0) were active on GitHub. | (n=15) of all UIUC employees (n=NaN0) were active on GitHub. | 15 15 UIUC employees were active on GitHub. |
| 98. Figma | (n=15) of all Figma engineers (n=NaN0) were active on GitHub. | (n=15) of all Figma employees (n=NaN0) were active on GitHub. | 15 15 Figma employees were active on GitHub. |
| 99. Anyscale | (n=15) of all Anyscale engineers (n=NaN0) were active on GitHub. | (n=15) of all Anyscale employees (n=NaN0) were active on GitHub. | 15 15 Anyscale employees were active on GitHub. |
| 100. @oxidecomputer | (n=14) of all @oxidecomputer engineers (n=NaN0) were active on GitHub. | (n=14) of all @oxidecomputer employees (n=NaN0) were active on GitHub. | 14 14 @oxidecomputer 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 February 2026)
- Sentry.io employee count: linkedin.com (Retrieved February 2026)
- Vercel engineer count: linkedin.com (Retrieved January 2026)
- Vercel employee count: linkedin.com (Retrieved January 2026)
- Grafana Labs engineer count: linkedin.com (Retrieved January 2026)
- Grafana Labs employee count: linkedin.com (Retrieved January 2026)
- Automattic engineer count: linkedin.com (Retrieved January 2026)
- Automattic employee count: automattic.com (Retrieved January 2026)
- Kitware engineer count: linkedin.com (Retrieved January 2026)
- Kitware employee count: linkedin.com (Retrieved January 2026)
- Elastic engineer count: linkedin.com (retrieved January 2026)
- Elastic employee count: sec.gov (page 15)
- Docker engineer count: linkedin.com (Retrieved January 2026)
- Docker employee count: linkedin.com (Retrieved January 2026)
- SUSE engineer count: linkedin.com (Retrieved January 2026)
- SUSE employee count: linkedin.com (Retrieved January 2026)
- Mozilla engineer count: linkedin.com (Retrieved January 2026)
- Mozilla employee count: linkedin.com (Retrieved January 2026)
- 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
- PingCAP engineer count: linkedin.com (Retrieved August 2025)
- PingCAP employee count: linkedin.com (Retrieved August 2025)
- Cloudflare engineer count: linkedin.com (Retrieved January 2026)
- Cloudflare employee count: sec.gov (page 18)
- WSO2 engineer count: linkedin.com (Retrieved January 2026)
- WSO2 employee count: linkedin.com (Retrieved January 2026)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- Snyk engineer count: linkedin.com (Retrieved August 2025)
- Snyk employee count: linkedin.com (Retrieved August 2025)
- MongoDB engineer count: linkedin.com (Retrieved March 2026)
- MongoDB employee count: sec.gov (page 9)
- Odoo engineer count: linkedin.com (Retrieved January 2026)
- Odoo employee count: linkedin.com (Retrieved January 2026)
- Shopify engineer count: linkedin.com (Retrieved January 2026)
- Shopify employee count: sec.gov (page 10)
- Confluent engineer count: linkedin.com (Retrieved January 2026)
- Confluent employee count: sec.gov (page 19)
- Nebius Group engineer count: sec.gov (page 55, referred to as employees in 'product development')
- Nebius Group employee count: sec.gov (page 55)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- Alibaba engineer count: linkedin.com (Retrieved January 2026)
- Alibaba employee count: data.alibabagroup.com (page 14)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- Okta engineer count: linkedin.com (Retrieved January 2026)
- Okta employee count: sec.gov (page 13)
- Hyland engineer count: linkedin.com (Retrieved January 2026)
- Hyland employee count: linkedin.com (Retrieved January 2026)
- GitLab engineer count: linkedin.com (Retrieved January 2026)
- GitLab employee count: sec.gov (page 12)
- ESRI engineer count: linkedin.com (Retrieved January 2026)
- ESRI employee count: linkedin.com (Retrieved January 2026)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- OpenAI engineer count: linkedin.com (Retrieved February 2026)
- OpenAI employee count: linkedin.com (Retrieved February 2026)
- AMD engineer count: linkedin.com (Retrieved January 2026)
- AMD employee count: sec.gov (page 11)
- Square, Inc. engineer count: linkedin.com (Retrieved January 2026)
- Square, Inc. employee count: sec.gov (page 19)
- Amazon engineer count: linkedin.com (Retrieved January 2026)
- Amazon employee count: linkedin.com (Retrieved January 2026)
- Databricks engineer count: linkedin.com (Retrieved February 2026)
- Databricks employee count: linkedin.com (Retrieved February 2026)
- Google engineer count: linkedin.com (Retrieved January 2026)
- Google employee count: sec.gov (page 7)
- Netflix engineer count: linkedin.com (Retrieved January 2026)
- Netflix employee count: sec.gov (page 2)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- WIX engineer count: sec.gov (page 91, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 152)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Adobe engineer count: linkedin.com (Retrieved January 2026)
- Adobe employee count: sec.gov (page 13)
- ThoughtWorks engineer count: linkedin.com (Retrieved January 2026)
- ThoughtWorks employee count: sec.gov (page 6)
- Stripe engineer count: linkedin.com (Retrieved January 2026)
- Stripe employee count: linkedin.com (Retrieved January 2026)
- BBC engineer count: linkedin.com (Retrieved August 2025)
- BBC employee count: bbc.co.uk (page 59)
- Tencent engineer count: linkedin.com (Retrieved January 2026)
- Tencent employee count: static.tencent.com (page 52)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Meta engineer count: linkedin.com (Retrieved January 2026)
- Meta employee count: sec.gov (page 9)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Intel engineer count: linkedin.com (Retrieved January 2026)
- Intel employee count: sec.gov (page 15)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Airbnb engineer count: linkedin.com (Retrieved March 2026)
- Airbnb employee count: sec.gov (page 5)
- Bloomberg engineer count: linkedin.com (Retrieved January 2026)
- Bloomberg employee count: linkedin.com (Retrieved January 2026)
- Booking.com engineer count: linkedin.com (Retrieved January 2026)
- Booking.com employee count: sec.gov (page 5)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- Autodesk engineer count: linkedin.com (Retrieved January 2026)
- Autodesk employee count: sec.gov (page 13)
- Salesforce engineer count: linkedin.com (Retrieved January 2026)
- 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)
- Uber engineer count: linkedin.com (Retrieved January 2026)
- Uber employee count: sec.gov (page 7)
- Apple engineer count: linkedin.com (Retrieved January 2025)
- Apple employee count: sec.gov (page 4)
- SAP SE engineer count: sec.gov (page 31, referred to as employees in 'development')
- SAP SE employee count: sec.gov (page 100)
- 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)
- EPAM Systems engineer count: sec.gov (page 6, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 6)
- Capital One engineer count: linkedin.com (Retrieved January 2026)
- Capital One employee count: sec.gov (page 19)
- Nokia engineer count: linkedin.com (Retrieved January 2026)
- Nokia employee count: sec.gov (page 66)
- 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 January 2026)
- Capgemini employee count: investors.capgemini.com (page 4)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- IBM employee count: ibm.com (page 15)
- Accenture employee count: sec.gov (page 3)
- Ericsson employee count: sec.gov (page 7)
- Palo Alto Networks employee count: sec.gov (page 11)