Syphera is a web-based portal for sharing research and operational data between Roche teams and external partners under a named-user, project-based model. You sign in with your work identity, work inside one or more approved projects, and use the same controls whether you browse files in the browser, upload new material, transfer instrument-scale datasets (DataSync, IBM Aspera / Storage Scale, or FSxN SnapMirror where enabled), or use SFTP and scripted downloads where offered.

Data residency: when you create a project you choose a data region — currently United States (Oregon, us-west-2) or Europe (Frankfurt, eu-central-1). Project files, quarantine scanning, SFTP, and file storage stay in that region (downloads use time-limited S3 links). Sign-in and the web API remain on the shared hub.

• Sign in opens your personal workspace. If you have no project yet, you will see guidance to request access or wait for an administrator.
• Dashboard summarizes activity and entry points (for example, opening the data area or requesting access to another project, depending on your role).
• Data is where you choose an approved project (optionally filter by data region first — US or EU), then download or upload within that project's rules. Large files may require approaches other than a simple browser download (such as a generated script or SFTP), as indicated in the product. Project files, quarantine scanning, and SFTP stay in the region chosen when the project was created. You can share an authenticated deep link to a file (for example /files/eu-test/Roche/report.pdf): recipients must sign in; then Syphera opens that project and file. Browser download starts automatically when the file is 50GB or smaller; larger files stay selected for Bash/CLI or SFTP.
• Profile holds your account details and preferences your organization requires for compliance and contact.
• Some users see an administration area for approvals, user lists, or operational views. That appears only when your account has been granted those responsibilities.

• Browse and search datasets and files you are entitled to within a selected project.
• Download data using paths appropriate to file size and policy (browser, scripted, or bulk).
• Upload new files or folders where your project allows it (folder structure is kept under Roche/Partner after scanning), including checks that files meet format and safety rules.
• Choose data ingestion methods suited to interactive work or TB-scale instrument pipelines (see below).
• Request access to additional existing projects when your program expands.
• Submit a request to stand up a new collaboration project when your workflow requires it (subject to approval).

Every project always supports interactive uploads. When a program needs high-volume instrument or site-to-cloud transfer, administrators can enable additional methods at project create or later under Data ingestion — next steps. Instrument paths land in the project's main storage (not the interactive quarantine scan path).

• Browser upload — drag-and-drop or file picker in the Data area. Files go to quarantine, are scanned for malware and format rules, then promoted under Roche/Partner. Best for interactive collaboration and moderate sizes.
• SFTP — AWS Transfer Family endpoint shared with the project. Same quarantine → scan → promote path as the browser. Useful for scripted or recurring partner drops without a web session.
• AWS DataSync — agent near an on-prem NFS/SMB share (for example a sequencer landing zone) syncs into the project main bucket. IT configures the agent and task; Project Admin completes Configure DataSync in Syphera. Intended for high-volume instrument ingest (no interactive malware scan on this path).
• IBM Aspera / Storage Scale — one shared set of S3 credentials for IBM Aspera (HSTS/ATS) and/or IBM Storage Scale (AFM/CES) to write into the same project bucket prefix. Syphera issues a copy-ready IT handoff (bucket URI, keys, policy). On-prem licenses and gateways stay outside AWS.
• FSx for NetApp ONTAP (SnapMirror) — Syphera provisions an FSxN filesystem; IT peers SnapMirror from on-prem ONTAP. Users can browse/download via the FSxN storage root in the UI once ready; Mount and IT handoff cards guide admins through capacity and peering.

Which combination you need depends on volume, site tooling, and IT readiness. Use the cost estimator to model storage plus optional DataSync, IBM, or FSxN usage before onboarding.

Access is not automatic: your email domain, company, and the project you name are used to route you through the right approval path. In general:

1. You submit a request (new account, new project, or join an existing project) with the information the form asks for.
2. Administrators (IT support and/or project administrators, depending on the type of request) review it against program rules.
3. When approved, your account is attached to the correct project so the Data area and downloads only show that program's content.
4. If something is missing or inconsistent, you may be asked to correct your request or your sponsor may need to confirm your participation.

Exact approval chains depend on your organization; the portal surfaces status in the registration and sign-in flows rather than exposing internal ticketing details.

The registration form is split into logical steps. Fields below are described in plain language; required items are marked in the live form.

Account (email and password)

Work email and a strong password. Your email is often used as the username and must match your sponsor's expectations (for example Roche employees may need a Roche or Genentech address).

I am a / I want to register as

Whether you are a Roche employee or an external partner, and whether you are joining an existing project or requesting a new project for a collaboration.

Project name

The official program or study identifier you were given. For existing projects it must match exactly (including spelling and case) so the system can validate you against the right cohort.

New project details

When requesting a new project, you provide a short description, partner organization, and internal billing references such as cost center (and optionally WBS) so the program can be set up and funded correctly. You also set an expected duration and allowed file types (or "all formats" where policy allows).

Supporting documents

Optional attachments (for example a one-pager or approval email) that help administrators confirm the request faster.

Profile (name, company, contact)

Identity and contact fields used for audit, notifications, and compliance. Some items are fixed after approval; others can be updated in Profile depending on policy.

• Project boundary: permissions are tied to discrete projects. Being approved for Project A does not grant visibility into Project B.
• Authentication: you sign in with centrally managed credentials; sessions are bounded so unattended browsers do not stay open indefinitely.
• Transport and storage: data moves over encrypted channels; stored objects stay in segregated namespaces per project so routine operations do not mix customer or study content across programs.
• Upload safety: incoming files can be scanned and validated before they are treated as part of the canonical dataset, reducing the risk of malware or disallowed formats entering the space.
• Auditability: downloads and administrative actions are logged at a level appropriate for regulated collaboration (who accessed what, when, and in which project context)—without publishing internal architecture in this public summary.