Corporate GitHub Activity
Most Active Corporations on GitHub, 10 2025
Ranking companies with employees who, during 10 2025, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Sentry.io | 43% 43% (n=80) of all Sentry.io engineers (n=1881) were active on GitHub. | 19% 19% (n=80) of all Sentry.io employees (n=4262) were active on GitHub. | 80 80 Sentry.io employees were active on GitHub. |
|---|---|---|---|
| 2. ClickHouse | 42% 42% (n=75) of all ClickHouse engineers (n=1773) were active on GitHub. | 18% 18% (n=75) of all ClickHouse employees (n=4154) were active on GitHub. | 75 75 ClickHouse employees were active on GitHub. |
| 3. Vercel | 41% 41% (n=90) of all Vercel engineers (n=2205) were active on GitHub. | 12% 12% (n=90) of all Vercel employees (n=7316) were active on GitHub. | 90 90 Vercel employees were active on GitHub. |
| 4. Grafana Labs | 31% 31% (n=204) of all Grafana Labs engineers (n=6497) were active on GitHub. | 13% 13% (n=204) of all Grafana Labs employees (n=1,5918) were active on GitHub. | 204 204 Grafana Labs employees were active on GitHub. |
| 5. Automattic | 24% 24% (n=161) of all Automattic engineers (n=6799) were active on GitHub. | 18% 18% (n=161) of all Automattic employees (n=88710) were active on GitHub. | 161 161 Automattic employees were active on GitHub. |
| 6. Elastic | 19% 19% (n=257) of all Elastic engineers (n=1,32211) were active on GitHub. | 7% 7% (n=257) of all Elastic employees (n=3,53712) were active on GitHub. | 257 257 Elastic employees were active on GitHub. |
| 7. SUSE | 19% 19% (n=138) of all SUSE engineers (n=71813) were active on GitHub. | 5% 5% (n=138) of all SUSE employees (n=2,66314) were active on GitHub. | 138 138 SUSE employees were active on GitHub. |
| 8. Docker | 19% 19% (n=37) of all Docker engineers (n=19415) were active on GitHub. | 4% 4% (n=37) of all Docker employees (n=94116) were active on GitHub. | 37 37 Docker employees were active on GitHub. |
| 9. Mozilla | 16% 16% (n=101) of all Mozilla engineers (n=64817) were active on GitHub. | 6% 6% (n=101) of all Mozilla employees (n=1,74918) were active on GitHub. | 101 101 Mozilla employees were active on GitHub. |
| 10. Kitware | 15% 15% (n=15) of all Kitware engineers (n=9919) were active on GitHub. | 10% 10% (n=15) of all Kitware employees (n=15320) were active on GitHub. | 15 15 Kitware 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=136) of all JetBrains engineers (n=1,15523) were active on GitHub. | 6% 6% (n=136) of all JetBrains employees (n=2,24524) were active on GitHub. | 136 136 JetBrains employees were active on GitHub. |
| 13. WSO2 | 10% 10% (n=66) of all WSO2 engineers (n=69425) were active on GitHub. | 6% 6% (n=66) of all WSO2 employees (n=1,16926) were active on GitHub. | 66 66 WSO2 employees were active on GitHub. |
| 14. Cloudflare | 8% 8% (n=88) of all Cloudflare engineers (n=1,10527) were active on GitHub. | 2% 2% (n=88) of all Cloudflare employees (n=4,26328) were active on GitHub. | 88 88 Cloudflare employees were active on GitHub. |
| 15. DataDog | 7% 7% (n=224) of all DataDog engineers (n=3,10029) were active on GitHub. | 3% 3% (n=224) of all DataDog employees (n=6,50030) were active on GitHub. | 224 224 DataDog employees were active on GitHub. |
| 16. WikiMedia Foundation | 6% 6% (n=14) of all WikiMedia Foundation engineers (n=23231) were active on GitHub. | 1% 1% (n=14) of all WikiMedia Foundation employees (n=1,06932) were active on GitHub. | 14 14 WikiMedia Foundation employees were active on GitHub. |
| 17. MongoDB | 6% 6% (n=74) of all MongoDB engineers (n=1,32733) were active on GitHub. | 1% 1% (n=74) of all MongoDB employees (n=5,55834) were active on GitHub. | 74 74 MongoDB employees were active on GitHub. |
| 18. Snyk | 4% 4% (n=19) of all Snyk engineers (n=46935) were active on GitHub. | 1% 1% (n=19) of all Snyk employees (n=1,27436) were active on GitHub. | 19 19 Snyk employees were active on GitHub. |
| 19. Odoo | 4% 4% (n=38) of all Odoo engineers (n=96637) were active on GitHub. | 1% 1% (n=38) of all Odoo employees (n=6,65138) were active on GitHub. | 38 38 Odoo employees were active on GitHub. |
| 20. Confluent | 3% 3% (n=38) of all Confluent engineers (n=1,36339) were active on GitHub. | 1% 1% (n=38) of all Confluent employees (n=3,06040) were active on GitHub. | 38 38 Confluent employees were active on GitHub. |
| 21. Nebius Group | 3% 3% (n=19) of all Nebius Group engineers (n=73141) were active on GitHub. | 1% 1% (n=19) of all Nebius Group employees (n=1,37142) were active on GitHub. | 19 19 Nebius Group employees were active on GitHub. |
| 22. ESRI | 2% 2% (n=49) of all ESRI engineers (n=2,25843) were active on GitHub. | 1% 1% (n=49) of all ESRI employees (n=7,01144) were active on GitHub. | 49 49 ESRI employees were active on GitHub. |
| 23. Shopify | 2% 2% (n=94) of all Shopify engineers (n=4,39245) were active on GitHub. | 1% 1% (n=94) of all Shopify employees (n=8,10046) were active on GitHub. | 94 94 Shopify employees were active on GitHub. |
| 24. New Relic | 2% 2% (n=23) of all New Relic engineers (n=1,08847) were active on GitHub. | 1% 1% (n=23) of all New Relic employees (n=2,92348) were active on GitHub. | 23 23 New Relic employees were active on GitHub. |
| 25. Microsoft | 2% 2% (n=1,620) of all Microsoft engineers (n=80,00049) were active on GitHub. | 1% 1% (n=1,620) of all Microsoft employees (n=228,00050) were active on GitHub. | 1,620 1,620 Microsoft employees were active on GitHub. |
| 26. Snowflake, Inc. | 2% 2% (n=40) of all Snowflake, Inc. engineers (n=2,25751) were active on GitHub. | 1% 1% (n=40) of all Snowflake, Inc. employees (n=7,83452) were active on GitHub. | 40 40 Snowflake, Inc. employees were active on GitHub. |
| 27. GitLab | 2% 2% (n=15) of all GitLab engineers (n=86553) were active on GitHub. | 1% 1% (n=15) of all GitLab employees (n=2,37554) were active on GitHub. | 15 15 GitLab employees were active on GitHub. |
| 28. NVIDIA | 2% 2% (n=439) of all NVIDIA engineers (n=27,10055) were active on GitHub. | 1% 1% (n=439) of all NVIDIA employees (n=36,00056) were active on GitHub. | 439 439 NVIDIA employees were active on GitHub. |
| 29. Okta | 2% 2% (n=28) of all Okta engineers (n=1,79957) were active on GitHub. | 0% 0% (n=28) of all Okta employees (n=5,91458) were active on GitHub. | 28 28 Okta employees were active on GitHub. |
| 30. Progress Software | 1% 1% (n=15) of all Progress Software engineers (n=1,05559) were active on GitHub. | 1% 1% (n=15) of all Progress Software employees (n=2,81560) were active on GitHub. | 15 15 Progress Software employees were active on GitHub. |
| 31. Adobe | 1% 1% (n=143) of all Adobe engineers (n=11,21361) were active on GitHub. | 0% 0% (n=143) of all Adobe employees (n=30,70962) were active on GitHub. | 143 143 Adobe employees were active on GitHub. |
| 32. Alibaba | 1% 1% (n=119) of all Alibaba engineers (n=9,83163) were active on GitHub. | 0% 0% (n=119) of all Alibaba employees (n=126,66164) were active on GitHub. | 119 119 Alibaba employees were active on GitHub. |
| 33. Arm Ltd | 1% 1% (n=84) of all Arm Ltd engineers (n=6,94365) were active on GitHub. | 1% 1% (n=84) of all Arm Ltd employees (n=8,33066) were active on GitHub. | 84 84 Arm Ltd employees were active on GitHub. |
| 34. AMD | 1% 1% (n=215) of all AMD engineers (n=19,69767) were active on GitHub. | 1% 1% (n=215) of all AMD employees (n=28,00068) were active on GitHub. | 215 215 AMD employees were active on GitHub. |
| 35. Amazon | 1% 1% (n=537) of all Amazon engineers (n=49,92069) were active on GitHub. | 0% 0% (n=537) of all Amazon employees (n=146,76470) were active on GitHub. | 537 537 Amazon employees were active on GitHub. |
| 36. Databricks | 1% 1% (n=61) of all Databricks engineers (n=5,74771) were active on GitHub. | 0% 0% (n=61) of all Databricks employees (n=13,67972) were active on GitHub. | 61 61 Databricks employees were active on GitHub. |
| 37. OpenAI | 1% 1% (n=29) of all OpenAI engineers (n=2,84973) were active on GitHub. | 0% 0% (n=29) of all OpenAI employees (n=9,91574) were active on GitHub. | 29 29 OpenAI employees were active on GitHub. |
| 38. Google | 1% 1% (n=826) of all Google engineers (n=81,83775) were active on GitHub. | 0% 0% (n=826) of all Google employees (n=183,32376) were active on GitHub. | 826 826 Google employees were active on GitHub. |
| 39. Netflix | 1% 1% (n=28) of all Netflix engineers (n=2,95777) were active on GitHub. | 0% 0% (n=28) of all Netflix employees (n=14,00078) were active on GitHub. | 28 28 Netflix employees were active on GitHub. |
| 40. Stripe | 1% 1% (n=33) of all Stripe engineers (n=3,81679) were active on GitHub. | 0% 0% (n=33) of all Stripe employees (n=12,04980) were active on GitHub. | 33 33 Stripe employees were active on GitHub. |
| 41. Unity Technologies | 1% 1% (n=25) of all Unity Technologies engineers (n=3,21781) were active on GitHub. | 1% 1% (n=25) of all Unity Technologies employees (n=4,98782) were active on GitHub. | 25 25 Unity Technologies employees were active on GitHub. |
| 42. BBC | 1% 1% (n=17) of all BBC engineers (n=2,18883) were active on GitHub. | 0% 0% (n=17) of all BBC employees (n=21,50884) were active on GitHub. | 17 17 BBC employees were active on GitHub. |
| 43. ThoughtWorks | 1% 1% (n=29) of all ThoughtWorks engineers (n=3,81685) were active on GitHub. | 0% 0% (n=29) of all ThoughtWorks employees (n=10,50086) were active on GitHub. | 29 29 ThoughtWorks employees were active on GitHub. |
| 44. Tencent | 1% 1% (n=96) of all Tencent engineers (n=13,12487) were active on GitHub. | 0% 0% (n=96) of all Tencent employees (n=110,55888) were active on GitHub. | 96 96 Tencent employees were active on GitHub. |
| 45. Broadcom | 1% 1% (n=108) of all Broadcom engineers (n=18,81089) were active on GitHub. | 0% 0% (n=108) of all Broadcom employees (n=33,00090) were active on GitHub. | 108 108 Broadcom employees were active on GitHub. |
| 46. Autodesk | 1% 1% (n=27) of all Autodesk engineers (n=4,70591) were active on GitHub. | 0% 0% (n=27) of all Autodesk employees (n=15,30092) were active on GitHub. | 27 27 Autodesk employees were active on GitHub. |
| 47. Spotify | 1% 1% (n=22) of all Spotify engineers (n=3,94493) were active on GitHub. | 0% 0% (n=22) of all Spotify employees (n=7,69194) were active on GitHub. | 22 22 Spotify employees were active on GitHub. |
| 48. Square, Inc. | 1% 1% (n=20) of all Square, Inc. engineers (n=3,73395) were active on GitHub. | 0% 0% (n=20) of all Square, Inc. employees (n=11,37296) were active on GitHub. | 20 20 Square, Inc. employees were active on GitHub. |
| 49. Meta | 1% 1% (n=202) of all Meta engineers (n=39,05897) were active on GitHub. | 0% 0% (n=202) of all Meta employees (n=74,06798) were active on GitHub. | 202 202 Meta employees were active on GitHub. |
| 50. Intel | 0% 0% (n=233) of all Intel engineers (n=54,92499) were active on GitHub. | 0% 0% (n=233) of all Intel employees (n=108,900100) were active on GitHub. | 233 233 Intel employees were active on GitHub. |
| 51. SAP SE | 0% 0% (n=152) of all SAP SE engineers (n=37,590101) were active on GitHub. | 0% 0% (n=152) of all SAP SE employees (n=109,973102) were active on GitHub. | 152 152 SAP SE employees were active on GitHub. |
| 52. Yandex | 0% 0% (n=44) of all Yandex engineers (n=11,020103) were active on GitHub. | 0% 0% (n=44) of all Yandex employees (n=29,000104) were active on GitHub. | 44 44 Yandex employees were active on GitHub. |
| 53. Airbnb | 0% 0% (n=14) of all Airbnb engineers (n=3,540105) were active on GitHub. | 0% 0% (n=14) of all Airbnb employees (n=7,300106) were active on GitHub. | 14 14 Airbnb employees were active on GitHub. |
| 54. Bloomberg | 0% 0% (n=32) of all Bloomberg engineers (n=8,192107) were active on GitHub. | 0% 0% (n=32) of all Bloomberg employees (n=25,356108) were active on GitHub. | 32 32 Bloomberg employees were active on GitHub. |
| 55. Salesforce | 0% 0% (n=76) of all Salesforce engineers (n=23,597109) were active on GitHub. | 0% 0% (n=76) of all Salesforce employees (n=76,453110) were active on GitHub. | 76 76 Salesforce employees were active on GitHub. |
| 56. Cisco Systems | 0% 0% (n=81) of all Cisco Systems engineers (n=25,256111) were active on GitHub. | 0% 0% (n=81) of all Cisco Systems employees (n=86,200112) were active on GitHub. | 81 81 Cisco Systems employees were active on GitHub. |
| 57. Apple | 0% 0% (n=140) of all Apple engineers (n=45,226113) were active on GitHub. | 0% 0% (n=140) of all Apple employees (n=166,000114) were active on GitHub. | 140 140 Apple employees were active on GitHub. |
| 58. Uber | 0% 0% (n=24) of all Uber engineers (n=8,071115) were active on GitHub. | 0% 0% (n=24) of all Uber employees (n=31,100116) were active on GitHub. | 24 24 Uber employees were active on GitHub. |
| 59. Atlassian | 0% 0% (n=18) of all Atlassian engineers (n=6,906117) were active on GitHub. | 0% 0% (n=18) of all Atlassian employees (n=13,813118) were active on GitHub. | 18 18 Atlassian employees were active on GitHub. |
| 60. Oracle | 0% 0% (n=90) of all Oracle engineers (n=50,000119) were active on GitHub. | 0% 0% (n=90) of all Oracle employees (n=162,000120) were active on GitHub. | 90 90 Oracle employees were active on GitHub. |
| 61. Baidu | 0% 0% (n=35) of all Baidu engineers (n=19,500121) were active on GitHub. | 0% 0% (n=35) of all Baidu employees (n=35,900122) were active on GitHub. | 35 35 Baidu employees were active on GitHub. |
| 62. PayPal | 0% 0% (n=17) of all PayPal engineers (n=10,077123) were active on GitHub. | 0% 0% (n=17) of all PayPal employees (n=24,400124) were active on GitHub. | 17 17 PayPal employees were active on GitHub. |
| 63. EPAM Systems | 0% 0% (n=48) of all EPAM Systems engineers (n=55,100125) were active on GitHub. | 0% 0% (n=48) of all EPAM Systems employees (n=61,200126) were active on GitHub. | 48 48 EPAM Systems employees were active on GitHub. |
| 64. Nokia | 0% 0% (n=19) of all Nokia engineers (n=29,189127) were active on GitHub. | 0% 0% (n=19) of all Nokia employees (n=78,434128) were active on GitHub. | 19 19 Nokia employees were active on GitHub. |
| 65. Ericsson | 0% 0% (n=15) of all Ericsson engineers (n=26,744129) were active on GitHub. | 0% 0% (n=15) of all Ericsson employees (n=94,326130) were active on GitHub. | 15 15 Ericsson employees were active on GitHub. |
| 66. Huawei | 0% 0% (n=39) of all Huawei engineers (n=113,000131) were active on GitHub. | 0% 0% (n=39) of all Huawei employees (n=208,000132) were active on GitHub. | 39 39 Huawei employees were active on GitHub. |
| 67. Samsung | 0% 0% (n=29) of all Samsung engineers (n=88,984133) were active on GitHub. | 0% 0% (n=29) of all Samsung employees (n=262,647134) were active on GitHub. | 29 29 Samsung employees were active on GitHub. |
| 68. Capgemini | 0% 0% (n=16) of all Capgemini engineers (n=77,872135) were active on GitHub. | 0% 0% (n=16) of all Capgemini employees (n=341,100136) were active on GitHub. | 16 16 Capgemini employees were active on GitHub. |
| 69. IBM | (n=1,170) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=1,170) of all IBM employees (n=270,300137) were active on GitHub. | 1,170 1,170 IBM employees were active on GitHub. |
| 70. ByteDance | (n=110) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=110) of all ByteDance employees (n=NaN0) were active on GitHub. | 110 110 ByteDance employees were active on GitHub. |
| 71. Canonical | (n=81) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=81) of all Canonical employees (n=NaN0) were active on GitHub. | 81 81 Canonical employees were active on GitHub. |
| 72. Software Mansion | (n=66) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=66) of all Software Mansion employees (n=NaN0) were active on GitHub. | 66 66 Software Mansion employees were active on GitHub. |
| 73. Posit | (n=40) of all Posit engineers (n=NaN0) were active on GitHub. | (n=40) of all Posit employees (n=NaN0) were active on GitHub. | 40 40 Posit employees were active on GitHub. |
| 74. Accenture | (n=39) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=39) of all Accenture employees (n=779,000138) were active on GitHub. | 39 39 Accenture employees were active on GitHub. |
| 75. Flant | (n=30) of all Flant engineers (n=NaN0) were active on GitHub. | (n=30) of all Flant employees (n=NaN0) were active on GitHub. | 30 30 Flant employees were active on GitHub. |
| 76. @pass-culture | (n=29) of all @pass-culture engineers (n=NaN0) were active on GitHub. | (n=29) of all @pass-culture employees (n=NaN0) were active on GitHub. | 29 29 @pass-culture employees were active on GitHub. |
| 77. PostHog | (n=26) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=26) of all PostHog employees (n=NaN0) were active on GitHub. | 26 26 PostHog employees were active on GitHub. |
| 78. Palo Alto Networks | (n=22) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=22) of all Palo Alto Networks employees (n=16,068139) were active on GitHub. | 22 22 Palo Alto Networks employees were active on GitHub. |
| 79. 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. |
| 80. ServiceNow | (n=19) of all ServiceNow engineers (n=NaN0) were active on GitHub. | 0% 0% (n=19) of all ServiceNow employees (n=26,293140) were active on GitHub. | 19 19 ServiceNow employees were active on GitHub. |
| 81. @expo | (n=18) of all @expo engineers (n=NaN0) were active on GitHub. | (n=18) of all @expo employees (n=NaN0) were active on GitHub. | 18 18 @expo employees were active on GitHub. |
| 82. @apache | (n=18) of all @apache engineers (n=NaN0) were active on GitHub. | (n=18) of all @apache employees (n=NaN0) were active on GitHub. | 18 18 @apache employees were active on GitHub. |
| 83. @supabase | (n=17) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=17) of all @supabase employees (n=NaN0) were active on GitHub. | 17 17 @supabase 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. 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. |
| 86. Sanity | (n=17) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=17) of all Sanity employees (n=NaN0) were active on GitHub. | 17 17 Sanity employees were active on GitHub. |
| 87. Metabase | (n=16) of all Metabase engineers (n=NaN0) were active on GitHub. | (n=16) of all Metabase employees (n=NaN0) were active on GitHub. | 16 16 Metabase employees were active on GitHub. |
| 88. @hackclub | (n=16) of all @hackclub engineers (n=NaN0) were active on GitHub. | (n=16) of all @hackclub employees (n=NaN0) were active on GitHub. | 16 16 @hackclub employees were active on GitHub. |
| 89. Anyscale | (n=16) of all Anyscale engineers (n=NaN0) were active on GitHub. | (n=16) of all Anyscale employees (n=NaN0) were active on GitHub. | 16 16 Anyscale employees were active on GitHub. |
| 90. NXP | (n=15) of all NXP engineers (n=NaN0) were active on GitHub. | (n=15) of all NXP employees (n=NaN0) were active on GitHub. | 15 15 NXP employees were active on GitHub. |
| 91. Juspay | (n=15) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=15) of all Juspay employees (n=NaN0) were active on GitHub. | 15 15 Juspay employees were active on GitHub. |
| 92. TU Darmstadt | (n=15) of all TU Darmstadt engineers (n=NaN0) were active on GitHub. | (n=15) of all TU Darmstadt employees (n=NaN0) were active on GitHub. | 15 15 TU Darmstadt employees were active on GitHub. |
| 93. @zed-industries | (n=15) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=15) of all @zed-industries employees (n=NaN0) were active on GitHub. | 15 15 @zed-industries employees were active on GitHub. |
| 94. Sentry | (n=14) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=14) of all Sentry employees (n=NaN0) were active on GitHub. | 14 14 Sentry employees were active on GitHub. |
| 95. TUM | (n=14) of all TUM engineers (n=NaN0) were active on GitHub. | (n=14) of all TUM employees (n=NaN0) were active on GitHub. | 14 14 TUM employees were active on GitHub. |
| 96. Redis | (n=14) of all Redis engineers (n=NaN0) were active on GitHub. | (n=14) of all Redis employees (n=NaN0) were active on GitHub. | 14 14 Redis employees were active on GitHub. |
| 97. UIUC | (n=14) of all UIUC engineers (n=NaN0) were active on GitHub. | (n=14) of all UIUC employees (n=NaN0) were active on GitHub. | 14 14 UIUC 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. @espressif | (n=14) of all @espressif engineers (n=NaN0) were active on GitHub. | (n=14) of all @espressif employees (n=NaN0) were active on GitHub. | 14 14 @espressif 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
- Sentry.io engineer count: linkedin.com (Retrieved December 2025)
- Sentry.io employee count: linkedin.com (Retrieved December 2025)
- ClickHouse engineer count: linkedin.com (Retrieved December 2025)
- ClickHouse 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)
- 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)
- Kitware engineer count: linkedin.com (Retrieved July 2025)
- Kitware employee count: linkedin.com (Retrieved July 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
- WSO2 engineer count: linkedin.com (Retrieved October 2025)
- WSO2 employee count: linkedin.com (Retrieved October 2025)
- 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)
- WikiMedia Foundation engineer count: linkedin.com (Retrieved July 2025)
- WikiMedia Foundation employee count: linkedin.com (Retrieved July 2025)
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- Snyk engineer count: linkedin.com (Retrieved August 2025)
- Snyk employee count: linkedin.com (Retrieved August 2025)
- Odoo engineer count: linkedin.com (Retrieved July 2025)
- Odoo employee count: linkedin.com (Retrieved July 2025)
- 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)
- ESRI engineer count: linkedin.com (Retrieved July 2025)
- ESRI employee count: linkedin.com (Retrieved July 2025)
- Shopify engineer count: linkedin.com (Retrieved July 2025)
- Shopify employee count: sec.gov (page 10)
- New Relic engineer count: linkedin.com (Retrieved July 2025)
- New Relic 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)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- GitLab engineer count: linkedin.com (Retrieved July 2025)
- GitLab employee count: sec.gov (page 12)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- 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)
- Adobe engineer count: linkedin.com (Retrieved July 2025)
- Adobe employee count: sec.gov (page 19)
- 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)
- AMD engineer count: linkedin.com (Retrieved July 2025)
- AMD employee count: sec.gov (page 10)
- Amazon engineer count: linkedin.com (Retrieved July 2025)
- Amazon employee count: linkedin.com (Retrieved July 2025)
- Databricks engineer count: linkedin.com (Retrieved December 2025)
- Databricks employee count: linkedin.com (Retrieved December 2025)
- OpenAI engineer count: linkedin.com (Retrieved December 2025)
- OpenAI employee count: linkedin.com (Retrieved December 2025)
- Google engineer count: linkedin.com (Retrieved July 2025)
- Google employee count: sec.gov (page 9)
- Netflix engineer count: linkedin.com (Retrieved July 2025)
- Netflix employee count: sec.gov (page 2)
- Stripe engineer count: linkedin.com (Retrieved July 2025)
- Stripe employee count: linkedin.com (Retrieved July 2025)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- BBC engineer count: linkedin.com (Retrieved August 2025)
- BBC employee count: bbc.co.uk (page 59)
- ThoughtWorks engineer count: linkedin.com (Retrieved July 2025)
- ThoughtWorks employee count: sec.gov (page 6)
- Tencent engineer count: linkedin.com (Retrieved July 2025)
- Tencent employee count: static.tencent.com (page 52)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Autodesk engineer count: linkedin.com (Retrieved July 2025)
- Autodesk employee count: sec.gov (page 13)
- Spotify engineer count: sec.gov (page 65, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 65)
- 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)
- Intel engineer count: linkedin.com (Retrieved July 2025)
- Intel employee count: sec.gov (page 10)
- 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)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Airbnb engineer count: linkedin.com (Retrieved December 2025)
- Airbnb employee count: sec.gov (page 5)
- Bloomberg engineer count: linkedin.com (Retrieved July 2025)
- Bloomberg employee count: linkedin.com (Retrieved July 2025)
- Salesforce engineer count: linkedin.com (Retrieved July 2025)
- Salesforce employee count: sec.gov (page 10)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- Apple engineer count: linkedin.com (Retrieved December 2025)
- Apple employee count: sec.gov (page 4)
- Uber engineer count: linkedin.com (Retrieved July 2025)
- Uber employee count: sec.gov (page 7)
- 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)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- Baidu engineer count: sec.gov (page 201, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 201)
- PayPal engineer count: linkedin.com (Retrieved July 2025)
- PayPal employee count: sec.gov (page 12)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 5)
- Nokia engineer count: linkedin.com (Retrieved July 2025)
- Nokia employee count: sec.gov (page 70)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- 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)