Seqera Platform Feature Requests

Allow a Cloud organization owner/admin to allocate a defined amount of usage/CPU credits for its members, similar to what's done in the Community|Showcase for new users. This will allow public and private orgs to more granularly manage their organization resources.

It would be great if you could package your installation up into a helm chart, where we could simply set the necessary variables all in one place. This would simplify the container installation on EKS and have this much more repeatable in terms of installation. We have multiple environments to install this application in, and we've spun up EKS with Terraform. However, the installation of Seqera Platform is quite hands-on and manual. It would be a benefit to have a helm chart with the necessary configuration options available. Thanks MarkA

Could the Quick Launch configuration option in the Platform default to use the configured primary compute environment instead of being listed in alphabetical order?

In the "About" tab of a completed task, it would be nice to have a link to launch a data 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

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

As of v24.2 Enterprise, if the AWS credentials supporting an AWS Batch Forge compute environment are deleted, the AWS resources will not be cleaned-up upon compute-environment deletion. This is absolutely logical, of course. However, I think non-technical users could benefit from a explicit warning regarding orphaned resources if credentials are deleted.

Putting multiline comments and a markdown table render fine on the nf-core website, but not on Seqera platform. A link to the conversion on Slack is https://nfcore.slack.com/archives/CP3RJSMF0/p1739191319184859?thread_ts=1737642219.577559&cid=CP3RJSMF0 . A branch you could use to launch from a and see the issue on platform in action is this one: https://github.com/nf-core/methylseq/pull/506 Thanks!

seqera ai constantly logout after several mintues in vanilla firefox in ubuntu 22.04, logged in with github sign-in. quite a pain.

Pipeline development in Nextflow is often done using docker. When inside a VS Code environment within Studios, I want to be able to run: nextflow run main.nf -with-docker The requirement is to run fast, "local" iterations rather than requiring an external service like AWS Batch or similar, which has delays.

Its currently very hard to monitor executions when using trace commands.