Years ago (2015) I had a customer (hospital) that had webcams installed above the incubators of newborn babies. The video images were offered to people at home via an old MS ISA server so that they could see their child at home (via a login).
That old ISA server needed to be decommissioned.
The video images where presented via an iFrame in a static web page. So I took the ISA webserver configuration, modified it so it could run as hosted content on the BIG-IP and exposed it via APM.
Every camera had an AD group assigned, so nurses could create a username and password per baby.
Years later the hospital outsourced their IT, that company wanted to use Netscalers. But they were unable to migrate this configuration to their Netscalers. And this solution is still used today.
When we managed DevCentral servers ourselves back in the day, we were in a vmware hosted environment. We provisioned APM for traditional SSLVPN access to manage the web, database, file, mgmt, and directory servers, but since everything was fairly flat from a network perspective, we decided against the traditional benefits of a jumpbox for managing the BIG-IPs and used a policy forwarding trick combined with an iRule to gain access to the GUI/CLI/API endpoints directly from our team laptops. Not as cool as @KeesvandenBos use case but it simplified things a lot for us.