LIFE SCIENCES

Compute for
regulated research.

Genomics, imaging, drug discovery, and AI workloads on infrastructure you control, with the audit trail your compliance team needs.

Orion Admin×
+
←→↻
admin.your-institute.org/storage☆
⋮
Orion Admin mounts list with NFS shares
Orion Admin×
+
←→↻
admin.your-institute.org/storage☆
⋮
Orion Admin mounts list with NFS shares
Orion Admin×
+
←→↻
admin.your-institute.org/storage☆
⋮
Orion Admin mounts list with NFS shares

Why regulated teams run Orion

Customer-hosted, always

Orion installs into your environment and stays there. Sensitive data never leaves it.

Customer-hosted, always

Orion installs into your environment and stays there. Sensitive data never leaves it.

Customer-hosted, always

Orion installs into your environment and stays there. Sensitive data never leaves it.

Controls for compliance-sensitive work

Audit logging and group-scoped data access, inside your own environment. Your team owns compliance.

Controls for compliance-sensitive work

Audit logging and group-scoped data access, inside your own environment. Your team owns compliance.

Controls for compliance-sensitive work

Audit logging and group-scoped data access, inside your own environment. Your team owns compliance.

Every launch attributed

SSO mapped to POSIX. Every workload is tied to a named user, and the right person owns the right file.

Every launch attributed

SSO mapped to POSIX. Every workload is tied to a named user, and the right person owns the right file.

Every launch attributed

SSO mapped to POSIX. Every workload is tied to a named user, and the right person owns the right file.

Pipelines and people on the same plane.

Batch pipelines, Jupyter for analysis, and GPU workstations for imaging schedule against one cluster, under one identity.

JupyterLab×
+
←→↻
orion.your-institute.org/session/jupyter☆
⋮
JupyterLab launcher running as an Orion Workspace session

Jupyter with the lab's data already mounted.

JupyterLab×
+
←→↻
orion.your-institute.org/session/jupyter☆
⋮
JupyterLab launcher running as an Orion Workspace session

Jupyter with the lab's data already mounted.

JupyterLab×
+
←→↻
orion.your-institute.org/session/jupyter☆
⋮
JupyterLab launcher running as an Orion Workspace session

Jupyter with the lab's data already mounted.

Dim lab bench with a microscope and a sequencer

CONTROLS

Limit a mount to one group.

Mounts can be limited to one group, and each workspace has its own network rules. Put the HPC nodes you retired back to work.

Group mounts

Sensitive data only where it belongs.

Network rules

Ingress and egress per workspace.

Short-lived sessions

Open data in a workspace that goes away when you’re done.

60-90s

request to running workload

One

identity from login to file owner

Zero

phone-home calls, connected or offline

Questions regulated teams ask

Keep your research data where it is.

Book a 30-minute demo with an engineer, or install Community Edition and read the docs.

Keep your research data where it is.

Book a 30-minute demo with an engineer, or install Community Edition and read the docs.

Keep your research data where it is.

Book a 30-minute demo with an engineer, or install Community Edition and read the docs.