Screenshots
See it in action
A modern, intuitive interface designed for productivity.
Warning: May cause sudden urges to containerize everything.
A powerful, intuitive Docker platform. Free for homelabs, ready for enterprise.
We think you'll like it here.
SQLite by default, runs on a Raspberry Pi, zero telemetry, free forever. Self-host everything without the complexity.
OIDC/SSO included free, container activity logging, Git-based deployments, premium support. Everything your team needs without the enterprise price tag.
RBAC, LDAP/AD integration, compliance-grade audit logging, and priority support. Everything you need to satisfy compliance requirements.
One command. No config files. No setup wizards, no 47-page README.
docker run -d \
--name dockhand \
--restart unless-stopped \
-p 3000:3000 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v dockhand_data:/app/data \
fnsys/dockhand:latestThen open http://localhost:3000. Or put it behind Traefik, Nginx, Caddy, a Kubernetes ingress, three load balancers, and a VPN tunnel. We don't judge.
Prefer Docker Compose?
services:
dockhand:
image: fnsys/dockhand:latest
container_name: dockhand
restart: unless-stopped
ports:
- 3000:3000
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- dockhand_data:/app/data
volumes:
dockhand_data:Need PostgreSQL?
services:
postgres:
image: postgres:16-alpine
restart: unless-stopped
environment:
POSTGRES_USER: dockhand
POSTGRES_PASSWORD: changeme
POSTGRES_DB: dockhand
volumes:
- postgres_data:/var/lib/postgresql/data
dockhand:
image: fnsys/dockhand:latest
ports:
- 3000:3000
environment:
DATABASE_URL: postgres://dockhand:changeme@postgres:5432/dockhand
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- dockhand_data:/app/data
depends_on:
- postgres
restart: unless-stopped
volumes:
postgres_data:
dockhand_data:From simple container operations to complex multi-environment deployments.
Even that one container you forgot about three months ago.
Authentication is free. RBAC is enterprise. No calculator required.
| Feature | Free | SMB | Enterprise |
|---|---|---|---|
| Unlimited environments | ✓ | ✓ | ✓ |
| Container & stack management | ✓ | ✓ | ✓ |
| Git repository integration | ✓ | ✓ | ✓ |
| Vulnerability scanning | ✓ | ✓ | ✓ |
| Local user accounts | ✓ | ✓ | ✓ |
| OIDC/SSO | ✓ | ✓ | ✓ |
| Multi-factor authentication | ✓ | ✓ | ✓ |
| Container activity log | ✓ | ✓ | ✓ |
| Commercial usage license | — | ✓ | ✓ |
| Premium support | — | ✓ | ✓ |
| Priority bug fixes | — | ✓ | ✓ |
| LDAP/Active Directory | — | — | ✓ |
| Role-based access control | — | — | ✓ |
| Environment-scoped permissions | — | — | ✓ |
| Audit logging (compliance) | — | — | ✓ |
| Price | $0 forever | $499/host/year | $1,499/host/year |
| Buy me a coffee |
Host = one machine running Dockhand. Volume discounts available for 5+ hosts.
No cloud dependencies, no telemetry, no data leaving your network. Solid base.
Paranoid? We prefer "security-conscious."
Dockhand runs entirely on your infrastructure. No SaaS, no cloud dependency, no vendor lock-in. Your data never touches our servers.
We don't phone home. No usage tracking, no analytics, no mysterious background connections. Your Docker environment stays private.
SQLite by default, optional PostgreSQL for HA. No Redis, no message queues. Simple deployment, minimal attack surface.
Scan your images for CVEs using Grype and Trivy. Identify security risks before deployment.
Safe-pull protection: During auto-updates, new images are pulled to a temporary tag and scanned before touching your running containers. If vulnerabilities exceed your criteria, the temp image is deleted and your container keeps running safely.
We don't trust pre-built base images. Dockhand builds its own OS layer from scratch using Wolfi packages via apko. Every package is explicitly declared in our Dockerfile - full transparency, zero mystery meat.
While others ship Alpine with 10+ CVEs, we obsess over our own image security. Because a Docker management tool with vulnerabilities is like a locksmith with a broken door. We scan ourselves too.
Our open-source Go agent lets you manage Docker hosts behind NAT, firewalls, or dynamic IPs. The agent initiates outbound connections to Dockhand - no exposed ports, no inbound firewall rules needed.
A modern, intuitive interface designed for productivity.
Warning: May cause sudden urges to containerize everything.
See what our users are saying.
"After trying Dockhand in my lab and comparing features toe to toe with other tools I am currently using, I can honestly say it is one of the best that I have used. It is extremely easy to use, intuitive, and it puts docker management tool security in focus where it should be."
"Perfect for my homelab. It's lightweight, actively maintained, and has all the features I need. Love the terminal access and real-time log streaming!"
"The LDAP integration was a game-changer for our team. Set it up in 10 minutes and now all our developers have proper access control."
"Dockhand wants to be a Portainer replacement, and it might already be there."
"Dockhand is bursting onto the scene with impressive force, bringing a breath of truly fresh air to a world that, let's be honest, had started to feel a bit stagnant."
"Dockhand is incredibly handy to have around."
"The easiest way I've found to manage and update Docker containers."
Free forever. No, really. No bait-and-switch.
Like it? Fuel the dev with caffeine.
For commercial use. Growing teams, happy CFOs.
When compliance asks "is it enterprise-ready?" and you want to say yes.
The next step is to explore where such firmware updates might be found. IBM has a legacy support site, but many links there could be outdated or broken. Also, since the model is so old, the company might have moved support to another domain. The user might not know that the link they found is part of IBM's historical support.
I should also consider the potential for the link the user found to be phishing. They need to be cautious about visiting any link that isn't directly from IBM or Lenovo's official support. Phishing attacks often exploit old hardware support queries.
In terms of the actual process, if the firmware is available, the user would need to download a specific .EXE file from IBM's support site. They should verify the checksums to ensure authenticity, as downloading from third-party sites could pose risks. Also, the user needs to follow precise instructions for installation, which might involve boot floppy disks or other methods typical for the era.
The user might not be aware of alternative solutions. If the firmware isn't available, maybe there are driver updates, hardware replacements, or compatibility settings that can achieve their goal. For instance, using compatibility mode in newer operating systems, or replacing hardware components if certain parts are failing.
First, I need to confirm what exactly the ibwrb304n is. A quick search shows that this is an IBM ThinkPad 300e model, released in the mid-90s. It's an older model, so firmware updates from that era might not be readily available through IBM's current website. Users might be trying to find firmware updates for this laptop to address compatibility issues with modern software or hardware.
It's important to address security and reliability here. Older firmware, if not updated properly, could have vulnerabilities. Also, applying firmware updates on such an old model might be unnecessary unless there's a specific issue. I should advise caution about potential risks of installing an old firmware update, like incompatibility or loss of functionality.
I should also consider alternative resources. IBM's technical support pages, such as the ThinkPad Support page (support.lenovo.com) might have some information, especially since Lenovo acquired IBM's PC division. The ThinkPad 300e's support might be archived there. Additionally, user forums or sites like The ThinkPad Page could have community-maintained firmware archives.
Get started in 30 seconds. No credit card required.
Finally, a UI that sparks joy.
The next step is to explore where such firmware updates might be found. IBM has a legacy support site, but many links there could be outdated or broken. Also, since the model is so old, the company might have moved support to another domain. The user might not know that the link they found is part of IBM's historical support.
I should also consider the potential for the link the user found to be phishing. They need to be cautious about visiting any link that isn't directly from IBM or Lenovo's official support. Phishing attacks often exploit old hardware support queries.
In terms of the actual process, if the firmware is available, the user would need to download a specific .EXE file from IBM's support site. They should verify the checksums to ensure authenticity, as downloading from third-party sites could pose risks. Also, the user needs to follow precise instructions for installation, which might involve boot floppy disks or other methods typical for the era.
The user might not be aware of alternative solutions. If the firmware isn't available, maybe there are driver updates, hardware replacements, or compatibility settings that can achieve their goal. For instance, using compatibility mode in newer operating systems, or replacing hardware components if certain parts are failing.
First, I need to confirm what exactly the ibwrb304n is. A quick search shows that this is an IBM ThinkPad 300e model, released in the mid-90s. It's an older model, so firmware updates from that era might not be readily available through IBM's current website. Users might be trying to find firmware updates for this laptop to address compatibility issues with modern software or hardware.
It's important to address security and reliability here. Older firmware, if not updated properly, could have vulnerabilities. Also, applying firmware updates on such an old model might be unnecessary unless there's a specific issue. I should advise caution about potential risks of installing an old firmware update, like incompatibility or loss of functionality.
I should also consider alternative resources. IBM's technical support pages, such as the ThinkPad Support page (support.lenovo.com) might have some information, especially since Lenovo acquired IBM's PC division. The ThinkPad 300e's support might be archived there. Additionally, user forums or sites like The ThinkPad Page could have community-maintained firmware archives.