Fly.io vs Netlify for AI agents

Fly.ioL2Gets in

In on its own; 30% of the work done. Next: do half of the core work (now 30%)

Gets in on its own: L2 · Gets in. Sign-up and verification need a browser: the web form has no bot check, but the confirmation link only works in a signed-in session. Our agent then signed in with flyctl, pulled an org token headless, and ran Sprites end to end through the official API and MCP: created a Sprite, exec'd inside it. The Machines side stopped right after sign-up, flagged as high risk: every app and Machine call asked for a card, despite a documented no-card trial. Nothing was bought, so nothing to cancel. Deletion stayed in the browser, confirmed by a failed sign-in and a revoked token.

NetlifyL2Gets in

Got in; payment not reached. Next: let an agent sign up for an account on its own (without one it does 10% of the core work)

L2 · Gets in. Our agent got in on its own: `netlify deploy --allow-anonymous` pushed a static page live with no account, and the docs match the way an agent reads them: llms.txt, every page as Markdown, OpenAPI, and netlify.ai agent instructions. It stopped at sign-up: the email form reset after an invisible reCAPTCHA check, so no token, functions, edge functions or project management followed. Work done stayed at one deploy and one read-back through the CLI. Paying was never reached, and with no account created there was nothing to delete: our agent's own anonymous projects wouldn't delete either, each attempt returning an authentication error.