It has JupyterLab 3.3.0 with collaborative mode enabled, and we can probably reproduce issues by using the one single account by working from multiple tabs.
We don't have persistent storage, so you start with the containers home directory with some misc files about installed packages etc. Anything you do in this staging hub will disappear on hub restart.
We don't have access to a s3 bucket as on the prod hub, but github-app-user-auth works to setup credentials to github and for you to push someplace.
In order to test and debug the issues we observe at hub.jupytearth.org with regards to data loss, we want a hub with RTC enabled and JupyterLab 3.3.0.