The node library

A broad bioinformatics catalog, organized for the canvas.

943 built-in nodes across 51 categories, with metadata used to plan environments and make workflow requirements visible.

943 nodes · 51 categories · 22 templates

rnaseq.pipeline
running
0Built-in nodes
0Categories
0Templates
rnaseq.pipeline
$ ready ✓

The library

Built-in tools. Visible environments.

943 built-in bioinformatics nodes across the stack. BioNodulo uses their package metadata to plan and provision supported environments while keeping those requirements visible before a run.

nodes
943

nodes

categories
51

categories

bundled templates
22

templates

What’s inside

Visible requirements, reusable workflow pieces.

The library ships today. A hosted registry with versioning and publishing is the roadmap — clearly labeled below.

shipped

943 nodes, one palette

QC, alignment, variant calling, single-cell, assembly, metagenomics, proteomics, methylation, spatial and more — search the palette and drop the node you need onto the canvas.

shipped

51 categories

Nodes are organized into 51 categories spanning the whole stack, so you can find the right tool by domain instead of memorizing package names.

shipped

Per-node dependency metadata

Nodes carry package metadata that BioNodulo uses to plan and provision supported environments. Contract and execution evidence remains visible as the catalog is certified.

shipped

Custom nodes

Load your own custom nodes from configured local directories to extend the library with lab-specific tools and wrap scripts you already trust.

shipped

Bidirectional converters

Import and export workflows to and from SnakeMake, NextFlow, CWL, Galaxy, so a BioNodulo graph doesn't lock you in and existing pipelines can come along.

roadmap

Hosted registry

A public/private registry service for discovering, versioning, and publishing nodes — with a trust and sandboxing policy — is the direction, not yet a live product.

Build from visible, reusable pieces.

Open a template, search 943 built-in nodes, and inspect the environment plan before execution. Load your own custom nodes to make the library yours.