Seqera Platform Feature Requests

The current implementation of Studios requires wildcard certificates to manage the in-application URL routing. This can be a blocker for adoption at Enterprise organizations that cannot issue wildcard certificates due to security concerns.

Currently, Studios cannot be used with Fusion-enabled Kubernetes CEs (Amazon EKS and Google GKE). Adding this will allow for greater control and more direct management of CEs for compliance, scale, and cost management purposes.

Currently, real-time in-notebook collaboration is only available in Jupyter, VS Code and Xpra containers because RStudio only supports this feature with a paid Pro license. Adding support in RStudio will require the ability to attach a Posit license to a Studio session.

When creating a Studio sessions, it is possible to associate key-value resource labels to the session. These resource labels are displayed in the UI as tags, but the list of Studios does not provide the ability to filter or sort the studios based on the key or value of these labels. For larger workspaces with many studios, it would be helpful to subset the available sessions to those with particular keys and/or particular values.

Trusted research environments enabling research progress without sacrificing data security - ensuring data are handled in a secure and responsible manner. The following five general items need to be adhered to: Safe Data - Confidentiality of data is maintained Safe Projects - Data owners approve the research projects Safe People - Researchers are trained to use the data safely Safe Settings - A secure computing environment prevents unauthorised data access Safe Outputs - All exported results are screened and approved

Devcontainers is a standard format developed by Microsoft to configure development environments for VSCode and GitHub codespaces . It’s also going to be supported by GitPod . It’s a JSON file that sits in the root of a repo in a directory called .devcontainer/ . It can contain VSCode extensions, etc but the key things are: Dockerfile, docker arguments, and launch run commands. Supporting these files in Studios allow users to programmatically encode settings for Studios using a well adopted standard.

Currently, to interact with a Shiny/Dash/Streamlit dynamic dashboard you have to be connected to a running Studio session and manually execute the code, which typically opens a new browser window. The new application internal browser window creation process bypasses the current connect protocols and is therefore non-shareable. Making interactive dashboard URLs shareable across workspace participants would allow rapid feedback and iteration for notebook analyses/processes.

Currently, AWS Batch without Fargate is the only supported compute environment (CE) for Studios. Adding support for HPC environments (like Slurm) would benefit many customers who want to adopt interactive analyses within their HPC deployments.

In the "About" tab of a completed task, it would be nice to have a link to launch a studio environment using the same image, and with the input data linked/copied into the environment. It would be a convenient way to quickly test different settings on a given step/tool.

It would be helpful from security and compliance perspectives to allow Enterprise installations of Seqera Platform to support custom subdomains for Studios.