You can deploy the browser version with a Docker container in a remote server. With that, instead of running the client in your computer and connecting to the r

You can deploy the browser version with a Docker container in a remote server. With that, instead of running the client in your computer and connecting to the remote database, you can have the client running as a service in your servers. Then you can use all the DBeaver functionality (whatever they are providing in the browser version) by just navigating to it (the desktop application is quite heavy). Apart from that, I guess that from a team's point of view, you have better control of the database access than if you had to whitelist IPs. Now you can have the same access control policies in your database client than for any other service you are running. Yes, you could do the same by using the native database permissions systems, but it's just a use case I think of.