Skip to content
Feature comparison between Docker Commander, Portainer CE, Dozzle, Arcane, Lazydocker
CapabilityDocker CommanderPortainer CEDozzleArcaneLazydocker
InterfaceWeb UIWeb UIWeb UIWeb UI + mobile appsTerminal UI
ScopeMonitor + full controlMonitor + full controlLogs + optional controlStart/stop/restart/remove/update are opt-in and role-gated, off by defaultMonitor + full controlMonitor + control
Runtime dependenciesOne binary, embedded SQLiteContainer with embedded DBOne container imageOne container imageOne CLI binary
Multi-hostYesAgentless — TCP+TLS or SSHYesAgent / Edge agent, or direct Docker API (TCP+TLS, legacy)YesAgent per host (or legacy remote TCP+TLS)YesAgent per host (direct or outbound edge, mTLS)Not built inOne daemon at a time — local or via DOCKER_HOST / docker context
Two-factor / passwordless loginYesTOTP or WebAuthn passkeys, enforced by defaultNot built inPassword, LDAP/AD or OAuth — MFA only via the identity providerNot built inLogin optional; GitHub/OIDC sign-in can delegate MFAYesPasskeys and recovery codes; no TOTPNot built inNo login of its own — relies on Docker / SSH access
Aggregated logs across containersYesLevel detection, regex, parse rulesNot built inPer containerYesIts whole purposePartiallyPer container and per projectNot built inPer container
Built-in alert rules → webhook / emailYesState, resource, network, log-pattern, crash-loop → webhook & e-mail, with retryNot built inAlerting is Business Edition onlyPartiallyLog, metric & event alerts → webhook/Slack/Discord/ntfy; e-mail only via hosted Dozzle CloudPartiallyEvent notifications for updates, CVEs and auto-heal via SMTP, chat and webhooks; no general threshold/log-rule engineNot built in
Maintenance windows / alert silencingYesScoped, one-off or weekly; auto-silence after a deployNot built inSilences are Business Edition onlyNot built inPer-rule on/off and cooldownNot built inNot built in
Prometheus exporterYesNot built inNot built inNot built inNot built in
Compose editing in the UIYesValidated editor + templatesYesSchema-validated editor, templates, Git-backed stacksNot built inYesCompose and .env editors, templates, Git syncNot built in
Deploy preview & rollbackYesDiff before deploy, drift detection, a revision per deploy, validated atomic restorePartiallyOne step back to the previous stack fileNot built inNo general deployment preview/history; failed image updates are automatically revertedNot built inNot built in
Policy checks before deployYesPrivileged, host namespaces, socket, :latest, limits, healthcheck — off / warn / blockPartiallyRestricts privileged, bind mounts, host PID… for non-admins onlyNot built inNot built inNot built in
Automatic HTTPS (Let’s Encrypt)YesFor the panel, and per container via the opt-in proxyNot built inOwn or self-signed certificateNot built inTLS at a reverse proxyNot built inOwn certificate or a reverse proxyn/aNo network listener
BackupsYesSelf-backup, recovery bundle, volume jobs wrapping your restic/borgPartiallyManual config download; scheduled & S3 are Business EditionNot built inYesBuilt-in Rustic volume backups, local or S3, scheduledNot built in
Image updatesPartiallyDetects a new digest and alerts; does not apply it yetNot built inUpdate indicator is Business Edition onlyYesManual, bulk and scheduled auto-update; failed updates restore the previous containerYesScheduled auto-updateNot built in
MCP server for AI assistantsYesOff by default, RBAC-scoped, read + safe controlPartiallySeparate, unsupported portainer-mcp serverYesRead-only, built-in, with OAuth/session-token auth; inherits roles and container filtersNot built inNot built in
Image vulnerability scanningYesTrivy, in-app, with CVE triageNot built inNot built inYesTrivy, with ignore and CSV exportNot built in
Sources

A cross has one meaning here: not documented as a built-in feature in the source above. Several of these projects cover the same ground through plugins, agents or a paid edition.