UnifiedFlowInfrastructure for Evidence

IT & Security

Built to work withinyour institution’s environment.

Onboarding establishes the approved environment, access, data boundaries and operating responsibilities for your deployment. Begin with a clear view of what your institution is being asked to approve.

Request technical review materialsExplore the responsibilities
An agreed environment for research and technical supportAn institutional research suite contains research storage and an analysis workstation. An authorized staff member approaches the access checkpoint. A researcher and technical partner review the operating environment together at a shared worktable.Institution-controlledResearch data & outputsAuthorized accessFor an approved purposeTechnical reviewThe environment, agreedShared responsibilityAgreed roles. Continuing support.

An agreed boundary for the work

Clear boundaries.
Shared responsibility.

See what your institution is asked to approve: research storage, processing arrangements, authorized access and the responsibilities that keep the workflow operating.

01 / Research materials

Keep research materials under institutional control.

Persistent research data and scientific outputs remain in institution-controlled storage. Source recordings, processed data, analysis artifacts and lab-owned materials belong within that research boundary.

The institution retains control of research storage and its backup arrangements.

Establish during technical review
Research materials
Source data, processed data, analysis artifacts and scientific outputs.
Storage
Approved persistent locations, retention and backup responsibilities.
Platform boundary
UnifiedFlow provides software, orchestration, models, analysis capabilities and platform infrastructure.
A stable home for the research. The storage boundary contains persistent research files and scientific outputs. Platform components and services have separate responsibilities.Institution-controlled storagePersistent research filesSource dataProcessed dataScientific outputsInstitution · Storage + backup
The storage boundary contains persistent research files and scientific outputs. Platform components and services have separate responsibilities.

02 / Processing arrangements

Agree where processing runs and what moves.

Compute may be on premises, in an approved cloud environment or hybrid. Define the selected inputs, output destinations and any temporary copies required for the workflow.

Institution-controlled storage does not mean data never leave institutional premises.

Establish during technical review
Compute
Locations and capacity approved for the selected workflow.
Data paths
Which inputs, outputs or metadata cross each boundary.
Temporary copies
Any processing copies and their handling are deployment-specific.
Processing has a defined path. Selected inputs and returned outputs connect the approved processing environment to research storage. No specific topology or cloud arrangement is implied.Institution-controlled storageSource dataProcessed dataScientific outputsSelected inputsReturned outputsApproved processingOn premises · cloud · hybridAgreed data paths
Selected inputs and returned outputs connect the approved processing environment to research storage. No specific topology or cloud arrangement is implied.

03 / Authorized access

Give technical access a defined purpose.

Authorized UnifiedFlow personnel require access to support the environment. The lab and institutional reviewers establish the permitted scope and approved technical and security controls during onboarding.

Support access does not grant unrelated rights to use research data.

Establish during technical review
People
Authorized researchers, institutional reviewers and support personnel.
Controls
Authentication and technical access appropriate to the approved deployment.
Purpose
Operation, troubleshooting and support within the approved scope.
People act within an approved scope. The roles illustrate research, institutional review and technical support. They do not imply a universal identity integration or unrestricted remote access.Platform servicesSoftware + orchestrationConfiguration + supportApproved accessLab researchersScientific workInstitutional ITReview + approvalsAuthorized supportTechnical operationNo unrelated data-use rights
The roles illustrate research, institutional review and technical support. They do not imply a universal identity integration or unrestricted remote access.

04 / Continuing responsibility

Know who looks after each part.

The institution manages research storage, backup and its data governance. UnifiedFlow maintains platform components and services within the agreed operating scope. Technical review establishes the arrangements before routine use.

Research files, platform records and supported services need explicit owners.

Establish during technical review
Institution
Research storage, backup, governance and institutional approvals.
UnifiedFlow
Platform software, components, services and scoped technical support.
Shared review
Service locations, access, retention, recovery responsibilities and escalation routes.
Responsibilities follow the work. Storage and backup remain institutional responsibilities; platform maintenance and scoped support sit with UnifiedFlow. The deployment review resolves the details.InstitutionStorage + backupPersistent research filesPlatform servicesSoftware + orchestrationConfiguration + supportUnifiedFlow: platform servicesAgreed before operationLocations · controls · responsibilities
Storage and backup remain institutional responsibilities; platform maintenance and scoped support sit with UnifiedFlow. The deployment review resolves the details.

Processing, access and service locations are agreed for each deployment.

Confirm the supported research data scope

Current supported data scope

A clear starting
boundary.

Our current focus is non-human neuroscience research. Data scope is confirmed before implementation.

In current scope

  • Preclinical animal research data
  • Cell-line and in-vitro research data
  • Other non-human research data appropriate to the agreed workflow

UnifiedFlow is not currently intended for identifiable human-subject data or regulated clinical data.

Authentication & confidentiality

Access follows
the approved purpose.

Technical access supports the environment. It does not grant unrelated rights to use research materials.

Authentication

UnifiedFlow accounts may be used where institutionally permitted. Institutional identity requirements are evaluated during onboarding where required, with the supported arrangement established before operational use.

Confidentiality

Non-public research is confidential by default. Private customer data are not reused for unrelated development without permission. Public scientific data may be used according to their license and citation terms.

Institutional technical review

Make the operating
scope concrete.

We coordinate with the lab and authorized institutional IT and security reviewers to establish the requirements, approved controls and responsibilities for the proposed deployment.

Environment & data paths

Approved machines and storage, compute and service locations, connectivity, and which data or metadata cross each boundary.

Continuity & ownership

Research retention and backup, platform records, recovery arrangements and the people responsible for each layer.

Access & continuing support

Authorized technical access, authentication arrangements, maintenance coordination and routes for escalating a blocked workflow.

Compare on-premises and hybrid processing From technical review to supported use

Review materials

The right detail,
shared directly.

Detailed technical and security documentation is provided directly to authorized institutional IT and security reviewers.

UnifiedFlow’s software, models, analysis capabilities, configuration, infrastructure and platform intellectual property are distinct from the lab’s research materials.

This public overview describes the intended operating model. The deployment-specific review establishes what will be implemented and approved, including the platform components, services and technical support within the agreed scope.

A conversation, grounded in your work

Evaluating UnifiedFlow for your institution?

Request the technical and security materials your authorized reviewers need to assess a proposed deployment.

Request technical review materials