Building a product on Sprites for my own end users: OK under the ToS?

Questions / Help
1

Hi all,

I’m building a mobile app (not public yet) where users create and run coding-agent projects from their phone. Each user project gets its own Sprite, which my backend creates and manages through the Sprites API under my Fly.io account. Users never touch Fly directly; they only use my app.

Inside a Sprite, a coding agent edits and previews an Expo app for that user. So a Sprite runs user-directed and AI-generated code, and may hold credentials the user supplies for their own accounts (for example an AI provider API key), kept only inside that user’s Sprite.

The ToS grants use “for Customer’s internal use” and says not to use the services “for the benefit of a third party.” I’ve seen others expose Sprites to their own customers, and Sprites are pitched for agent sandboxes, so I assume this is fine, but I’d like it confirmed before I launch.

Questions:

  1. Is hosting end-user workloads on Sprites like this fine on the standard terms, or is a platform or partner agreement expected at some point?

  2. For user-directed and AI-generated code: what abuse handling do you expect from a platform like this (reports, takedowns, a contact address)?

  3. Any limits I should design for: Sprites per org, API rate limits on create/exec, or anything that changes at larger scale?

Thanks!

2

building something for end users on Sprites is not only okay but is very much welcomed! we’re currently in talks with our lawyers to clear up the wording around this.

we do expect you to promptly respond to abuse reports via email; I can’t share details of our abuse handling process in public for obvious reasons, but we do tend to be reasonable.

there’s no limit of Sprites per org. there is a limit to concurrently running sprites but you can increase that by upgrading to a higher tier plan.