Portainer is a centralized container management platform for containerized apps and IoT device management. It helps accelerate container adoption and reduce time-to-value on Kubernetes, Docker, and Swarm with a management portal, allowing users to deliver and manage containerized applications from the data center to the edge. Portainer helps - Reduce the operational complexity associated with multi-cluster management Bridge the skills gap and facilitate feature…
$0
Pricing
Apache Mesos
Portainer
Editions & Modules
No answers on this topic
Portainer Business - 3 Nodes Free
$0
Home & Student
$149
per year
Starter
$995
per year
Professional
$2995
per year
Enterprise
Contact Sales for Pricing
per year
Offerings
Pricing Offerings
Mesos
Portainer
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Mesos
Portainer
Features
Apache Mesos
Portainer
Container Management
Comparison of Container Management features of Product A and Product B
Mesos is really great when you have a big datacenter with many different applications and use cases. It will help you to optimize the resource usage, being a centralized API for your infrastructure. It will not suit well for small companies that just need to deploy a web app. In this case, I would recommend something smaller.
Many developers, especially lesser experienced developers, don't have a really good background in setting up containers from the command line. Portainer is invaluable to them. Giving a UI to them gives them much more confidence and allows them to learn properties and capabilities of containers under far less stress. On the flip side of this, giving then a UI on a production system can lead to chaos...never give junior developers access to production servers.
Mesos may have many frameworks. If you have Mesos installed on your servers, you may use it for many kinds of tasks. Today we're running only web applications but the idea is to install a different framework for big data soon.
Separating server maintenance with application development, providing a clear user interface for developers who don't want to worry about the underlying server.
RBAC for container deployment linked to a SAML IDP, not something particularly easy in a native Docker instance but point and shoot in Portainer, allowing the use of Azure / Okta etc to provide user access.
Image management with multiple repositories is super clear and reduces incidents
Unreliable deployments that would fail for no good reason. Sometimes our Docker container would be "restarting" forever because Mesos thought it didn't have enough resources to start the container.
Impossibly slow UI. Built in React under the hood with a lot of bloatware backed in, so loading the Mesos UI on a slow internet connection was painful.
No real logging solution - it would stream "console.log()" output to the UI, but searching for logs wasn't really possible without downloading a huge file.
No built-in support for redeploying containers from a CI. We had to create a service whose whole job was to expose an HTTP endpoint that restarted a container, and then made Circle CI ping the endpoint whenever we wanted to redeploy.
Lack of granular RBAC control: While Portainer does have role-based access control (RBAC) features, they are not as granular as some users would like. Some users have reported that they would like to have more control over permissions for individual users or groups. This would enable more fine-grained control over who has access to which containers or clusters.
Limited support for non-Docker container technologies: While Portainer is primarily designed to manage Docker containers, it does have some limited support for other container technologies like Kubernetes and Docker Swarm. However, this support is not as robust as it is for Docker, and some users have reported that they would like to see better support for other container technologies.
Limited control over container networking: Portainer's networking features are somewhat limited compared to other container management tools. Some users have reported that they would like more control over container networking, including the ability to create custom networks and control IP addresses.
Accessibility for Non-Experts: even with some people having a bit longer on-boarding it is still very simple Quick setup is insanely useful, we can get it running in 10 seconds after installing docker Portainer has once again super clean UI and is very user friendly. Deployment/monitoring and management are super easy. I can tell just from a glance if something is out of date (watching at you Watchtower not doing your job for some reason)
One of their staff members jumped on a video call immediately with me and led me through the problem and solution during a quick session of screen sharing. In this day and age that is above and beyond, especially when it comes to software. It took approximately 5-10 minutes to diagnose and fix, including pleasantries!
Kubernetes is by far the best choice. More reliable and better developer experience. Mesos is prone to sporadic failures and not really designed to handle CI/CD-based deployments. Docker Cloud once shut down our entire cluster for "upgrades" without giving us any warning.
Portainer takes the cup in terms of usability and features. It is also more useful for smaller deployments, whereas Kubernetes in our opinion and experience, could probably be more suited to certain other use cases. Portainer is also a fresh feel among all the preexisting container management solutions and brings positivity and a new breeze in the industry.
Instead of having 1 senior who does all the setup, debugging and caretaking of "all things docker" we now split the load on basically everyone in the team. Hard to put into direct numbers but with everyone helping themselves, noone alone is forced into that position "because you know how to do it" and overall we're more productive
