GitLab is an intelligent orchestration platform for DevSecOps, where software teams enable AI at every stage of the software lifecycle to ship faster. The platform enables teams to automate repetitive tasks across planning, building, securing, testing, deploying, and maintaining software.
$0
Planview AgilePlace
Score 7.9 out of 10
N/A
AgilePlace is a project management solution built around flexibility, data-driven analytics, and workflow automation. The software was acquired by Planview in December 2017 to expand that company's capabilities.
$19
per user, per month
Pricing
GitLab
Planview AgilePlace
Editions & Modules
GitLab Free (self-managed)
$0
GitLab Free
$0
GitLab Premium
$29
per month per user
GitLab Premium (self-managed)
$29
per month per user
GitLab Ultimate
Contact Sales
GitLab Ultimate (self-managed)
Contact Sales
Teams
$19
per user, per month
Scaled Teams
$29
per user, per month
Custom
Contact Sales for Quote
per user, per month
Offerings
Pricing Offerings
GitLab
Planview AgilePlace
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
GitLab Credits enable flexible, consumption-based access to agentic AI capabilities in the GitLab platform, allowing you to scale AI adoption at your own pace while maintaining cost predictability. Powered by Duo Agent Platform, GitLab’s agentic AI capabilities help software teams to collaborate at AI speed, without compromising quality and enterprise security.
If usage exceeds monthly allocations and overage terms are accepted, automated on-demand billing activates without service interruption, so your developers never lose access to AI capabilities they need.
Real-time dashboards provide transparency into AI consumption patterns. Software teams can see usage across users, projects, and groups with granular attribution for cost allocation. Automated threshold alerts facilitate proactive planning. Advanced analytics deliver trending, forecasting, and FinOps integration.
GitLab is a cost effective alternative to names like GitHub and others. It provides easy to use interface that is not dissimilar from GitHub and Atlassian Bitbucket. Where GitLab really shines is in its simplicity and ease of use. It's very intuitive and effectively allows a …
It is easy to use , devsecops/ dataops / gitops implementation is quite easy and straightforward compared to other tools which we have tested , it provides seamless integration with tools like dbt , talend , snowflake , collibra and python. Merge issues as well as pipeline …
I liked GitLab better than Beanstalk. GitLab had a free option, which Beanstalk did not at the time. From what I have used of Bitbucket, I probably like it better than GitLab, specifically I like the design better. Doing things in Bitbucket seemed a bit slower to me though. Now …
GitLab is widely used throughout the developer community and provides all the required features industry wide. Many of the paid features help the team a lot to achieve efficient source code management. Many features like vulnerability management and AI chat while code review in …
Gitlab is an industry standard tool for version controlling of the source code with multiple features used by the developers to maintain efficient development process and scalable services integration on the larger code bases. Multiple tools like AI code review helps the …
GitLab is an industry standard software and provides alot of features helpful for the developers with a suitable price point. It has most of the features that are provided and are useful. Team management and security for the source code and restrictions helps achieve all the …
GitLab is an all-in-one Git and CI/CD platform that also offers generous credits in its free plan. It allows both private and public projects. The pipelines can be fully defined in YAML files put under version control.
GitLab is superior to beanstalk but still lacking in some areas in comparison to newer features to Github. However, it's enterprise based approach is very attractive to many of our top tier clients making it and effective solution for us within their organizations. It's well …
We have recently migrated from Bamboo to GitLab across our enterprise as part of our tech modernization roadmap. GitLab provides a all-in-one platform for integrated code management. The only advantage that Bamboo had over GitLab was the integration with JIRA. The streamlined …
In our case, we opted for an open source solution and complete control of information, meaning we kept critical information and company developments in-house.
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
Because it has the latest features, it is perfect for collaboration, has the best integrations available, and is super secure. Basically, it covers all my needs and the companies. I love its pipelines because of its secrets and agents. I also love that you can manage the …
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
AgilePlace is better than JIRA when it comes to ease of use and intuitiveness of the tool. Card based model and ability to customize/tailor the way you want makes AgilePlace is a great tool. Look and feel as well as colored cards, makes the board layout much more easier to …
All these tools are different and have different uses. Depending upon SDLC your organization uses, you would use any of these tools. They all have their plusses and minuses.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration.
Front-End Web Developer, Office of Mediated Education
Chose Planview AgilePlace
I use Trello a bit for personal use. It's much less powerful than LeanKit, but it's also a better design and simpler to use. ServiceNow has some kanban board stuff built-in, but I wasn't super impressed with it. JIRA seemed to be even more complex than LeanKit for the short …
I think that LeanKit is very similar to Asana's Kanban feature and Trello, but is much less sleek looking than Asana. Asana's clean and sleek UI makes me enjoy project management much more than LeanKit. It might sound silly that the UI makes so much of a difference to me, but …
Our company uses LeanKit, Pivotal Tracker, and Trello. It all depends on what team you're on. There's even a team that just does KanBan on a whiteboard. In the end, I would tank LeanKit above Pivotal Tracker, but below Trello. The differences are relatively subtle between …
Both VersionOne and Trello are good products. VersionOne is for the real hardcore Agile shops who want to track and report on everything related to the Agile process. Trello is a tool that works for Agile, but really is just a simple list making/tracking tool. Both tools serve …
I have used Trello, which is not as robust for tracking and customizing workflows as LeanKit is. It does not scale well to big teams. JIRA is the standard project management software but does not support Kanban well.
Nearly all the other tools I evaluated against are free, so that's one area where LeanKit is not as competitive. LeanKit does allow the experience to be much more customizable, though.
Being from QA I prefer Spiratest and QC for the fact my team can do all our work in one program and it is linked. But the tech department as a whole prefers Leankit as it is the tool of choice based on ease of use and overall performance.
While LeanKit was not designed for project and task management, we selected it because of its collaborative nature as a project and task management platform for our marketing team. It was also selected because our engineering and product management teams were using Leankit. We …
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
AgilePlace is a great way for teams, or individuals, to bring visibility to the work in process and in their backlog. The color coding and icon use helps to quickly analyze the type of work or status of the work. The product team is doing a good job at listening to their user's feedback and implementing improvements. Where it falls short is when reporting needs to occur.
Okta Integration: We love using SSO for all our SaaS apps, and as new team members join, they can be automatically joined to the appropriate LeanKit boards.
Filtering and viewing: Can filter and refine by several fields as well as custom fields. Assigned Users, Tagged, Card Type, Date, etc
Their analytics and reporting can be helpful for PMs, especially if they have several teams they oversee.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
LeanKit isn't the best designed Kanban system I've seen, but overall it's pretty usable. The boards I've used are pretty complex, so it can be difficult to find things. I found that searching and filtering for specific cards was somewhat of a challenge. Dragging a card from one lane to another is kind of a fun way to get things done though.
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
Every time I have reached out to the AgilePlace support team I have received a timely response in addition to professional & personal feedback. Their consultants are knowledgeable and the management team is happy to jump in and help when needed.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration. In the end, we picked Planview LeanKit because of several reasons: Aesthetics: The look was much more clean and professional. Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement. API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it. Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.