GitHub Headquarters & Corporate Office

About GitHub

GitHub is a global software development and collaboration platform headquartered in San Francisco, California. It was founded in 2008 and provides developers, open-source maintainers, businesses, governments, and large enterprises with tools for source-code hosting, version control, software collaboration, automation, security, cloud development environments, and AI-assisted programming. GitHub is built around Git version control and has developed into a broader software-development platform used throughout the software lifecycle. Current GitHub information reports 225 million+ developers, 4 million+ organizations, and 800 million+ repositories on the platform.

GitHub has expanded significantly beyond its original repository-hosting business. Developers now use the platform for code reviews, pull requests, issues, project planning, CI/CD automation, software packages, cloud development environments, security scanning, AI coding through GitHub Copilot, and enterprise governance. GitHub states that approximately 90% of Fortune 100 companies use the platform, illustrating how deeply it has become embedded in professional software-development workflows.

GitHub is currently owned by Microsoft Corporation. Microsoft announced the $7.5 billion stock acquisition in June 2018 and completed the transaction on October 26, 2018. GitHub continued to operate as a distinct developer platform within Microsoft. A major recent leadership change occurred in 2025, when CEO Thomas Dohmke announced that he was stepping down. GitHub’s current official leadership page no longer lists a standalone GitHub CEO and instead shows GitHub operating within Microsoft’s CoreAI leadership structure, with Jay Parikh, Microsoft’s Executive Vice President of CoreAI, alongside GitHub’s senior executives.

Quick Information

Corporate Phone Number

GitHub does not publish a verified general corporate telephone number for public use.

GitHub’s current Terms explicitly state that ordinary GitHub support is provided electronically rather than through a general telephone support line.

Customer Service Number

GitHub does not offer a universal public Customer Service phone number.

Customer assistance is provided through the GitHub Support portal:

https://support.github.com/

Paid and enterprise support availability depends on the customer’s GitHub plan.

Corporate Office Address

GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107
United States

Headquarters Address

GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107
United States

GitHub’s current privacy documentation confirms this San Francisco address, and GitHub’s official press page continues to identify the company as headquartered in San Francisco.

Email

Privacy: privacy@github.com

Data Protection Officer: dpo@github.com

Media / Press: press@github.com

Copyright / DMCA: copyright@github.com.

Industry

Software Development, Developer Platforms, Cloud Services, DevOps, AI Coding, Cybersecurity and Source-Code Hosting

Founded

2008

GitHub’s official press materials state that the company was founded in February 2008.

Number of Employees

GitHub’s current leadership page describes a workforce of:

3,000+ employees

referred to internally as Hubbers.

Platform Scale

GitHub currently reports:

225M+ developers
4M+ organizations
800M+ repositories
90% of Fortune 100 companies using GitHub.

Corporate Office Hours

GitHub does not publish normal public walk-in headquarters hours.Corporate visitors should arrange access in advance, while customers should use the digital support portal.

Website

https://github.com/

Investor Relations / Careers Page

GitHub does not maintain standalone public Investor Relations because it is owned by Microsoft.

Careers

https://www.github.careers/

Parent company Investor Relations

https://www.microsoft.com/en-us/Investor/

GitHub Products & Services

GitHub Repositories

GitHub repositories provide cloud-based spaces where developers can store, manage, document, and collaborate on source code. Repositories can be public or private, and GitHub currently offers unlimited public and private repositories across its major account plans.

GitHub Free

GitHub Free provides core source-code hosting and collaboration tools for individuals and organizations. Current features include unlimited public and private repositories, Dependabot updates, GitHub Issues and Projects, community support, and monthly GitHub Actions usage allowances.

GitHub Team

GitHub Team adds more advanced organization-level collaboration and repository-management features. Current pricing is listed at $4 per user per month, with features such as additional Actions minutes, increased Packages storage, repository rules, code owners, and web-based support.

GitHub Enterprise

GitHub Enterprise is designed for large organizations that need advanced governance, identity management, compliance, auditability, and deployment controls. Current published pricing starts at $21 per user per month, with options including Enterprise Managed Users, SAML SSO, SCIM provisioning, audit capabilities, regional data residency, and enterprise support.

GitHub Copilot

GitHub Copilot is GitHub’s AI-assisted development platform. It provides code completion, chat, coding agents, code review, command-line tools, model selection, and other AI capabilities. Current individual options include Copilot Free, Pro, and Pro+, with additional Business and Enterprise plans for organizations.

GitHub Actions

GitHub Actions provides CI/CD and workflow automation directly within repositories. Developers can automate testing, builds, deployments, security checks, release processes, and other software workflows using configurable actions and reusable workflow files.

GitHub Codespaces

GitHub Codespaces provides cloud-hosted development environments that can be launched from a browser or supported editor. Teams can use preconfigured environments to standardize development tooling, reduce setup time, and provide developers with access to scalable compute resources.

GitHub Packages

GitHub Packages allows developers and organizations to publish, store, distribute, and manage software packages alongside their source code. Storage and data-transfer allowances vary according to GitHub plan.

GitHub Issues

GitHub Issues provides collaborative issue tracking for bugs, features, tasks, planning, and engineering discussions. Issues can be linked with code, pull requests, Projects, milestones, labels, and automation.

GitHub Projects

GitHub Projects provides customizable planning and project-management views that allow development teams to organize issues, pull requests, roadmaps, priorities, and other work directly alongside source code.

Pull Requests and Code Review

Pull requests allow developers to propose, review, discuss, test, and merge code changes. GitHub’s review system supports comments, required approvals, automated status checks, code owners, draft pull requests, and protected branch workflows.

GitHub Advanced Security

GitHub’s security products include code scanning, secret protection, Dependabot, automated security updates, vulnerability management, and enterprise security features. Current paid Advanced Security components include Code Security and Secret Protection.

Dependabot

Dependabot monitors project dependencies and can alert developers about vulnerable or outdated software packages. It can also automatically open pull requests that update dependencies to safer or newer versions.

GitHub Enterprise Server

GitHub Enterprise Server allows organizations to operate GitHub’s enterprise platform within customer-controlled infrastructure. It is designed for organizations requiring dedicated deployment, governance, network, or compliance controls.

GitHub Sponsors

GitHub Sponsors allows individuals and organizations to financially support eligible open-source developers and projects. GitHub currently reports that the program has supported thousands of maintainers and projects worldwide.

GitHub Education

GitHub Education provides developer tools, educational benefits, training, and support for students, teachers, and academic institutions. GitHub’s current diversity and education information reports millions of students reached through its educational programs.

GitHub Community

GitHub Community provides discussion-based assistance and knowledge sharing for GitHub users. Users on free plans frequently rely on Community discussions, while paid accounts receive access to additional support options.

GitHub Premium Support

GitHub Premium Support is available for eligible enterprise customers and adds higher-priority support, service-level commitments, and callback options. GitHub currently advertises 24/7 electronic support and callback availability for qualifying Premium Support customers.

GitHub Corporate Phone Numbers

Corporate Phone Number

GitHub does not publish a verified general corporate phone number for public use.

Corporate Headquarters Number

No general public headquarters telephone number is currently published.

Headquarters Number

No verified public GitHub headquarters switchboard is listed.

Corporate Office Number

Not publicly listed.

Customer Service Number

GitHub does not offer a universal Customer Service phone number.

Use:

https://support.github.com/

Customer Support Number

No universal public phone number.

GitHub Support is primarily handled through tickets, electronic messaging, and the Support portal.

Toll-Free Number

No verified universal toll-free number is publicly listed.

Sales Number

GitHub does not prominently publish one universal sales phone number.

Enterprise customers and prospective customers should use:

https://github.com/enterprise/contact

GitHub’s sales form allows prospects to provide a phone number and request contact from the sales team.

Billing Number

No separate public billing phone number is published.Billing issues should be submitted through the GitHub Support portal.

Technical Support Number

GitHub does not publish a general technical-support telephone number.Paid and enterprise accounts receive support electronically, with Premium Support customers eligible for callback support.

Security / Abuse Support Number

No general phone number is published.Account security, abuse, and policy reports can be submitted through GitHub Support and GitHub’s policy reporting tools.

Copyright / DMCA Number

No dedicated public phone number is published.

Email

copyright@github.com

Mail

GitHub, Inc., Attn: DMCA Agent, 88 Colin P. Kelly Jr. St., San Francisco, CA 94107.

Privacy Contact

privacy@github.com

Data Protection Officer

dpo@github.com.

International Number

No universal international phone number is published.

GitHub’s service and support structure is primarily digital and global.

Emergency / After-Hours Number

GitHub does not publish a public emergency hotline.

Service outages should be checked through GitHub Status.

Investor Relations Number

Not applicable at the GitHub level.Investor inquiries belong to Microsoft Corporation.

Media / Press Number

No general press phone number is publicly promoted.

Email

press@github.com.

Human Resources Number

GitHub does not publish a universal applicant HR number.

Careers

https://www.github.careers/

Reservations / Booking Number

Not applicable.

How to Reach a Real Person at GitHub

The primary way to reach a GitHub employee for an account, billing, technical, security, or platform issue is to open a ticket through the GitHub Support portal. Paid GitHub plans, Copilot Business, and Copilot Enterprise provide direct access to GitHub Support, while users on free accounts can still contact GitHub for important account, security, and abuse matters. For routine questions on free plans, GitHub Community discussions are often the first support route.

Before submitting a ticket, have the username, organization or enterprise name, repository URL if relevant, billing account, error message, screenshots, plan type, and a clear description of the issue ready. Enterprise administrators should submit tickets from the enterprise account because urgent-priority SLAs and Premium Support commitments apply specifically to properly associated enterprise tickets.

GitHub should not be approached through unverified telephone numbers found on third-party directories. GitHub’s current Terms explicitly state that the service uses electronic support rather than ordinary phone support. Premium Support customers can receive callbacks, but that is part of an authenticated enterprise-support process rather than a public call-in Customer Service number.

GitHub Headquarters & Corporate Office Address

Current Headquarters

GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107
United States

GitHub’s current privacy and legal materials identify this as GitHub, Inc.’s U.S. address, and GitHub’s official press resources continue to identify San Francisco as company headquarters.

Corporate Office

GitHub does not publish a separate U.S. corporate office address distinct from the San Francisco headquarters for general public correspondence.

Mailing Address

For ordinary corporate matters, the verified U.S. address is

GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107

Other Important Address

For DMCA notices

GitHub, Inc.
Attn: DMCA Agent
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107.

Former / Historical Headquarters

GitHub has operated from multiple San Francisco offices during its history, but the current verified official address is 88 Colin P. Kelly Jr. Street. Older San Francisco addresses appearing in historical directories should not be presented as the present headquarters without current verification.

How to File a Complaint Against GitHub

Complaints involving GitHub can include account access, billing, repository availability, suspension, security, abuse, privacy, copyright, enterprise service, Copilot, or other platform issues. Before escalating, collect the GitHub username, organization name, affected repository URLs, subscription details, invoices, screenshots, previous support ticket numbers, dates, and copies of any policy or enforcement notices.

Step 1: Contact Customer Service

Open a ticket through https://support.github.com/ and select the account, organization, or enterprise associated with the problem. Explain the issue clearly, provide relevant URLs and screenshots, and state the exact result you are requesting. Paid customers can use GitHub Support directly for technical and account questions, while free users can use support for account, security, and abuse matters.

Step 2: Contact the Relevant Department

Use the specialized route that matches the complaint. Security and abuse concerns should use GitHub’s abuse and account-security processes, privacy matters can be directed to privacy@github.com, DMCA matters to copyright@github.com, and enterprise issues should be submitted under the correct enterprise account. This helps the complaint reach the team authorized to act on it.

Step 3: Request Supervisor or Management Review

If the first response does not resolve the issue, reply to the existing support ticket and request further review or escalation. Keep the discussion in the same ticket wherever possible so the next support specialist can see the complete history. Enterprise administrators should make sure the ticket is properly associated with the enterprise account if service-level commitments apply.

Step 4: Use the Company’s Written Complaint Channel

GitHub’s support system is itself the primary written complaint channel. Provide a concise chronology, identify previous case numbers, attach relevant evidence, and explain which GitHub policy, billing item, security event, or service issue is disputed. For privacy concerns, a written complaint can also be submitted to privacy@github.com or the Data Protection Officer at dpo@github.com.

Step 5: Contact Corporate Headquarters

For serious corporate correspondence, write to GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107. This route is appropriate when a written corporate record is necessary, but it should not replace the authenticated support portal for routine account and technical issues. Include copies of support references and supporting documents rather than original records.

Step 6: Use the Specialized Complaint or Dispute Department

Copyright complaints should use GitHub’s DMCA process, while content or conduct complaints should use GitHub’s Acceptable Use and abuse reporting mechanisms. Account suspensions or content moderation decisions may also have appeal procedures under GitHub’s policy framework. Use the specialized policy route rather than treating all platform complaints as ordinary Customer Service issues.

Step 7: File With the Appropriate Regulator

Privacy complaints may be filed with the relevant privacy regulator when applicable. GitHub’s privacy statement specifically acknowledges users’ rights to complain to applicable data-protection authorities, including European and UK regulators where relevant. Other issues may fall under different government agencies depending on the subject and jurisdiction.

Step 8: Use Consumer Protection or Financial Dispute Options

If the complaint concerns an unauthorized charge, subscription billing problem, or disputed payment and GitHub cannot resolve it, the customer may contact the payment-card issuer or payment provider. Businesses should first preserve invoices, subscription records, ticket responses, and contractual documentation before initiating any financial dispute.

Step 9: Consider Formal Legal or Arbitration Procedures

For disputes that become formal legal matters, review the agreement governing the specific GitHub product. GitHub’s public Terms state that legal notice cannot be provided merely through normal support messages and must follow the applicable legal-notice requirements. The Terms also identify California law and courts in San Francisco for many consumer GitHub Terms disputes, subject to applicable law and the relevant contract.