Over the last few hours, 111 people signed up for Zipbox in fast bursts.
104 took the $25 free credit. 4 added a card. We then noticed a pattern. Junk usernames, throwaway emails, only free boxes booted, $25 of LLM model calls drained in a short period of time.
First we tried the polite fix: make the $25 require a card. Shipped it at 2:30pm.
Then we found accounts still booting free machines with no card at all. The free tier was skipping the card check entirely. That was the actual hole, and it had been open the whole time.
So as of today: a card on file and a $5 top-up to boot anything, including the free Tiny.
The Tiny is still free. $0/hr, we don't charge you for the machine, that hasn't changed.
We also killed the $25 signup credit outright. It only ever funded this.
Sorry to everyone using it honestly. You're the reason this sucks to write.
Your first sandbox on @Zipbox_ is now free forever. Not a trial. Plus you get a free $25 credit.
1 vCPU, 2GB RAM, 20GB disk, full root, Claude Code, Codex, etc. No card needed.
Leave it a day and it pauses itself. Files kept, one click brings it back.
A remote @Zipbox_ machine can stream your microphone + speaker with almost no noticeable latency.
Here I'm using the /voice command directly inside Claude Code. Feels surprisingly local. 🔊🎙️
I've been working on a presentation for @Zipbox_ and thought this was worth sharing.
If you've used coding agents in the last 6 months, there's a 150% chance you've exposed an API key to the agent. We wanted to solve that without limiting what the agent can do.
So when you add an API key to Zipbox, it's encrypted from your browser all the way into Cloudflare's Secret Store. Inside the sandbox, your agent only gets a fake placeholder key, like the one in the screenshot.
When the agent makes an API call, our Toolbooth proxy intercepts it, recognizes the placeholder, swaps in the real key, and forwards the request.
The important part: your agent never sees the real API key. It never exists inside the sandbox, and the key stays within Cloudflare's infrastructure. Your API keys are SAFU 🔐
Crypto keys are a different story. Be careful with those. We do give your agent its own crypto wallet using @privy_io
@ultrathinktrash full YOLO is the only sane mode, just not on your own laptop. we do it on disposable Firecracker boxes and stopped caring what it deletes. https://t.co/NKNATDGyBi
@seanphan@NielsRogge@danielhanchen yeah the built in sandbox is either too strict or something jumps out of it. we gave up and run agents in throwaway microVMs instead. https://t.co/NKNATDGyBi
@vanamerongen yeah prompt fatigue just becomes YOLO with extra steps. we run agents on disposable Firecracker boxes so it stops mattering. https://t.co/MdYflewB3j
@Love2Code@domenic@thsottiaux the bypass-at-will part is the killer, a sandbox the agent can step out of isn't one. we just gave it a disposable microVM instead so it can do whatever inside. https://t.co/MdYflewB3j
@RenaudAdorno@calltheball_@anothercohen same setup here for a while, phone to Mac Mini. we ended up moving it to a cloud Firecracker box so the mini isn't the single point of failure. https://t.co/NKNATDGyBi
The best part of @zipbox_’s new email feature:
Agent 1 spins up the QA stack, watches logs then files bugs to @Github
Agent 2 signs up with its own email, confirms the OTP, and QAs using headless Chrome.
We automated dev, code review, and now QA.
Hands-free vibe building
Every agent just got a passport.
Today, every Zipbox harness gets its own:
📧 Email inbox 🌐 Public HTTP w/ custom subdomains Ξ EVM wallet ◎ Solana wallet
One click and you’re all setup!
4/5
This also makes parallel work much simpler.
Give one machine to the builder. Give another to QA. Give another to security.
Each gets its own identity, and they can access and test each other’s work.
Shut them down when the job is done.