I think this can be done relatively easy in the current infrastructure. We can have a cookiecutter to create new bokeh apps in the squash-bokeh repository creating a template based on
https://github.com/lsst-sqre/squash-bokeh/tree/master/app/monitor

The new apps can be organized by verification package in that repo, something like:

squash-bokeh/apps/

  /verify

     /validate_drp

        /code_changes

        /AMx

        /PAx

     /jointcal

  /sysver 

    /monitor

    /camera

  /opsim

    /monitor

NOTE: Depending on the number of bokeh apps and scalability required we might want to change the deployment architecture to run multiple bokeh servers, and at this point probably the cookie cutter would create a separate repository for each bokeh.