--- description: 검증된 사용 후기를 확인하고 GitHub 사용성, 특징, 가격, 장점과 단점에 대한 자세한 정보를 확인해보세요! 비슷한 경쟁 제품도 확인이 가능합니다. image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: GitHub 가격, 사용 후기, 평점 | 켑테라 Capterra --- Breadcrumb: [홈](/) > [애플리케이션 개발 소프트웨어](/directory/30082/application-development/software) > [GitHub](/software/129067/github) # GitHub Canonical: https://www.capterra.co.kr/software/129067/github Page: 1 / 249\ 다음: [Next page](https://www.capterra.co.kr/software/129067/github?page=2) > GitHub를 통해 개발 팀은 DevOps 파이프라인 및 내장된 코드 보안 내에서 코드 협업, 검토 및 관리를 수행할 수 있습니다. > > Verdict: Rated **4.8/5** by 6187 users. Top-rated for **추천 가능성**. ----- ## Overview ### GitHub은(는) 누가 사용하나요? 스타트 및 소규모 기업업부터 Fortune 50 기업까지 많은 개발 팀들이 모든 단계에서 GitHub를 사용하고 있습니다. ## Quick Stats & Ratings | Metric | Rating | Detail | | **종합** | **4.8/5** | 6187 리뷰 | | 사용 편의성 | 4.4/5 | Based on overall reviews | | 고객 지원 | 4.3/5 | Based on overall reviews | | 비용 대비 가치 | 4.6/5 | Based on overall reviews | | 특징 | 4.7/5 | Based on overall reviews | | Recommendation percentage | 90% | (9/10 추천 가능성) | ## 공급업체 정보 - **회사**: Microsoft - **Location**: Redmond, 미국 - **Founded**: 1975 ## Commercial Context - **시작 가격**: US$4.00 - **Pricing model**: (Free version available) (무료 체험판) - **Target Audience**: 자영업, 2~10, 11~50, 51~200, 201~500, 501~1,000, 1,001~5,000, 5,001~10,000, 10,000+ - **Deployment & Platforms**: 클라우드, SaaS, 웹 기반, Mac(데스크톱), Windows(데스크톱), Windows(온프레미스), Linux(온프레미스), Android(모바일), iPhone(모바일), iPad(모바일) - **Supported Languages**: 영어 - **Available Countries**: 남아프리카, 네덜란드, 노르웨이, 뉴질랜드, 대한민국, 덴마크, 독일, 라트비아, 러시아, 루마니아, 룩셈부르크, 리비아, 리투아니아, 리히텐슈타인, 말레이시아, 멕시코, 미국, 벨기에, 벨라루스, 불가리아 and 27 more ## 특징 - Automated Testing - Real-Time Analytics - 구성 관리 - 그래픽 사용자 인터페이스 - 대시보드 - 디버깅 - 릴리스 관리 - 마일스톤 추적 - 모니터링 - 문제 관리 - 문제 추적 - 백로그 관리 - 버그 추적 - 버그/문제 캡처 - 버전 제어 - 보고/프로젝트 추적 - 애플리케이션 보안 - 저장소 관리 - 지속적 배달 - 지속적 배포 - 지속적 통합 - 취약성 스캔 - 코드 검토 - 태스크 관리 - 태스크 진행률 추적 - 통합 개발 환경 - 티켓 관리 - 파일 공유 - 품질 보증 - 프로젝트 관리 - 협업 개발 - 협업 도구 ## Integrations (15 total) - CircleCI - Docker - Git - Heroku - JIRA Service Management - Jenkins - Jira - Microsoft Azure - Microsoft Visual Studio - Netlify - Pivotal Tracker - Slack - Trello - Vercel - Visual Studio Code ## Support Options - 이메일/지원 센터 - FAQ/포럼 - 지식 기반 ## Category - [애플리케이션 개발 소프트웨어](https://www.capterra.co.kr/directory/30082/application-development/software) ## 관련 범주 - [애플리케이션 개발 소프트웨어](https://www.capterra.co.kr/directory/30082/application-development/software) - [소스 코드 관리 소프트웨어](https://www.capterra.co.kr/directory/31420/source-code-management/software) - [비영리 프로젝트 관리 소프트웨어](https://www.capterra.co.kr/directory/32439/project-management-software-for-nonprofits/software) - [프로젝트 관리 소프트웨어](https://www.capterra.co.kr/directory/30002/project-management/software) - [지속적 통합 소프트웨어](https://www.capterra.co.kr/directory/31119/continuous-integration/software) ## 대안 1. [Jira](https://www.capterra.co.kr/software/19319/jira) — 4.4/5 (15414 reviews) 2. [Wrike](https://www.capterra.co.kr/software/76113/wrike) — 4.4/5 (3023 reviews) 3. [ClickUp](https://www.capterra.co.kr/software/158833/clickup) — 4.6/5 (4603 reviews) 4. [SpiraTeam](https://www.capterra.co.kr/software/85434/spirateam) — 4.2/5 (98 reviews) 5. [Bitrix24](https://www.capterra.co.kr/software/113540/bitrix24) — 4.2/5 (997 reviews) ## 리뷰 ### "Reliable Platform for Version Control and Test Automation Collaboration" — 5.0/5 > **Sarav** | *2026년 5월 20일* | 컴퓨터 소프트웨어 | Recommendation rating: 10.0/10 > > **장점**: GitHub made collaboration and version control very efficient for development and automation testing projects. I especially liked the seamless integration with VS Code, which made committing, reviewing, and managing code much easier directly from the editor. Using GitHub together with Playwright helped streamline test automation workflows, maintain test scripts, and collaborate effectively with team members through PRs and branch management. > > **단점**: Managing merge conflicts and repository permissions sometimes required extra attention. Some advanced enterprise features and CI/CD capabilities may also become expensive for smaller teams. > > Overall, my experience with GitHub has been very positive. It has been a reliable platform for source code management, collaboration, and automation testing workflows. The integration with VS Code improved developer productivity, and using Playwright with GitHub helped organize and maintain automated test scripts efficiently. Features like pull requests, issue tracking, and GitHub Actions added value to the development lifecycle and team collaboration. ----- ### "The Version Control Packed With Features" — 4.0/5 > **검증된 리뷰어** | *2026년 5월 27일* | 소비자 상품 | Recommendation rating: 9.0/10 > > **장점**: This version control makes coding, deployment and maintainance of repository easier for a team.The tool is also exceptional for automating workflows. Easy to integrate with other UI platforms such as source tree , making it user friendly. > > **단점**: Permission and security management with access tokens can be complicated. For large enterprices, Github can be expensive. For a new user, advance features have a steap learning curve. > > overall, I have a positive experience with the platform. Github is a widely used version control platform helping team collaboration and clean coding. over the years, it has created a strong ecosystem of its own. The large online community makes the life of a user easier. ----- ### "Good tool for code management but lacks some features when integrating with Confluence/Jira" — 3.0/5 > **Mark** | *2025년 6월 3일* | 정보 기술 및 서비스 | Recommendation rating: 6.0/10 > > **장점**: GitHub is a great tool to manage pull requests and being able to add labels in our teams helps to differentiate between urgent items which need reviews and are vital for the next release. > > **단점**: One of the drawbacks with GitHub is integrating non development team members into a workflow process. Even though it is possible to setup a workflow too add approvers the terminology and UI is very developer based so can be a bit confusing to non development colleagues. > > Overall GItHub is a good tool for managing code, getting reviews and merging into the relevant branch ahead of deployment. There are some good integrations but it would be great if it could work more seamlessly with Confluence and Jira, and provide additional features to help automatically manage the correct states of the linked jira. ----- ### "The undisputed standard for code collaboration and open source" — 4.0/5 > **Davide** | *2026년 4월 17일* | 보안 및 조사 | Recommendation rating: 10.0/10 > > **장점**: GitHub Actions is the CI/CD tool I prefer over any other. It is immediate, works extremely well, supports multiple operating systems, and even allows you to run self-hosted runners on-premises with minimal setup. What makes it truly powerful is the ecosystem: thousands of community-built, reusable actions exist for almost every use case, so you rarely have to reinvent the wheel. This saves an enormous amount of time day to day. Beyond Actions, the pull request workflow is excellent and the collaboration features — Issues and Discussions in particular — are extremely convenient and well-designed. GitHub is also the de facto standard for open source: almost every meaningful open source project lives here, and the fact that public repositories are free makes it the natural home for community-driven software. I use it both for my personal open source projects and at an enterprise level, and it handles both scenarios very well. The ability to host public and private repositories on the same platform without needing separate tools is a significant advantage. > > **단점**: The project management section (GitHub Projects) still feels rough compared to dedicated tools like Linear. It works, but the UX is unintuitive and I usually reach for other tools when I need real project tracking. Issues and Discussions are great; Projects needs more work. Stability has also become a concern. GitHub has been experiencing more frequent outages lately. They are usually short, but they are disruptive — when your entire workflow depends on GitHub (pushing code, running pipelines, reviewing PRs), even brief downtime brings everything to a halt. Finally, the notification system is genuinely broken for my use case. The sheer volume of notifications makes it nearly impossible to find the ones that actually matter — a comment on your own issue, a review request, a mention. I often miss important updates unless someone tells me directly or I stumble across them manually. > > GitHub is a tool I would recommend to any team, regardless of size or industry. Small teams can get started for free; larger organizations can scale up to GitHub Enterprise. The platform works equally well for closed-source commercial projects and public open source repositories, and you never need to split your work across multiple tools. I would especially recommend it to anyone building or contributing to open source software — GitHub is the central hub where projects are born, grow, and gain traction. There is simply no better place to build in public. It is also worth noting that GitHub is not limited to software developers. Writers, researchers, and academics can benefit from version-controlled plain-text workflows (Markdown, LaTeX) managed through branches and releases — and modern AI tooling makes the learning curve much more approachable than it used to be. In short: I could not work without GitHub. Despite its rough edges, it remains the most complete and widely adopted platform for code collaboration and version control available today. ----- ### "Rock-solid for developing our museum apps, just a massive learning curve for the non-tech guys" — 5.0/5 > **Mark** | *2026년 6월 12일* | 박물관 및 기관 | Recommendation rating: 9.0/10 > > **장점**: GitHub has sheer reliability as a central source of coder truth, especially when you are managing a diverse mix of projects. I work closely with a professional System Architect to manage our codebases, and the platform handles everything we throw at it flawlessly. Recently, we used it as a repository for hosting Mail Transfer Agent Strict Transport Security (MTA-STS), which demands total stability. But where it really shines for us is managing repositories for our in-house applications across completely different museum departments. We have repos dedicated to our Flight Sim \& VR Suite team, another for our Aviation Library team, and a separate one to catalogue our heritage collection. The version control is bulletproof, pull requests are intuitive, and it gives us a secure, centralised space to collaborate. Knowing the platform is fast, stable, and simply never falls over gives us massive peace of mind. > > **단점**: While it is absolute perfection for me and our volunteer System Architect, the biggest challenge is the steep learning curve for everyone else. GitHub’s interface and terminology are fundamentally developer-centric. When you try to bring in non-technical volunteers or niche department teams—like the Admin guys managing physical library archives or setting up flight simulators—the UI can be incredibly intimidating. Concepts like branch merging, pull requests, and commit histories feel like a foreign language to them. GitHub has tried to simplify things over the years, but it still lacks a genuinely user-friendly, abstracted environment for non-developers who just need to collaborate on data or check progress. It takes a lot of hand-holding and internal training to get them comfortable, which slows down cross-department onboarding, especially for 100% non-profit organisation like ours. > > GitHub has been top-tier for me. It has allowed two technical leads to cleanly structure, secure, and oversee multiple developer pipelines for an entire aviation heritage organisation. It seamlessly bridges the gap between high-level infrastructure tasks, like deploying MTA-STS, and bespoke app development for our various museum sectors. The platform is incredibly robust, the hosting is rock-solid, and the security features—particularly the SSL and repo permissions—are exactly what you need when handling heritage data. It isn’t the easiest tool to introduce to non-technical staff or volunteers, and you will have to bridge that UI gap yourself. However, as a core repository system and collaboration engine, it is completely unmatched. It keeps our projects organised, secure, and moving forward in the current, lightning speed of coding in this Singularity of AI. ----- Page: 1 / 249\ 다음: [Next page](https://www.capterra.co.kr/software/129067/github?page=2) ## Links - [View on Capterra](https://www.capterra.co.kr/software/129067/github) ## This page is available in the following languages | Locale | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | ko | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | tr | | ----- ## Structured Data