The snapshot/restore detail is the most interesting part to me. If artifacts really suspend to storage after inactivity and restore on next access, that's the same bet Fly.io made with Firecracker machines, and it mostly worked once restore times got under a few hundred ms. I'd love to see the author measure actual restore latency across artifact sizes, because that number decides whether this pattern can replace always-on preview environments. There's also a cost angle worth digging into: per-session ephemeral VMs are cheap to suspend, but storage and restore I/O for big node_modules trees add up fast at scale.
simonw
One thing that I didn't understand from this article was how you use this deployment platform.
Can you tell Claude code for web to build and deploy a web app using it? If so, does that end up with a public URL somewhere? Does that deployment continue working after your Claude code for web session ends?
show comments
gabrielsroka
Actual title: '
Anthropic's Hidden Vercel Competitor "Antspace"'
It's for Claude Code, not Claude web. And it's been posted here 3 times already.
simonw
"No systemd. No sshd. No cron. No logging daemon."
You can delete that sentence. Why would someone assume sshd or cron in an environment like this?
The snapshot/restore detail is the most interesting part to me. If artifacts really suspend to storage after inactivity and restore on next access, that's the same bet Fly.io made with Firecracker machines, and it mostly worked once restore times got under a few hundred ms. I'd love to see the author measure actual restore latency across artifact sizes, because that number decides whether this pattern can replace always-on preview environments. There's also a cost angle worth digging into: per-session ephemeral VMs are cheap to suspend, but storage and restore I/O for big node_modules trees add up fast at scale.
One thing that I didn't understand from this article was how you use this deployment platform.
Can you tell Claude code for web to build and deploy a web app using it? If so, does that end up with a public URL somewhere? Does that deployment continue working after your Claude code for web session ends?
Actual title: ' Anthropic's Hidden Vercel Competitor "Antspace"'
It's for Claude Code, not Claude web. And it's been posted here 3 times already.
"No systemd. No sshd. No cron. No logging daemon."
You can delete that sentence. Why would someone assume sshd or cron in an environment like this?
Omit needless words.