Installing Nucleora
Nucleora runs entirely on your own machine. Nothing you design is uploaded, and no account is needed to compute anything. Two of the scientific libraries it can use are published under licences that don't allow us to redistribute them, so you install those yourself — free, one time, from the people who wrote them. Everything else works out of the box.
What works without any extra install
The large majority of Nucleora needs nothing beyond the app itself:
- The full parametric CAD document — feature tree, dependency recompute, undo/redo, timeline scrubbing
- All 433 tools in the palette
- Codon optimization and the 33 RefSeq-derived codon usage tables
- Primer design and melting temperatures (our own SantaLucia 1998 nearest-neighbour implementation)
- Cloning, assembly, restriction analysis, plasmid maps and sequence views
- The complete build output, with a citation behind every number
- Export to GenBank, FASTA, GFF3 and SBOL
Two features need an optional library: RNA secondary-structure folding (ViennaRNA) and an alternative primer engine (primer3). If either is missing, Nucleora says so plainly on the panel that would have used it, rather than quietly returning a different number.
macOS
- Get Nucleora. Download the folder and put it wherever you keep your work — Desktop is fine. There is nothing to install and no admin password needed.
- Start it. Double-click
Start Nucleora.command. A Terminal window opens — that's the app's own server, so leave it open while you work. Your browser opens automatically athttp://127.0.0.1:8770.The first launch takes a minute or two while it sets up its own private Python environment. Later launches are quick.If macOS says the file is from an unidentified developer: right-click it, choose Open, then Open again. You only do this once. - Stop it by pressing
Control+Cin that Terminal window, or just close it.
Optional: RNA folding (ViennaRNA) on macOS
Pick whichever you find easier. Both are free.
# Option A — Homebrew (if you already use it)
brew install viennarna
# Option B — pip, into Nucleora's own environment
cd ~/Desktop/genelab
.venv/bin/python3 -m pip install ViennaRNAOr download the official macOS installer from the Vienna group directly: tbi.univie.ac.at/RNA.
Optional: the primer3 engine on macOS
cd ~/Desktop/genelab
.venv/bin/python3 -m pip install primer3-pyYou probably don't need this one. Nucleora's built-in primer thermodynamics are the default and are used whether or not primer3 is present — we made that switch because the same primer was returning different melting temperatures on different computers depending on whether primer3 happened to be installed. primer3 remains available as a labelled second opinion.
Windows
- Install Python 3.11 or newer from python.org. On the first screen of the installer, tick “Add python.exe to PATH” before clicking Install — this is the one step people miss, and skipping it causes most Windows setup problems.
- Get Nucleora and unzip it somewhere like
C:\Users\you\Documents\Nucleora. - Open PowerShell in that folder — Shift+right-click inside the folder, then Open PowerShell window here.
- Set it up (first time only):
python -m venv .venv .\.venv\Scripts\python.exe -m pip install -r requirements.txt - Start it (every time):
Then open
.\.venv\Scripts\python.exe server.pyhttp://127.0.0.1:8770in your browser. Stop it withCtrl+C.To avoid typing that each time, save it as a.batfile in the same folder and double-click that instead.
Optional: RNA folding (ViennaRNA) on Windows
.\.venv\Scripts\python.exe -m pip install ViennaRNAIf that fails to build, use the official Windows installer from tbi.univie.ac.at/RNA, or run Nucleora under WSL2 and follow the Linux route.
Optional: the primer3 engine on Windows
.\.venv\Scripts\python.exe -m pip install primer3-pyLinux
python3 -m venv .venv
.venv/bin/python3 -m pip install -r requirements.txt
.venv/bin/python3 server.py # then open http://127.0.0.1:8770
# optional extras
.venv/bin/python3 -m pip install ViennaRNA primer3-pyDebian and Ubuntu also package it: sudo apt install vienna-rna.
Why aren't these just included?
Because their authors' licences don't permit us to redistribute them, and we'd rather respect that than quietly bundle them.
- ViennaRNA (Institute for Theoretical Chemistry, University of Vienna) is free to use, but its licence does not permit redistribution for a fee. Installing it yourself means you receive it directly from its authors, under their terms. It is excellent software and has been maintained for three decades — if you publish work that used the folding features, cite it.
- primer3-py is GPL-2.0, a licence that would impose its own terms on everything shipped alongside it. Keeping it as an optional install keeps both licences intact. Nucleora's own primer thermodynamics are the default anyway.
The same reasoning applies to a couple of optional graphics libraries used for SVG export. Nucleora detects each one at startup and tells you what is and isn't available, instead of failing later or silently changing an answer.
Checking what's active
Open Nucleora and look at the toolbar. It shows the live status of each optional library — for example
Vienna [OK] when folding is available, or a note that it's absent. Any panel that needs a missing
library says which one, rather than returning a number computed a different way.
If something goes wrong
| What you see | What to do |
|---|---|
python: command not found (Windows) | Python was installed without “Add to PATH”. Re-run the installer and tick that box. |
| “Unidentified developer” (macOS) | Right-click Start Nucleora.command →
Open → Open. Once only. |
| Port 8770 already in use | Nucleora is probably already running — check your browser tabs. To use a
different port, set NUCLEORA_PORT before starting. |
| Browser doesn't open by itself | Go to http://127.0.0.1:8770 manually. |
| Folding features greyed out | ViennaRNA isn't installed — see the optional step for your platform above. |
| You moved the Nucleora folder and it won't start | Start it again; it detects the move and repairs its environment automatically. |
Still stuck? Tell us what you saw — include the text from the Terminal or PowerShell window, which usually identifies the problem immediately.