PestWarsaw
Member
Same here
it works in my container
Poll: what do you use for remote KVM when IPMI dies?
Same. Built, tested, trusting. Will add serial later. For now: PiKVM primary, IPMI when it feels like it, and the building owner's phone number is still in my contacts but I hope never to use it.
Good thread. Good people. Goodnight from Tallinn.
builds at 3AM, sleeps at noon
phasmapiotr
Member
Good thread. I remain lazy with my one box and OVHcloud Warsaw support, but I am convinced. When I add a second box, PiKVM is happening.
Polish hosting: still underrated. French support in Poland: still slow. But the latency is excellent.
harbourops
Member
Late to the thread but confirming: I have deployed PiKVM at three client sites now, all previously using IPMI that failed at bad moments. Zero regrets. The bracket prints well, the Recom is stable, the support burden is down.
For the professionals here: it scales. Not just homelab. Small business, remote office, anywhere you can't afford a 3am drive.
Charge accordingly.
harbourops said:
It scales
Important point. This started as a "what do you use" thread for enthusiasts, but the answer applies broader. Anywhere you need reliable out-of-band access, PiKVM or similar is the answer.
The enterprise KVM vendors should be embarrassed. They won't be. They will just lose market to a $50 Pi and some open source.
Good.
3-2-1 or you're already dead
Last word from me: the STL is now on GitHub, link in profile. Parameterized for different panel spacing, different Pi models. Print, build, share improvements.
The community built this thread. The community builds the tools. That's how it should be.
Rack on.
visit twice: install and decom