Discover · convex.dev

No picture published by convex.dev

How to connect Convex to RunPod for serverless GPU workloads

Stack convex.dev

This is what was read here when it was published. convex.dev no longer carries it in what it publishes now.

Every GPU task I've run from a backend has the same problem: you fire off the job, then poll for results or wire up webhooks to know when it's done. This walkthrough shows a different approach. Convex triggers a GPU job on RunPod, and the RunPod worker calls mutations directly on Convex using the Python client. The frontend stays in sync through live queries. No polling, no webhook infrastructure. I'll walk through the full implementation using video background removal as the example, but the pattern works for any GPU workload — compression, transcription, object detection, whatever you need.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from Stack

  1. Convex Auth v2 is finally hereconvex.dev
  2. I asked Convex's CTO 34 spicy questionsconvex.dev
  3. I tried Expo's new Exact with Convexconvex.dev
  4. I built a better Claude Code and Codex appconvex.dev
  5. I built a component to make high frequency updates work on Convex (kinda)convex.dev
  6. Turns out database backups are NOT trivialconvex.dev