A market and router for compute

Joined February 2025
🏁 ComputeSDK Actions are live What we built: ⚡ Massive concurrency for parallel dev cycles
🌐 Sandbox providers + regions
🌿 Git-first workflow portability
🛡️ Ordered fallback for reliability
🤖 Agent-native CLI + API Let’s get into it ↓
7
5
7
63
12,315
This is why we built our TTI is that we found some people were lying. problem solved now. we publish every week!
If you can’t start a customer’s workload (cold) within your supposed sandboxes spin-up time, you’re straight up lying to your users. Time to interactivity is the *only* number that matters.
5
291
ComputeSDK retweeted
We’re thrilled to be a launch partner for ComputeSDK actions, which allows you to run your CI jobs on unused sandbox capacity across several clouds — saving significantly on costs and avoiding centralized outages. I’ve known @HeyGarrison for a better part of a year now, and I love his vision of connecting all of this disparate compute together into a big pool that users can schedule across so that they never see downtime. Of course, in that world, you have to figure out how to get your data into each provider. More on that problem soon.
Just last week we announced ComputeSDK Actions. CI Is your biggest blocker and we’ve built a git agnostic actions system.
2
3
15
1,220
Just last week we announced ComputeSDK Actions. CI Is your biggest blocker and we’ve built a git agnostic actions system.
1
2
6
1,921
Now you can use your favorite sandbox provider to run your actions. We have support for @archildata @blaxelAI @namespacelabs @tensorlake + 7 more with new ones being added every day.
1
160