Plexora
Plexora is a viewer for multiplexed imaging and spatial transcriptomics. It opens large images where they are, without converting or copying them, draws segmentation masks and cell tables over them, and runs on a laptop, in a notebook, on a remote workstation or on an HPC cluster.
Documentation: https://nirmallab.github.io/plexora/
Install
pip install plexora
plexora
plexora starts the viewer and opens it in your browser. Python 3.12, 3.13 or
3.14 is required. A desktop app for macOS, Windows and Linux is on the
releases page. See
Installation.
Quick start
In the app, choose File → Import Sample… and pick an image, a folder of files, or a Xenium or Visium run. From Python:
import plexora
name = plexora.import_sample("slide.ome.tif", "slide_mask.tif", "cells.csv", wait=True)
plexora.view(name) # in a notebook, shows the viewer inline
More in Your first image.
What it reads
- Multiplexed images: OME-TIFF, TIFF, QPTIFF, OME-Zarr (local,
https://ors3://) - Brightfield whole-slide images: SVS, NDPI, SCN, BIF, MRXS, DICOM
- 10x Genomics Xenium, Visium and Visium HD output folders
- SpatialData stores and AnnData tables; CSV, TSV and Parquet cell tables
- Segmentation masks (label images) and cell boundary polygons
The full list is in Supported formats.
Where to go next
| I want to | Read |
|---|---|
| Use the viewer and its tools | Image viewer, Plugins |
| Script it from Python or a notebook | Python, Notebook |
| Look at data on a remote machine or cluster | Remote and HPC |
| Write a plugin | Build a custom plugin |
| Look up a function or command | Python API, Command line |
Developing Plexora
git clone https://github.com/nirmallab/plexora.git
cd plexora
pip install -e ".[dev]"
python -m pytest -q -p no:randomly
For the documentation site in website/, see CONTRIBUTING_DOCS.md.
Engineering notes live in docs/internal/.
Usage data
Plexora can send anonymous usage counts -- which features and plugins are
used, how long tiles take to draw, which kinds of errors occur -- so we know
what to improve. It never sends file, project, marker or gene names, cell
data, coordinates, usernames, machine names, paths, prompts or anything typed
into a tool; every field it may send is on an allowlist
(plexora/telemetry/schema.py). Everything is queued on this machine first,
nothing in Plexora waits for it, and it works air-gapped exactly as before.
It is on by default and a notice says so the first time. Any one of these turns it off:
plexora telemetry off # or: Settings > Usage data
export DO_NOT_TRACK=1 # honoured everywhere
export PLEXORA_TELEMETRY=off
plexora telemetry preview prints exactly what the next upload would contain,
and plexora telemetry status says which of the above is in force.
docs/TELEMETRY.md has the details.
Free and Pro
Free is everything described above: every image, table and modality, every tool's manual features, remote, HPC and notebook viewing, and export. It needs no account, no activation and no network, it never asks, and anyone may use it for any purpose, commercial work included.
Pro adds Plexora AI (guided gating and QC sessions an agent runs with you, the evidence and analysis tools it uses, and the chat), Plexora 3D (analysing z-stacks and time series beyond viewing them), spatial transcriptomics (Xenium, Visium and Visium HD) and Video Studio (videos made from the viewer). A 30-day trial is everything in Pro. External MCP access, for an outside coding agent, is off by default and not part of Pro; an administrator can turn it on for a licence. Pro is a yearly subscription per seat, at an academic or a commercial price, and both are bought online from the pricing page: one seat is an individual account, two or more make a team. Licences, devices and AI credits are managed on the BioCognia platform, which Plexora shares with SCIMAP Pro: you sign in at account.biocognia.com, never in Plexora. In Settings > Account, Connect this device shows a short code and opens the page to approve it; or, from a terminal:
plexora license status
plexora license activate # this computer: prints a code to approve in the browser
plexora license activate BIOC-XXXX-XXXX-XXXX-XXXX # with your licence key from the portal, no browser needed
plexora license activate --cluster --name O2 # a whole HPC cluster, once, from a login node
plexora license install lab.bioc # an offline licence file
plexora license trial # 30 days of Pro
A licence check sends the licence certificate and a hash that identifies the device. It never sends your data, file names, machine names or anything about what you are looking at. When a licence ends, everything Free keeps working, and every gate, ROI, figure and export you made, with or without AI, stays yours and editable. AI model providers your agent uses bill you separately. docs/LICENSING.md has the details.
License
Plexora is licensed by BioCognia under the Plexora End User Licence Agreement
1.0 (LicenseRef-Plexora-EULA-1.0, see LICENSE). It is not an
open source license. In short:
| Plexora Free, for any purpose: research, teaching, personal or commercial | ✅ Free, no account or licence key |
| Plexora Pro for academic research and teaching | Per seat, per year, at the academic price |
| Plexora Pro for commercial use | Per seat, per year, at the commercial price |
| Redistributing Plexora unmodified, with the licence attached | ✅ Allowed |
| Patching your own copy to fix a bug or a compatibility problem | ✅ Allowed |
| Publishing a fork, a patched build, or a renamed version | ❌ Not allowed |
Prices, and Buy for either use class, are on the pricing page; a subscription renews at the price it was bought at.
Plugins are a deliberate exception. Anything you build against the documented
extension interfaces — the plexora.plugins entry point group and the plexora.api
package — is yours. You may distribute and sell your plugin under whatever license
you like, and you do not need our permission. Extending Plexora through the plugin
API is the supported way to change what it does; editing its source is not.
For licensing questions, contact support@biocognia.com.
Some bundled components carry their own licenses, which are unaffected by the above — see section 13 of LICENSE.
Metadata
Release files for plexora 0.0.35
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plexora-0.0.35.tar.gz | 14.2 MB | Without provenance | Details for plexora-0.0.35.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plexora-0.0.35-py3-none-any.whl | Python 3 | none | any | Details for plexora-0.0.35-py3-none-any.whl |
Total release size: 27.5 MB
Release files / plexora-0.0.35.tar.gz
| Download URL | plexora-0.0.35.tar.gz |
|---|---|
| Size | 14.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c2decdc2b7889775d41fd63e3e5bee9fed5957880c51433f007f7a72065d743
|
|
BLAKE2b-256 checksum How to use checksums |
de8476db00c9b92155638288d9c58fe952a45640744460facb9462cc55ab95e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.14
|
Release files / plexora-0.0.35-py3-none-any.whl
| Download URL | plexora-0.0.35-py3-none-any.whl |
|---|---|
| Size | 13.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cacc35e849346eed029b4dc51b372a3ebe47f12aea2eb04188c9d11f25a27996
|
|
BLAKE2b-256 checksum How to use checksums |
4157c6e58833d30440a9cc372523ebee05b790f1c266a587b4468b8a925ea017
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.14
|
Security for plexora 0.0.35
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.