Hey community — I’ve been building MediaRuntime, an asynchronous media-processing API for developers, and I’m finally at the stage where I’d value outside feedback. The problem I wanted to solve was the amount of infrastructure that normally grows around media processing: FFmpeg scripts, queues, storage conventions, retries, webhook delivery, billing estimates, and inconsistent output paths. With MediaRuntime, one job can request several related outputs—for example: - Video renditions, HLS or DASH - Audio conversion and transcription - Posters, thumbnails and contact sheets - Image derivatives and loading placeholders - Audiograms and waveform data - Compatibility and forensic media reports - QR and barcode detection - Moderation and image privacy redaction Instead of treating every artifact as a separate result, the completed job returns one ZIP bundle containing the requested output tree and client-safe metadata. There’s also: - A browser-authenticated CLI that accepts local file paths - Node.js and Python SDKs - Go and PHP HTTP quickstarts - Hosted/versioned processing recipes - Signed terminal webhooks - A public OpenAPI document You can run a real job without creating an account here: **Sandbox:** https://mediaruntime.com/sandbox I’m also offering **$10 in processing credit** so developers can test their own media workloads: **Developer promotion:** MR-4Y8ZA-QN4GP-VKV2Y-EK4PW If you try it, I would especially appreciate feedback about the job API, preset discoverability, ZIP-bundle model, documentation, pricing clarity, or any workflow that feels difficult to express. **Feedback form:** https://mediaruntime.com/develop... This is self-promotion—I built the product—but I’m sharing it because I’d genuinely like technical feedback from developers who work with media, uploads, storage, background jobs, or API integrations.

MediaRuntime

One API for video, audio, and images: transcode and deliver

One API for video, audio, and images: transcode and deliver