nodus-compute
The Python SDK for Nodus: run functions, sandboxes, jobs and workspaces on the cheapest capacity that finishes them on time, with checkpoints, recovery and exact prepaid billing.
pip install nodus-compute
nodus login
import nodus
app = nodus.App("hello")
@app.function(gpu="H100", timeout="1h", max_cost=5)
def square(x: int) -> int:
return x * x
@app.local_entrypoint()
def main():
print(square.remote(7)) # one call; blocks and returns 49
print(list(square.map(range(10)))) # fan out; results stream back in order
nodus run app.py # ephemeral: the App is deleted when main() returns
nodus deploy app.py # persistent: call it later with nodus.Function.from_name("hello", "square")
Every blocking call also has an .aio form for asyncio code: await square.remote.aio(7).
For organizations enabled for the Spot pilot, nodus.Client().spot.request("h200x8", max_price=12) waits for a
dedicated interruptible node and returns its Nodus SSH command. Use client.spot.release(node["id"]) when finished.
The Spot guide covers stable request keys, polling and billing.
- Guides: https://nodus-compute.ai/docs/guides/python/
- Coming from Modal: https://nodus-compute.ai/docs/getting-started/modal-users/
- Examples:
examples/python/
Layout
| Path | What |
|---|---|
src/nodus/api/ |
Layer 1: the generic resource client (nodus.api.get, list, watch, apply, …) |
src/nodus/api/models/ |
Generated pydantic models (make gen; never edit) |
src/nodus/errors/ |
One exception per error-registry code, plus the SDK's outcome errors |
src/nodus/*.py |
Layer 2: App, Function, Image, Volume, Secret, Sandbox, Job, Workspace, llm |
src/nodus/runtime.py, log.py, checkpoint.py, cluster.py |
In-container helpers; no-ops outside Nodus |
src/nodus/_runtime/ |
The in-container worker runtimes (Functions, durable steps, agents) |
Development
make -C sdk/python lint # ruff lint and format check, mypy strict on nodus.api
make -C sdk/python gen # regenerate nodus.api.models from api/openapi
make -C sdk/python docs # griffe dump for the reference pages
The SDK has no tests of its own: the compose journeys exercise it end to end. The per-platform wheels that embed the
CLI are built with NODUS_CLI_BIN=<binary> NODUS_WHEEL_PLATFORM=<tag> make -C sdk/python wheel-cli.
1 maintainer
Metadata
1 maintainer
Release files for nodus-compute 1.0.48
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| nodus_compute-1.0.48-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details for nodus_compute-1.0.48-py3-none-win_arm64.whl |
| nodus_compute-1.0.48-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for nodus_compute-1.0.48-py3-none-win_amd64.whl |
| nodus_compute-1.0.48-py3-none-manylinux_2_17_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for nodus_compute-1.0.48-py3-none-manylinux_2_17_x86_64.whl |
| nodus_compute-1.0.48-py3-none-manylinux_2_17_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details for nodus_compute-1.0.48-py3-none-manylinux_2_17_aarch64.whl |
| nodus_compute-1.0.48-py3-none-macosx_12_0_x86_64.whl | Python 3 | none | macOS 12.0+ x86-64 | Details for nodus_compute-1.0.48-py3-none-macosx_12_0_x86_64.whl |
| nodus_compute-1.0.48-py3-none-macosx_12_0_arm64.whl | Python 3 | none | macOS 12.0+ ARM64 | Details for nodus_compute-1.0.48-py3-none-macosx_12_0_arm64.whl |
Total release size: 150.4 MB
Release files / nodus_compute-1.0.48-py3-none-win_arm64.whl
| Download URL | nodus_compute-1.0.48-py3-none-win_arm64.whl |
|---|---|
| Size | 23.3 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
1e2d027ba64ff6b6c9a2d392cedce71761e633aac93dadf2d5f91f9347067d36
|
|
BLAKE2b-256 checksum How to use checksums |
9431fc9018871f086e082f3004ffee5baf43d283b05eac8a74242edff0aab0cd
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logRelease files / nodus_compute-1.0.48-py3-none-win_amd64.whl
| Download URL | nodus_compute-1.0.48-py3-none-win_amd64.whl |
|---|---|
| Size | 26.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
550ae3bf6e05e9e708091e06e27b6ae23a0e072d93faef727936d31390bcac13
|
|
BLAKE2b-256 checksum How to use checksums |
85b15e82aafc3f54e72d07f20668a97ce5720236b61d8cc0cffb9edd6753f5a5
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logRelease files / nodus_compute-1.0.48-py3-none-manylinux_2_17_x86_64.whl
| Download URL | nodus_compute-1.0.48-py3-none-manylinux_2_17_x86_64.whl |
|---|---|
| Size | 26.2 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
11db89e1214abf83e381fa12a0a177c56b732cb240c3f8c86fffd9db1a48fca6
|
|
BLAKE2b-256 checksum How to use checksums |
86383baca294b50f52d30533ed5ddfcaa1f128aea2b3a029e66c6cdc8e478078
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logRelease files / nodus_compute-1.0.48-py3-none-manylinux_2_17_aarch64.whl
| Download URL | nodus_compute-1.0.48-py3-none-manylinux_2_17_aarch64.whl |
|---|---|
| Size | 23.2 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
b1aa2fea03fa7d81ed4a72ca566953964e5d57c92e8be0b265492dc34f93a060
|
|
BLAKE2b-256 checksum How to use checksums |
864d1b1e1e571cbe0a3b793e7a7e91c3e93ac842e385a78c4280cabf9cfc7cd0
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logRelease files / nodus_compute-1.0.48-py3-none-macosx_12_0_x86_64.whl
| Download URL | nodus_compute-1.0.48-py3-none-macosx_12_0_x86_64.whl |
|---|---|
| Size | 26.7 MB |
| Tags | Python 3 macOS 12.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
caf6afebe5afcdbcfeb7259a939789331dc67ddf29bc160043b79a1bae3c765c
|
|
BLAKE2b-256 checksum How to use checksums |
f65a94094bcc24c31067f17a37963144215ecb6a03abba1336b0c2f12d3b285d
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logRelease files / nodus_compute-1.0.48-py3-none-macosx_12_0_arm64.whl
| Download URL | nodus_compute-1.0.48-py3-none-macosx_12_0_arm64.whl |
|---|---|
| Size | 24.4 MB |
| Tags | Python 3 macOS 12.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
22299d2f677a96aaa545dd9882cb4cbf8f615db6d9fa8e07ef7a9db8eb09c5f8
|
|
BLAKE2b-256 checksum How to use checksums |
377c887914bfab6f64d4486a662dfd941090edd9268e184cbb686804e9395273
|
| Upload date | |
|
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.
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 Nov 2, 2026.
Transparency logSecurity for nodus-compute 1.0.48
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
All 6 files in this release have been uploaded with provenance metadata.
Attestation for nodus_compute-1.0.48-py3-none-win_arm64.whl
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 Nov 2, 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.
