A decade ago we used another solution which seemed to work well enough: Developers had a Unix accounts on a Linux server. Their workspace was mounted as a remote filesystem. Interactive console access was available via SSH.
Inlets seems to still require a remote Linux server, but seems a like a more complicated way to solve the problem.
By using a shared server, we didn't need maintain container image to keep laptop environments sync'ed. If we wanted to upgrade the development database version, we upgraded the DB once on the shared server and everyone had the new version immediately.
I've used ngrok before and it's a great solution for quick tests. I guess this is an open-sourced version of that.
I'll bookmark this in case I have this need in the future.