PolyStore

Framework-agnostic storage primitives for scientific applications.

PolyStore owns backend interfaces, execution-local backend registries, FileManager routing, storage formats, ROI values, virtual-workspace source references, and viewer-streaming payload mechanics. Applications retain ownership of domain artifact names and materialization policy.

Quick start

Pass an explicit mapping of backend names to instances. FileManager has no global fallback and does not infer a backend from a path.

from pathlib import Path
import numpy as np

from polystore import DiskBackend, FileManager, MemoryBackend

registry = {
    "disk": DiskBackend(),
    "memory": MemoryBackend(),
}
files = FileManager(registry)

data = np.arange(6).reshape(2, 3)
files.save(data, Path("output.npy"), backend="disk")
loaded = files.load(Path("output.npy"), backend="disk")

For application startup where every discoverable context-free backend is wanted, use the package-owned lazy registry:

from polystore import FileManager, ensure_storage_registry, storage_registry

ensure_storage_registry()
files = FileManager(dict(storage_registry))

Backends requiring context-specific construction, including virtual workspaces and OMERO, must be instantiated by the application and added to its registry.

Nominal backend extension

Concrete backends inherit DataSource, DataSink, StorageBackend, or ReadOnlyBackend and declare their backend key. The authoritative class catalog is BackendBase.__registry__ (also exported as STORAGE_BACKENDS). Do not build a second backend class table.

Installation

python -m pip install polystore

The core install includes NumPy, ArrayBridge, metaclass-registry, file locking, platform-aware cache paths, image I/O, Zarr/OME-Zarr support, and ZMQRuntime. Framework and streaming extras add their corresponding optional runtimes. Install polystore[bioformats] for the package-owned PyImageJ and Bio-Formats bridge. Its first use materializes a checksummed Fiji, JDK, and PyImageJ bridge runtime; later processes reuse that complete local cache without Maven resolution.

Full documentation: polystore.readthedocs.io

Release files for polystore 0.2.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for polystore 0.2.5
File	Size	Uploaded
polystore-0.2.5.tar.gz	164.0 kB	Aug 25, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for polystore 0.2.5
File	Interpreter	ABI	Platform	Reset
polystore-0.2.5-py3-none-any.whl 141.2 kB Aug 25, 2026	Python 3	none	any	Details

Total release size: 305.2 kB

Release files / polystore-0.2.5.tar.gz

Download URL	polystore-0.2.5.tar.gz
Size	164.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`af2907639ce8008009fec4c211ee32f41626e8be1b028ab921145c5fe67a643a`
BLAKE2b-256 checksum How to use checksums	`7c58cb8f3c8237b7bbdd24424994f2be4dc5ae909210f2f6cff2a4ce84434ba4`
Upload date	Aug 25, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/OpenHCSDev/PolyStore
Publishing commit: github.com/OpenHCSDev/PolyStore/tree/b98937f082c5d9b863ac34ad958b5b02dd0a3f31

Workflow

Publishing configuration: github.com/OpenHCSDev/PolyStore/blob/b98937f082c5d9b863ac34ad958b5b02dd0a3f31/.github/workflows/publish.yml
Publishing logs: github.com/OpenHCSDev/PolyStore/actions/runs/32867703984/attempts/1

Artifact

Subject: polystore-0.2.5.tar.gz
SHA-256 checksum: af2907639ce8008009fec4c211ee32f41626e8be1b028ab921145c5fe67a643a Verifying attestations

Release files / polystore-0.2.5-py3-none-any.whl

Download URL	polystore-0.2.5-py3-none-any.whl
Size	141.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`ccfe2710373b3296c919fdf019fdb207c4d44083a079e1bb84ec973eb5c4c605`
BLAKE2b-256 checksum How to use checksums	`ef574a1b13d433ae100a6c454cd22b2331b3d723fa541068b77e7e6a056c557a`
Upload date	Aug 25, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/OpenHCSDev/PolyStore
Publishing commit: github.com/OpenHCSDev/PolyStore/tree/b98937f082c5d9b863ac34ad958b5b02dd0a3f31

Workflow

Publishing configuration: github.com/OpenHCSDev/PolyStore/blob/b98937f082c5d9b863ac34ad958b5b02dd0a3f31/.github/workflows/publish.yml
Publishing logs: github.com/OpenHCSDev/PolyStore/actions/runs/32867703984/attempts/1

Artifact

Subject: polystore-0.2.5-py3-none-any.whl
SHA-256 checksum: ccfe2710373b3296c919fdf019fdb207c4d44083a079e1bb84ec973eb5c4c605 Verifying attestations