Recipes → Hub → Registry
Tools are declared as YAML recipes, validated and built by biochef-hub (SBOM, SLSA, cosign), then published as signed bundles to the BioChef Registry.
Peer-reviewed·BMC Bioinformatics, 2026
Genomics toolsin a browser tab
An open catalogue of bioinformatics tools that run end-to-end in your browser. No installs, no uploads.
Platform pillars
What you get
A signed publishing pipeline, a browser-native runtime, and a workflow editor. All open source.
Browser-native WebAssembly
Every published tool runs client-side in WebAssembly. Open the BioChef app, drop in a sequence, and execute. No installs, no uploads, no servers.
Drag-and-drop DAGs
A DAG editor chains tools end-to-end. Tools are filtered by data type, parameters re-execute live, and recipes can be saved and shared.
System design
Architecture at a glance
A YAML recipe in Git, signed by the Hub CI, served from the BioChef Registry, and run as WebAssembly in your browser.
System map
How a tool reaches your browser
A YAML recipe is built and signed by biochef-hub, published as a content-addressable bundle in the BioChef Registry, then fetched by digest and executed as WebAssembly inside your browser tab.
- 01RecipesYAML source
- 02HubCI · sign · publish
- 03RegistrySigned OCI bundles
- 04BrowserWebAssembly runtime
Standards
Ecosystem fit
Built on open standards and designed to integrate with existing infrastructure.
Runtime
WebAssembly
Bioinformatics tools compiled with Emscripten and biowasm; everything runs in the browser.
Distribution
OCI Registry
Signed bundles published to registry.biochef.app with SBOM and SLSA provenance.
Provenance
Sigstore cosign
Every recipe is built, tested, signed, and an immutable digest is recorded in the signed index.json.
Try it now
Open the BioChef app in your browser
Pick a tool, paste a sequence, run it. The whole catalogue is one click away.