ivoryos-edge
The IvoryOS edge: it runs next to your instruments, reads the Python classes that drive them, and serves a web page to design, run and optimize experiments with them. Every method becomes a step you can drag into a workflow, and every argument a field of the right type. Runs, results and workflows are kept on that computer.
Most people use it through the IvoryOS desktop app, which installs this package itself. Install it on its own to run a deck from your own Python environment, such as one your editor uses.
Install
pip install ivoryos-edge
Python 3.10 or newer. The web interface is inside the package; nothing else is needed.
Run your instruments
End a script that creates your instrument objects with ivoryos_edge.run(__name__):
import ivoryos_edge
from my_lab import SyringePump
pump = SyringePump(port="COM3") # each object becomes an instrument
ivoryos_edge.run(__name__) # http://localhost:8080
Then open http://localhost:8080 in a browser on that computer. A deck can also be a JSON file,
run with ivoryos-edge --deck deck.json.
Links
- Documentation
- Automation Hub: drivers, platforms and workflow templates
- Source and issues
Metadata
Release files for ivoryos-edge 0.1.1
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 |
|---|---|---|---|---|
| ivoryos_edge-0.1.1.tar.gz | 1.5 MB | With provenance | Details for ivoryos_edge-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ivoryos_edge-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for ivoryos_edge-0.1.1-py3-none-any.whl |
Total release size: 3.1 MB
Release files / ivoryos_edge-0.1.1.tar.gz
| Download URL | ivoryos_edge-0.1.1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef05b99b25635973c8895c75ed6f1ad42134d2e0b0fd5d67947b41efb95730cf
|
|
BLAKE2b-256 checksum How to use checksums |
5a129ef5385cccd60ea597175d16ca634de05af3910101d3dc374e9591d20a6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / ivoryos_edge-0.1.1-py3-none-any.whl
| Download URL | ivoryos_edge-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56a95b5985e283e1277e577f0eadd6e604e4ef96e0d6ec0f309a36f1817ff837
|
|
BLAKE2b-256 checksum How to use checksums |
dac23f8563b0b5a4e14654aac04c97355ce08ee064c3af0704587560c70b628e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for ivoryos-edge 0.1.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ivoryos_edge-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA 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.