rlp-sdk (Python)
Native rl-platform SDK with a Daytona-compatible interface (v0.190.x-shaped)
so existing Daytona code is near drop-in. It drives rl-platform's native API
(/vms, /daytona/snapshots) and the toolbox proxy directly.
- PyPI package:
rlp-sdk - Import module:
rlp - Requires: Python >= 3.9
Install
pip install rlp-sdk # or: uv pip install rlp-sdk / uv add rlp-sdk
Quickstart
from rlp import Daytona, DaytonaConfig, CreateSandboxFromSnapshotParams
daytona = Daytona(DaytonaConfig(
api_url="http://<api-host>:8088", # native API root
api_key="rlp_...", # rlp-api mint-key <name>
toolbox_url="http://<proxy-host>:9000/toolbox",
))
# Cache a registry image as a snapshot (image alias).
from rlp import CreateSnapshotParams, Resources
snap = daytona.snapshot.create(
CreateSnapshotParams(name="py312", image="python:3.12-slim",
resources=Resources(cpu=1, memory=1, disk=1)),
on_logs=print,
)
# Create a sandbox from it and run a command.
sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="py312"))
r = sandbox.process.exec("echo hello")
print(r.exit_code, r.result)
daytona.delete(sandbox)
Configuration
| Field / env | Purpose |
|---|---|
api_url / RLP_API_URL / DAYTONA_API_URL |
Native control-plane API root |
api_key / RLP_API_KEY / DAYTONA_API_KEY |
Bearer API key (rlp_...) |
toolbox_url / RLP_TOOLBOX_URL |
Toolbox proxy base (.../toolbox); required for fs/git/process |
target / RLP_TARGET |
Optional region/target label |
rl-platform specifics vs Daytona
- No warm stop/start.
stop()/archive()raiseDaytonaNotSupportedError(HTTP 501 semantics).start()tolerates an already-running sandbox but cannot revive a stopped/failed one — recreate instead. - Create is async.
create()pollsGET /vms/:iduntilstarted. - Extras on create:
mode(burstable|dedicated), fractionalcpu,ports,docker_data_mib. sandbox.create_snapshot(name, kind)— native VM-state capture (disk/full), distinct from Daytona image-alias snapshots.sandbox.access_token— per-VM toolbox credential returned once on create.
Surface (v1)
Daytona (create/get/list/start/delete + snapshot service), Sandbox
(fs/git/process, create_snapshot, lifecycle), SnapshotService
(create/get/list/delete/activate), toolbox Process/FileSystem/Git, and the
full Daytona error hierarchy. PTY/LSP/ComputerUse/Volumes and async are deferred.
Release files for rlp-sdk 0.3.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 | |
|---|---|---|---|
| rlp_sdk-0.3.1.tar.gz | 24.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rlp_sdk-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.6 kB
Release files / rlp_sdk-0.3.1.tar.gz
| Download URL | rlp_sdk-0.3.1.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29ff318c35584fa85937d1d2773c1685550dadd6d2c25c58f439cfb2855110ae
|
|
BLAKE2b-256 checksum How to use checksums |
ffdc22a2faccfb595488c92842a397e3e24b501cf34f2571bd5ae16369ff3691
|
| 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 Aug 5, 2026.
Transparency logRelease files / rlp_sdk-0.3.1-py3-none-any.whl
| Download URL | rlp_sdk-0.3.1-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92bced69899ae137b69680c30f85b71f8d84bf19654c89e78c55c561822286bb
|
|
BLAKE2b-256 checksum How to use checksums |
2b8c26c6efb76b51be8d176635452bffc878152870743161fd3170d9cf14284d
|
| 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 Aug 5, 2026.
Transparency log