JFrog Artifactory vs. Mirantis Kubernetes Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
JFrog Artifactory
Score 8.1 out of 10
N/A
JFrog Artifactory is a software repository management solution for enterprises available on-premise or from the cloud, presented as a single solution for housing and managing all the artifacts, binaries, packages, files, containers, and components for use throughout the software supply chain. JFrog Artifactory serves as a central hub for DevOps, integrating with tools and processes to improve automation, increase integrity, and incorporate best practices along the way.
$150
per month
Mirantis Kubernetes Engine
Score 9.3 out of 10
N/A
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
$500
per year per node
Pricing
JFrog ArtifactoryMirantis Kubernetes Engine
Editions & Modules
Pro
$150
per month unlimited users
Enterprise X
$750
per month unlimited users
Pro
$3,500
per year
Pro X
$21,500
per year
Enterprise X
$43,500
per year
Enterprise+
Custom Pricing
Enterprise+
Custom Pricing
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
JFrog ArtifactoryMirantis Kubernetes Engine
Free Trial
NoYes
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsThese pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
More Pricing Information
Community Pulse
JFrog ArtifactoryMirantis Kubernetes Engine
Top Pros
Top Cons
Best Alternatives
JFrog ArtifactoryMirantis Kubernetes Engine
Small Businesses
Git
Git
Score 10.0 out of 10
Portainer
Portainer
Score 9.3 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
Docker
Docker
Score 9.2 out of 10
Enterprises
Git
Git
Score 10.0 out of 10
Docker
Docker
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
JFrog ArtifactoryMirantis Kubernetes Engine
Likelihood to Recommend
8.4
(8 ratings)
8.3
(37 ratings)
Likelihood to Renew
-
(0 ratings)
9.1
(1 ratings)
Usability
10.0
(2 ratings)
8.0
(2 ratings)
Support Rating
8.9
(2 ratings)
7.8
(3 ratings)
User Testimonials
JFrog ArtifactoryMirantis Kubernetes Engine
Likelihood to Recommend
JFrog
It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.
Read full review
Mirantis
[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs
and separates any single application from the dependencies. Also, this tool is
helping me in the agile development of the processes. It is strongly recommended to
almost all major organizations.
Read full review
Pros
JFrog
  • Artifactory Management acting as a repository manager of docker images, application and component dependencies
  • Automate pipelines and thereby releasing changes faster
  • Supports high availability and scalability with multi site replication
Read full review
Mirantis
  • Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
  • Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
  • CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.
Read full review
Cons
JFrog
  • We can always use support for more different types of packages in Artifactory.
  • We also would like to see the Artifactory X-Ray produce continue to mature.
Read full review
Mirantis
  • Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
  • Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
  • Networking is complexified due to internal port mapping between containers, etc.
Read full review
Usability
JFrog
The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.
Read full review
Mirantis
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
Read full review
Support Rating
JFrog
Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.
Read full review
Mirantis
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
Read full review
Alternatives Considered
JFrog
JFrog Artifactory has a much more friendly GUI, making package exploration less of a chore to do. Other than that, their features are pretty much comparable to each other. Both support multiple types of packages; both have API that can integrate well with CI/CD pipelines.
Read full review
Mirantis
We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.
Read full review
Return on Investment
JFrog
  • So many times it happens at the time of dependency resolution some of the servers are down e.g NPM, Maven central, PiPy in that cause our builds starts failing. By proxying these repositories with JFrog this is never happened again.
  • It reduced the additional cost of container image registry and management effort.
  • Support of integration with Build, Monitoring, and CI tools resulted in smooth automation and management.
Read full review
Mirantis
  • Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
  • Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
  • Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.
Read full review
ScreenShots