Case Study: Why we migrated our production infrastructure from Portainer CE to Arcane

[basturkerhan]

Hi Arcane Team and Community,

I wanted to share a technical case study about why we recently decided to completely drop Portainer Community Edition in our production environment and migrate our standalone Docker hosts to Arcane.

Long story short: We desperately needed native OIDC authentication and flexible webhook automation for continuous deployment, without moving away from open-source. Arcane solved both problems out-of-the-box.

An unexpected bonus was the resource efficiency; our management container footprint dropped from ~150MB RAM (Portainer) to around ~67MB (Arcane). The built-in Compose linter is also a massive lifesaver when editing configuration files over headless servers.

I've documented our entire migration strategy, Docker Compose setups, Jenkins webhook integration, and resource comparison in a detailed blog post on my personal website:

🔗 Full Case Study: https://erhanbasturk.com.tr/blog/en/switching-from-portainer-to-arcane-docker-management/

Thank you so much for building such a lightweight, robust, and dev-friendly tool! Thought the community and the maintainers might appreciate a real-world production use-case.

[kmendell]

I will add this to the community section on the website if thats alright with you? i like to see stories and journeys like this and share them with the community :)

[basturkerhan]

I’d be honored! Thank you for the kind words. I’m glad my story resonates with you, and I’m happy to have it shared with the community.