One possibility could be to manage the modules at the gateway level.
Suppose, I want to black-list a few modules. Or, want to apply an 'activation policy', etc. If not the network server itself, a 'management server' should be available on the gateway to enforce policies over modules. It maybe possible for the policies to 'cascade' over from cloud to gateway to modules - but, with the server hosted on gateway, some intelligence can be pushed on 'edge'.
In case of network server deployment, I could imagine a scenario where a gateway might double up as the host for the network server. For example, while the features of Symphony Conductor are desirable, one may not necessarily want a gateway to back-haul to open Internet to connect to Conductor on cloud.