Docs · OGN platform
GPU-native genomics operating system
From raw reads to GIAB-validated variant calls in a continuous GPU pipeline. This is the control surface for the engine: CLI, pipelines, benchmarks, and deployment runbooks.
CUDA 12+Hopper · AmpereGIAB-validated flowsSchemas stable
Viewing
BioFlow quickstart
BioFlow quickstart
BioFlow is the deterministic workflow layer for life-science runs that need to be replayed, verified, and handed off without guesswork.
Use this page when you want the shortest path from a messy input, or a first workspace, to something you can trust later.
Pick your path
- Hosted workspace path: use the Omnis Genomics console if you want runs, telemetry, and team handoff in one place.
- Local core path: use the public BioFlow core repo if you want the deterministic CLI and evidence bundle flow on your own machine.
Real use cases
- Clean up a sample sheet and keep the artifact trail intact.
- Verify a run after the fact instead of trusting the original log.
- Export a signed bundle for QA, review, or downstream handoff.
- Share a run across a team without losing provenance.
- Let internal tools trigger safe workflow actions through the BioFlow API.
Hosted workspace path
- Open /platform/bioflow/signup and create a workspace.
- Run /platform/bioflow/onboarding to provision the workspace and expose the first operational surfaces.
- Use /platform/bioflow/runs to inspect run history and evidence.
- Use /platform/bioflow/settings to manage keys, billing, and workspace state.
- Use /platform/bioflow/telemetry when you need operator visibility.
If you are sending raw requests, keep the API reference open while you work: BioFlow API reference.
Local core path
If you are working in the public BioFlow core repo, start with the two canonical demo flows:
BashPowerShellPython API (coming)
ogn CLInpm run demo:sample-sheet:local
npm run demo:killerThen move to the evidence handoff flow:
BashPowerShellPython API (coming)
ogn CLInpm run bioflow -- verify <runId>
npm run bioflow -- bundle <runId> --out ./bundlesThe sample-sheet path is the fastest way to see the deterministic contract. The killer example is the full evidence path.
What to watch for
- Inputs should be treated as evidence, not as ad hoc files.
- Every run should produce a manifest, an execution record, and a verification path.
- If you cannot verify the output later, the workflow is not finished.