Getting started

Installation on Windows.

Oreumics is a Windows desktop app with a bundled Python analysis engine. Installing it takes a few minutes; the one thing to know in advance is that it signs you in at every launch.

System requirements

Operating system	Windows 10 or 11, 64-bit. macOS and Linux are not supported.
Memory	8 GB RAM minimum, 16 GB recommended. How far a given dataset goes depends on how it is stored and which steps you run — the app estimates that per node before it starts, see Memory & large data.
Disk	Room for the app and its Python analysis engine, plus a disk cache the app uses for checkpoints while a workflow runs. The cache is reclaimed automatically and its quota is a cleanup target, not a hard wall.
Network	Required at every launch: sign-in is verified with the server and the app will not start offline. After that, the network is used only for optional AI Copilot calls, one-time Resource Center installs, and update checks.
Account	A free account plus an admin-issued Beta Access ticket (7, 14 or 30 days) during the beta.

Installing

01
Create an account and request Beta Access
Sign up, verify your email, then request a ticket from the contact form. Redeem the code you receive on your dashboard; the app checks that ticket when you sign in.
02
Download the installer
On your dashboard, click Download Oreumics. It is a Windows installer (.exe) for the latest stable build.
03
Get past SmartScreen
The installer is not yet code-signed, so Windows Defender SmartScreen may warn. Click More info → Run anyway.
04
Approve the administrator prompt
Windows asks for administrator approval (the UAC prompt) because the app installs for all users of the PC. Click Yes. On a managed machine where you cannot approve UAC prompts, ask your IT administrator to run the installer.
05
Follow the setup wizard
Choose an installation directory and press Install. The installer creates a desktop shortcut and a Start Menu entry named Oreumics.
06
Launch and sign in
A sign-in window opens first. After you sign in, Oreumics checks for a newer version, then starts its analysis engine behind a splash screen — the first start takes longer than later ones because the Python runtime is unpacked and warmed up.

Sign-in at every launch

There is no offline mode

Every launch opens the sign-in window and verifies your access with the server before the app starts. If a previous session is still valid the window passes straight through without asking you to type anything — but it always appears, and it always checks. If the machine is offline, Oreumics reports Could not connect to the login server and closes.

One account is bound to one active device. Signing in on a second computer ends the first session; that app shows a warning and closes after a short grace period so you can save. Use Sign out in the sign-in window to switch accounts.

Updates

After sign-in, the app asks the release server whether a newer version exists. If one does, an update window offers Update now — the download runs with a progress bar and the new version installs itself — or Later, which starts the app you have. If the check does not answer within a few seconds, the app starts normally. Updates never touch your projects or saved .bioflow files.

Troubleshooting

“Could not connect to the login server”: The machine cannot reach the sign-in server. Check the connection or a proxy, then relaunch — the app cannot start until sign-in is verified.
“Backend failed to start”: Close and reopen the app. If it persists, make sure nothing else is using local port 8000, or restart the PC.
Startup takes minutes: Antivirus software scanning the bundled Python runtime is the usual cause. Add the Oreumics installation folder to its exclusions.
SmartScreen blocks the installer: Click “More info” then “Run anyway”. The warning appears because the installer is not yet digitally signed.
The installer asks for administrator permission: Expected: the installer is per-machine and installs for all users, so Windows shows its UAC prompt. Approve it; on a managed PC ask your IT administrator to run the installer.
The app closed by itself with a session warning: The same account signed in on another device. Sign in again on the machine you want to keep using.

Logs & reporting a problem

The app writes two log files to %APPDATA%\BioFlow Copilot\logs: backend.log (the Python analysis engine — node errors and tracebacks land here) and main.log (the app shell: sign-in, updates, backend start). The folder is still named after the app’s former name on purpose — it is a compatibility identifier. The quickest way there is Help → Open Log Folder in the app menu, or the Open log folder button in the app’s Log panel.

To report a problem, use the contact form with the inquiry type Report a problem and paste the relevant tail of backend.log — it holds the traceback we need. Check first that it contains no file paths you consider sensitive: the log records the paths of the files you loaded. During the beta we reply within 2 business days.