This release is a pre-release and may not be stable for production use.
Python
The orbite package is a thin PEP 8 binding to OrbiTE's Rust owners. It is
independent of Mooncake's Python API; there is no tent or mooncake.engine
alias. Rust remains the primary interface.
Install and configure
Wheels target CPython 3.10–3.14 on Linux x86_64 and aarch64. The maintainer
publishes releases; CI builds installable review artifacts. Python beta.1 is
0.1.0b1. The published profile includes RDMA, CUDA, io_uring, GDS and
metrics (plus the hidden adaptive reference core). Wheels bundle the verbs
runtime and its libnl dependencies; CUDA and cuFile are runtime-loaded.
CPU-only hosts can run the installed quickstart.
CPU + io_uring wheels remain separate CI artifacts, not a second PyPI variant.
A source build uses the same combined profile and needs the
Linux build prerequisites; it never qualifies a GPU profile.
This page lists the current API, not a freeze. Breaking changes remain allowed
between betas. The local CUDA copy API, including LocalCopyOptions, CTA caps
and background thresholds, remains Rust-only. Python's EngineConfig can set
rdma.gpu_direct_registration with the RDMA feature present; CUDA exports keep
the native allocation/device checks and retained-exporter contract.
import orbite
config = orbite.EngineConfig.from_json('{"bind_addr":"127.0.0.1:0","tcp":true}')
engine = orbite.TransferEngine(config)
EngineConfig(**settings) and from_json(text) use the
OrbiTE JSON format. from_file(path)
reads a bounded JSON file; from_env() reads only ORBITE_CONF, containing
inline JSON or a file path. TransferEngine() captures that environment
configuration once. Passing a config bypasses the environment. Unknown fields,
wrong types and metadata-server options are errors. The snapshot is immutable.
Registered buffers and remote segments
Consumers publish endpoint() and source_epoch() in their own registry.
Use that authoritative epoch when opening a peer; an endpoint alone does not
identify a source incarnation. No discovery or external metadata service is
part of OrbiTE.
with orbite.TransferEngine(config) as source, orbite.TransferEngine(config) as client:
src, dst = bytearray(b"hello"), bytearray(5)
with source.register_buffer(src) as remote, client.register_buffer(dst) as local:
with client.open_segment(source.endpoint(), source.source_epoch()) as peer:
with client.allocate_batch(1) as batch:
batch.submit(orbite.TransferOp.READ, peer, [
orbite.TransferRequest(local.address, remote.address, 5,
transport=orbite.Transport.TCP)
])
task, = batch.wait(5.0)
assert task.state == orbite.TaskState.COMPLETED
assert task.locally_drained and dst == src
register_buffer(owner) acquires and retains a writable contiguous buffer
export. register_memory(address, length, owner=owner) registers a subrange
of a retained exporter; a bare foreign integer is rejected. Engine-allocated
Memory can also be registered by address. register_memory_ranges(ranges, owners=...) validates the whole bounded list before registration. Close
related aliases together with unregister_memory_ranges(registrations).
CUDA exporters use __cuda_array_interface__ v2/v3 or
__dlpack__ plus __dlpack_device__. The driver validates the whole exported
extent, pointer and device; Python claims alone are insufficient. Read-only,
noncontiguous, out-of-range and wrong-device exports fail. CAI v3's stream and
DLPack's producer handoff establish readiness. The Python owner and consumed
capsule remain retained through drain, aliases and quarantine. A CPU wheel
reports UnavailableError before requesting a CUDA capsule.
registration = engine.register_memory(tensor.data_ptr(), tensor.nbytes, owner=tensor)
Batches, notifications and files
Batch.submit(operation, target, requests, notification=None) enqueues through
the Rust admission, selector and physical-owner paths. Requests carry a local
address, remote address (file offset for a file target), length, transport,
priority, optional policy name, absolute monotonic deadline_ns and intent.
tasks() observes; progress() advances a bounded step; wait(timeout)
waits with the timeout in seconds. cancel(task_index) cancels queued work;
running work still drains. A terminal result and physical quiescence are
separate: inspect locally_drained and failure.remote_effect.
send_notification(peer, Notification(name, message)) and
receive_notifications() use bounded native queues. A None peer delivers
locally. File operations use open_file_segment(path, permission) and the same
batch methods with Transport.IO_URING or Transport.GDS. Providers must be
built and enabled. FileSegment.info() reports the extent; close drains file
I/O. stats() returns a read-only snapshot of engine counters and charges.
Surface and defaults
| Surface | Public names |
|---|---|
| Construction | EngineConfig, TransferEngine |
| Retained owners / context managers | Memory, RegisteredMemory, RemoteSegment, FileSegment, Batch |
| Requests and results | TransferRequest, TaskStatus, TransferFailure, Notification, MemoryOptions |
| Enums | TransferOp, Transport, Permission, Priority, IntentType, TaskState |
| Exceptions | Error and one <RustVariant>Error subclass per native error variant |
Defaults come from Rust's typed configuration. Requests default to UNSPEC,
high priority, unspecified intent and no deadline or named policy.
MemoryOptions defaults to any local location, read/write permission and
automatic transport selection. Only implemented OrbiTE transport identities
are exported; a compiled-out provider raises a typed unavailable error.
All blocking native calls detach the GIL behind a panic barrier. Exceptions
derive from orbite.Error, including ConfigError, PermissionDeniedError,
EpochMismatchError, ResourceExhaustedError, TimeoutError and
UnquiescedError. Python argument/type errors retain normal Python exceptions.
Task failures retain their independent byte prefixes and remote-effect status.
Context exit invokes explicit close and surfaces errors. Dropping an unfinished
batch defers retirement; dropping an allocation cannot free memory used by a
registration or operation. A failed native cleanup retains owners and charges
and is never retried as a destroy. Timeout, cancellation and dropped Python
objects are not release receipts. Explicit unregister can report
ResourceExhaustedError while a native owner still holds the range.
RemoteSegment.close() releases that handle, not the peer identity; Rust's
per-peer retirement API remains available to Rust consumers.
Transport contains UNSPEC, TCP, HP_TCP, SHM, RDMA, NVLINK,
MNNVL, IO_URING and GDS. The removed FABRIC value 5 is unknown;
remaining numeric values are unchanged. A known transport that is not built
still reports UnavailableError when requested.
Packaging and evidence
The Python-only crate uses PyO3 and maturin. A CPython-specific wheel rather than abi3 preserves buffer protocol and CUDA exporter support across the tested interpreters. Its exact core dependency pin keeps hidden owner helpers within one release; other shared dependencies follow the repository's semver policy. There is no independent coordinator in the binding.
The installed-wheel controls check real two-process TCP bytes and guards, file segments, policy/intent/priority/deadline routing, exceptions, notifications, GIL release, queued cancel and exporter retention under timeout and early drop. The combined wheel runs CUDA exporter controls through a CPU driver shim. The sdist is rebuilt, installed and tested separately. See qualification for exact CI evidence. Python GPU remains Implemented; installed profile unqualified; its installed gate is written but unrun.
Metadata
Release files for orbite 0.1.0b1
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 |
|---|---|---|---|---|
| orbite-0.1.0b1.tar.gz | 1.5 MB | With provenance | Details for orbite-0.1.0b1.tar.gz |
Built distributions (wheels)
Total release size: 23.3 MB
Release files / orbite-0.1.0b1.tar.gz
| Download URL | orbite-0.1.0b1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a7c8c518e7ac88b77ff5f1f994d9c157e5a69192cd9c84589127db7af56a209
|
|
BLAKE2b-256 checksum How to use checksums |
06795d616fabb48f615815fb708d9f2e2a8a17c20cdd9cfc53b923046827e457
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | orbite-0.1.0b1-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0acad9c8698ea767b889506514aff985ffb92251fe9687acf5527ee52b6deac8
|
|
BLAKE2b-256 checksum How to use checksums |
3b958e494288e59719e7b0c301311f1a23f424000ba2341dd1c0540caf435732
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp314-cp314-manylinux_2_28_aarch64.whl
| Download URL | orbite-0.1.0b1-cp314-cp314-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
50566bac78ec8bd8f0963c4307e6159dcb944ad0e2cffff78ba8be22c7c2a119
|
|
BLAKE2b-256 checksum How to use checksums |
f24e7e86c8155fd52713efc356b5405cddf878f9b79582f3943962f76acf9049
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | orbite-0.1.0b1-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
a7013fe8b59b7c0b03ce552f8d132d4af7989077601de62e342c519cfddeb5a6
|
|
BLAKE2b-256 checksum How to use checksums |
a7a491066e3ef9ad6ecfebe3d8a9a0f69b7b1764d75bfaf89737a9a24f26ca14
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp313-cp313-manylinux_2_28_aarch64.whl
| Download URL | orbite-0.1.0b1-cp313-cp313-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ebbd42535a804f2df6b9ed9a189fa2220129dd18b49ceff0cfa92d72ccab95bb
|
|
BLAKE2b-256 checksum How to use checksums |
c93dd550cf5e5bd9a855a63ccc2c79c8a15f2a5e76f9e4bc8ea6db52bd3f9c46
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | orbite-0.1.0b1-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
07ab27e792e2bde17d9502ba322c5ab14bb5a7b4d602d07a31d4793c1fe0e20f
|
|
BLAKE2b-256 checksum How to use checksums |
0b89ca94a61cd6ff9db81e99bbe77816ef64b19e4aa95bf2eac2e6a98099b297
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | orbite-0.1.0b1-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
c9bad21ada139cb6c0579043f5124cffa89d7415e8d9ba7525a3308aff3261b4
|
|
BLAKE2b-256 checksum How to use checksums |
cf57c5693e3ea0b2a8690d688be77eebd8927b20d8ac1afcc989fe623f326d14
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | orbite-0.1.0b1-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1d818dbe90ca1a90f51f93ddeed33cbd7044c15f761dff82e76abdabc74ee0e5
|
|
BLAKE2b-256 checksum How to use checksums |
bf8bc6f1d681f1ab1f982f10d050a18a3e40d2c5f6dd6be7d631f4f046660fcc
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | orbite-0.1.0b1-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
9c94ec4bed1beaafba57564632f926ed482c4e77587e6dd2e9d24ec4fc63d752
|
|
BLAKE2b-256 checksum How to use checksums |
5f827b7e24c1a7597b80770701e9f6218b38f230e0b653d2cf861075e3ed03eb
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | orbite-0.1.0b1-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
12b2139e4dc5361778a8a263b82c22e3bea70794d56008dd2ff310e1b6dfffed
|
|
BLAKE2b-256 checksum How to use checksums |
809dd39085e58af56eac751d5cc512d5b731ab9cb7d5a21c9dd9cd980866e6e4
|
| 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 Nov 12, 2026.
Transparency logRelease files / orbite-0.1.0b1-cp310-cp310-manylinux_2_28_aarch64.whl
| Download URL | orbite-0.1.0b1-cp310-cp310-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
49373478fa3a6d0bf81a67a956c98078453ce8088b33923d70a0b2d5e5ff2c2f
|
|
BLAKE2b-256 checksum How to use checksums |
1a7734a04f0cb320ad4fe787465e554a7e2a470af286675b1ac0993a48d28466
|
| 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 Nov 12, 2026.
Transparency logSecurity for orbite 0.1.0b1
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 11 files in this release have been uploaded with provenance metadata.
Attestation for orbite-0.1.0b1.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 Nov 12, 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.