Overview
Studios provides interactive analysis environments that pair a container image with a compute environment and your preferred tools, such as JupyterLab, an R-IDE, Visual Studio Code, or Xpra remote desktops. Each Studio session runs as an individual interactive environment for live data analysis.
Studios in Enterprise is not enabled by default. To enable it, see Deploy Studios in Seqera Platform.
- Container image templates: Provided templates for JupyterLab, R-IDE, Visual Studio Code, and Xpra.
- Custom environments: Augment the Seqera-provided images with Conda packages or your own base container template image.
- Add a Studio: Configuration options for creating, running, and customizing Studio sessions.
- Manage Studios: Manage Studios and collaborator access.
- Connect changelog: Release notes for the Seqera Connect client.
Studios supports AWS Cloud, Azure Cloud, Google Cloud, and AWS Batch compute environments that do not have Fargate enabled.
Networking
The Seqera Connect client inside a Studio session opens a tunnel outward to the Connect server and registers the session over it. All session traffic, including SSH when enabled, travels over that outbound connection. No inbound path to the session VM is required. Users reach a Studio through the Connect proxy rather than by connecting to the VM, so you do not need inbound rules or source-IP allow-lists for dynamically launched Studio VMs.
This applies to every compute environment that supports Studios. If you run Studios inside a private network, see the networking guidance on your compute environment page for the outbound connectivity to allow: AWS Cloud, Azure Cloud, Google Cloud, or AWS Batch. For the ports and directions to configure on your firewall, see Firewall configuration.