GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Wrike
Score 8.5 out of 10
Mid-Size Companies (51-1,000 employees)
Wrike is a project management and collaboration software. This solution connects tasks, discussions, and emails to the user’s project plan. Wrike is optimized for agile workflows and aims to help resolve data silos, poor visibility into work status, and missed deadlines and project failures.
$240
per year 2 users (minimum)
Pricing
GitHub
Wrike
Editions & Modules
Team
$40
per year per user
Enterprise
$210
per year per user
Wrike Free
$0
per month per user
Wrike Team
$10
per month (billed annually) per user (2-15 users)
Wrike Business
$25
per month (billed annually) per user (5-200 users)
Apex
Request a quote
per month per user
Pinnacle
Request a quote
per month per user
Offerings
Pricing Offerings
GitHub
Wrike
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Every premium plan begins with a 14-day trial period.
We are currently using all of these products. Each of them does some things really well. Confluence is great for documentation on functionality that isn't changed frequently or to define how a business unit captures metrics. GitHub is good for source control, but we use Wrike to …
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
I think that Wrike is customizable enough to fit most needs, so I would generally recommend it as a starting point to anyone that is looking for a project management tool. Some people on my team don't like it, but I think that is moreso due to lack of exposure than any flaws in the tool itself. I predominately taught myself many of the features, and I found it to be straightforward. There is lots of great documentation out there, plus the community forums are incredible helpful as well. Wrike might not be THE perfect tool for every single need, but I think that there would be very few situations where it would ultimately be incompatible with a team's workflow needs.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
I wish that Wrike had more drag and drop functionality that would be connected to assignee and also I wish that the finish date of a task would update to the date where you checked completed. It does not do that. Also finishing a task doesn't move the start date of the next task it "protects your time in that way", but our management team wants us to quickly see what we have down the pipeline rather than having to scroll down the list of upcoming tasks.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
It's easy as pie to use. I don't have any issues and only the oldest, most un-tech savvy of coworkers on my team seems to have issues with it. It's quick to pick up, intuitive, and effective. I have no criticism for it.
Over two years of (almost) daily usage without outages. Don't remember any errors. I give it 9 only because some Wrike plugins (for online document edit) are based on NPAPI architecture. These types of plugins are being phased out in new browsers, and NPAPI plugins are disabled by default in recent versions of Chrome so you have to do some browser adjustments when you switch browsers or move to another computer.
Wrike tasks loads fine, but I hate clicking files and wait for a bit of time since it is powerpoint or word, Wrike assumes I want to open those on Wrike. My suggestion is to link it to office 365 so we do not need Wrike based decoder for PPTX and DOCX
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
During my learning phase with Wrike, I initially struggled with setting up automation rules and request forms. However, Wrike support was always my go-to, resolving issues within seconds or minutes. Their assistance made the learning process much easier. My best experience was receiving step-by-step screenshots to follow, with the support team on standby until I was completely satisfied.
I love the Wrike training options. Wrike Discover has tons of courses, learning plans, certifications, etc. This is an area where Wrike definitely shines! I wish these resources were more in your face for new people, because it seems like a lot of coworkers didn't know all of this training was available to them.
There are a lot of bells and whistles in Wrike, and not all of it is easy or intuitive to understand once it's plopped in your lap. It's easier when there are a few choice people who understand Wrike as a platform and articulate it in such a way where it makes it easy to pass it along to others in the group
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
We use both monday.com and Wrike. While Monday does have a better user interface, Wrike allows us to have more visibility into tasks where multiple people are collaborating. And also to receive project brief-ins and requests for new projects. We use both differently and I would say for us Wrike is more the collaboration tool than the day to day individual task management tool - and it works great.
The sky is the limit for what can be done in Wrike. We started with 1 use case and within 5 months we migrated several key business practices over to Wrike because they were easier to manage. Use cases so far: process improvement, management review, corrective actions, maintenance requests, month-end financial closing, and document management. As we grow, it's easy to imagine putting even more into Wrike where it becomes a cornerstone for how we do business
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.
Different teams (e.g., contracting, compliance, provider relations) can view updates in real time, comment directly on tasks, and escalate items when needed.
Wrike allows us to template the contracting process (from intake to signature) to ensure consistency across payers and reduce administrative overhead.
Leadership can see the status of negotiations at a glance, identify bottlenecks, and prioritize resources accordingly.
