File upload from any embedded device, straight to the cloud
Stream audio, images, and binary blobs from MCU to S3 without writing the upload pipeline.
How it works
Most embedded teams need to move files from devices to the cloud. Voice memos from a wearable, frames from a camera, calibration dumps from a bench unit. The standard playbook is to write an HTTP POST loop, sign URLs against S3, handle retries and partial failures, then babysit the whole thing in production.
SCADABLE replaces that. libscadable links into your firmware, chunks files, signs each chunk against your bucket (or our managed S3-compatible storage), retries on flaky cellular, and exposes a single function call.
A few lines of C
#include "scadable.h"
// On the ESP32. Upload a captured audio buffer.
uint8_t buf[BUF_SIZE];
size_t len = capture_audio(buf, BUF_SIZE);
scadable_file_upload("audio-${deviceId}-${ts}.wav", buf, len);What you get out of the box
- Chunked uploads with resumable transfers over flaky cellular and Wi-Fi
- Per-device signed URLs. No AWS credentials on the device
- Automatic retry with exponential backoff and idempotency tokens
- S3-compatible storage by default, or bring your own bucket
- Files indexed by device ID and timestamp in the SCADABLE console
Built for real fleets
Corvita Biomedical streams patient audio off wearables. Verdant Metrics uploads camera frames from solar field stations. Both teams ship on the same primitive. One function call, no upload pipeline to maintain.
Bring your fleet onto SCADABLE.
Connect a repo, leave with a fleet you can manage from your codebase.