Skip to main content

rlp-sdk (Python)

PyPI

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() raise DaytonaNotSupportedError (HTTP 501 semantics). start() tolerates an already-running sandbox but cannot revive a stopped/failed one — recreate instead.
  • Create is async. create() polls GET /vms/:id until started.
  • Extras on create: mode (burstable|dedicated), fractional cpu, 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.2

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

Source distribution (sdist)

Source distribution for rlp-sdk 0.3.2
File Size Uploaded
rlp_sdk-0.3.2.tar.gz 24.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rlp-sdk 0.3.2
File Interpreter ABI Platform
rlp_sdk-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 54.6 kB

Release files / rlp_sdk-0.3.2.tar.gz

Download URL rlp_sdk-0.3.2.tar.gz
Size 24.9 kB
Tags Source
SHA-256 checksum
How to use checksums
a1bde1144d5ad415f776215716ded655773a7d374e5365491bf3b6b3a1996f02
BLAKE2b-256 checksum
How to use checksums
eee0f3e69c2e06739a30288e767f43d5b706c7204483d9e55ac64b6ab52f4afa
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

Release files / rlp_sdk-0.3.2-py3-none-any.whl

Download URL rlp_sdk-0.3.2-py3-none-any.whl
Size 29.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d22fc0245041c3da25445945a2ce9f6143ec135087ffd50e7dd67ce18c466669
BLAKE2b-256 checksum
How to use checksums
83cda56b34a07de9c7e0e5650c509398fd8a1440a9c276015edfe1285d552e1b
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

Release history Release notifications | RSS feed

This release

0.3.2 This release

2 release files

0.3.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page