runtm-api
FastAPI control plane for Runtm. See the API docs for endpoint reference.
Hosted API: app.runtm.com
Endpoints
| Method | Path | Description |
|---|---|---|
| POST | /v0/deployments |
Create deployment (multipart: manifest + artifact.zip) |
| GET | /v0/deployments/:id |
Get deployment status, URL, timestamps, error |
| GET | /v0/deployments/:id/logs |
Get build/deploy logs |
Creating Deployments
POST /v0/deployments
Creates a new deployment or redeploys an existing one (based on manifest name).
Query Parameters:
new=true- Force creation of new deployment instead of redeploying existingtier=starter|standard|performance- Override machine tier from manifest
Request:
manifest(file) -runtm.yamlmanifest fileartifact(file) -artifact.zipcontaining project files
Headers:
Authorization: Bearer <token>- API authentication tokenIdempotency-Key: <key>- Optional idempotency key for retries
Example:
curl -X POST "http://localhost:8000/v0/deployments?tier=performance" \
-H "Authorization: Bearer $RUNTM_API_KEY" \
-F "manifest=@runtm.yaml" \
-F "artifact=@artifact.zip"
Machine Tiers:
All deployments use auto-stop for cost savings (machines stop when idle and start automatically on traffic).
| Tier | CPUs | Memory | Est. Cost |
|---|---|---|---|
starter (default) |
1 shared | 256MB | ~$2/month* |
standard |
1 shared | 512MB | ~$5/month* |
performance |
2 shared | 1GB | ~$10/month* |
*Costs are estimates for 24/7 operation. With auto-stop, costs are much lower for low-traffic services.
Development
# Install dependencies
pip install -e ".[dev]"
# Run migrations
alembic upgrade head
# Start server
uvicorn runtm_api.main:app --reload --host 0.0.0.0 --port 8000
# Run tests
pytest
Environment Variables
| Variable | Description | Default |
|---|---|---|
DATABASE_URL |
PostgreSQL connection string | Required |
REDIS_URL |
Redis connection string | Required |
RUNTM_API_SECRET |
API authentication secret (what server validates against) | Required |
ARTIFACT_STORAGE_PATH |
Local artifact storage path | /artifacts |
ARTIFACT_STORAGE_BACKEND |
Storage backend: local or s3 |
local |
BUCKET_NAME |
S3/Tigris bucket name (when backend=s3) | - |
AWS_ENDPOINT_URL_S3 |
S3 endpoint URL (e.g. https://fly.storage.tigris.dev) |
- |
AUTH_MODE |
Auth mode: single_tenant or multi_tenant |
single_tenant |
1 maintainer
Metadata
1 maintainer
Release files for runtm-api 0.2.163
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 | |
|---|---|---|---|---|
| runtm_api-0.2.163.tar.gz | 66.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runtm_api-0.2.163-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 128.3 kB
Release files / runtm_api-0.2.163.tar.gz
| Download URL | runtm_api-0.2.163.tar.gz |
|---|---|
| Size | 66.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3170c6950b548fc6403a8b5162a640647c1c0360dbc8e00ef1de68c724cb31e4
|
|
BLAKE2b-256 checksum How to use checksums |
fdbeb9cde2e6d149b892407d0862f478a78f999a1aaae38186570e1597a1f39e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / runtm_api-0.2.163-py3-none-any.whl
| Download URL | runtm_api-0.2.163-py3-none-any.whl |
|---|---|
| Size | 62.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d26e6aaeb86237c30177de8941be80ea9e5dccb19e48890bc1bb52f20265d3d0
|
|
BLAKE2b-256 checksum How to use checksums |
452686a54ba85a42612c8c7a7f67636a38b6ee374f2c4dbb3464eca30ccb1e80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for runtm-api 0.2.163
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
