Corporate nets use 802.1X authentication, risk of a DHCP hijack is very low.

As someone who works in large corporate networks, we absolutely don’t assign static IPs outside of core network gear, it’s impossible to manage a fleet of servers in this way with scaling in mind.

Instead of doing a manual action in two different places and having to keep them in sync, just do it once on the DHCP server. Setting a static IP on the server is superfluous.

don’t do this, use DHCP reservations instead so you actually have a list of all your servers and most routers register hostnames in DNS for you which is even better.

My personal opinion, as soon as you’re charging and providing SLAs you’ve exceeded what you should be doing on a residential ISP.

I’d really recommend putting your app in a real cloud solution, which can provide actual load balancing via DNS natively for regional failover if you desire.