Nextflow

“Dataflow variables are spectacularly expressive in concurrent programming”
Henri E. Bal , Jennifer G. Steiner , Andrew S. Tanenbaum

Nextflow CI Nextflow version Nextflow Twitter Nextflow Publication install with bioconda Nextflow license

Nextflow is a workflow system for creating scalable, portable, and reproducible workflows. It uses a dataflow programming model that simplifies writing parallel and distributed pipelines by allowing you to focus on data flow and computation. Nextflow can deploy workflows on a variety of execution platforms, including your local machine, HPC schedulers, and cloud. Additionally, Nextflow supports a range of compute environments, software container runtimes, and package managers, allowing workflows to be executed in reproducible and isolated environments.

Get started

To get started with Nextflow:

  1. See the Nextflow overview to learn key concepts.

  2. Download and install Nextflow.

  3. Set up an environment with the Nextflow VS Code extension.

  4. Run your first script.

To continue learning about Nextflow, visit the Nextflow community training portal and find a training course that is right for you. Seqera, the company that develops Nextflow, also runs a variety of training events. See Seqera Events for more information.

Community

You can post questions in the Nextflow community forum or the Nextflow Slack. Bugs and feature requests should be reported as GitHub issues.

The Nextflow community is highly active with regular community meetings, events, a podcast, and more. You can view this material on the Nextflow YouTube channel.

The nf-core project is a community effort aggregating high-quality Nextflow workflows that can be used by everyone.

Contributing

Contributions to Nextflow are welcome. See Contributing for more details.

License

Nextflow is released under the Apache 2.0 license. Nextflow is a registered trademark.

Citations

If you use Nextflow in your work, please cite:

P. Di Tommaso, et al. Nextflow enables reproducible computational workflows. Nature Biotechnology 35, 316–319 (2017) doi:10.1038/nbt.3820