IBM Cloud Private vs. Portainer

IBM Cloud Private is well suited for SaaS models.

Incentivized

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.

Incentivized

• There is a large variety of services available on IBM Cloud.
• This is my first experience with a PaaS and I haven’t had any major problems navigating around it.
• It is easy to deploy applications and services on IBM Cloud.

Incentivized

• 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

Incentivized

• More hands on training outside of virtual classes would be helpful.

Incentivized

• 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.

Incentivized

It is an excellent tool.

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)

Incentivized

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!

It is really easy. Just follow the documentation.

Incentivized

With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.

Incentivized

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.

• N/A
• N/A
• N/A

Incentivized

• 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

Incentivized