Skip to content
OGN logo
Omnis Genomics
Docs · BioFlow

BioFlow docs for runs, APIs, and operator telemetry

This lane covers workspace onboarding, proxy/API usage, telemetry, and the public quickstart paths behind hosted and self-serve BioFlow execution.

RunsAPI referenceTelemetryHosted workspace
Viewing
BioFlow quickstart
BioFlow overviewAPI referenceTelemetrySignup
Need another page?
Search the docs

Jump to buyers, verification, demos, self-hosting, or adapters without opening the full docs tree first.

Key sections
Pick your pathReal use casesHosted workspace pathLocal core pathWhat to watch forSee also
Mobile navigation
Jump to section
Open
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

  1. Open /platform/bioflow/signup and create a workspace.
  2. Run /platform/bioflow/onboarding to provision the workspace and expose the first operational surfaces.
  3. Use /platform/bioflow/runs to inspect run history and evidence.
  4. Use /platform/bioflow/settings to manage keys, billing, and workspace state.
  5. 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:
BashRunnable example
npm run demo:sample-sheet:local
npm run demo:killer
Then move to the evidence handoff flow:
BashRunnable example
npm run bioflow -- verify <runId>
npm run bioflow -- bundle <runId> --out ./bundles
The 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.

See also