Comment by simonw
2 days ago
Sprites are about more than just providing an environment for Claude Code et al to run code in. They're also useful for anyone who's building their own product that needs an inexpensive way to execute unsafe code.
2 days ago
Sprites are about more than just providing an environment for Claude Code et al to run code in. They're also useful for anyone who's building their own product that needs an inexpensive way to execute unsafe code.
And the way you compete is be cheap enough and DX. Because Lambda.
Why are you so sure "DX" is the right way to compete with commodity full-stack hosting? Have you had Claude deploy on AWS recently? It one-shots deployments just fine.
DX ups its game.
You got claude to deploy. Cool.
I clicked a button in my PaaS and I have an oncall responder and incident manager ready to go.
6 replies →
> execute unsafe code.
I have a question regarding sprites but when executing unsafe code, because by definition its unsafe, what happens if the code violates terms of service of fly/sprites. Would only that particular sprite be removed or would it escalate to whole account level ban and the risks attached to it or would they take a look at repeated offenders.
from fly's terms of service Section 1.4(d) and section 9.2 respectively
> Customer will not... "sublicense any of Customer's rights under this Agreement, or otherwise use the Fly.io Services for the benefit of a third party."
> "Either party may terminate this Agreement for no reason or any reason upon written notice to the other party, effective immediately at the end of the then current Subscription Term."
ignoring the TOS angle
unsafe code is likely being used as in unsafe rust, which is different from exploit code
certainly the wording seems to leave the door open for potentially compromised code as in supply-chain attack credential stealer or prompt injection data exfiltration, but sprites are not marketed as sandboxes for malware detonation