Sprites.dev as my customer's environment

[SkrOYC]

Can I -or am I allowed even- use Sprites as part of my SaaS so that each customer has their own Sprite?

The mental model is to provide something like today’s chat experiences (Claude/ChatGPT/Gemini/Grok/Kimi/Minimax/Etc) where the agent has a sandbox if needed to be used in a way that each customer gets it’s own Sprite (no Claude Code, Gemini nor Codex) for this purpose.

My agent is a custom one for my own SaaS. The agent wouldn’t deploy apps nor things like that, it’s just to serve Sprite instead of a Fly Machine per customer.

Thanks in advance

[mayailurus]

Hi… It looks like that’s not only allowed but actually rather encouraged/common:

@jfent

Lots of customers of ours are using a Sprite-per-customer sort of setup

My impression is that it was even one of the original motivating cases (along with security-firm clientele) for the product, although I may be wrong there…

Also, this older blog post pre-dates Sprites, but it gives an idea of Fly.io’s overall perspective on such things:

Our Best Customers Are Now Robots

(As far as I know, that general tenor hasn’t changed any.)

[SkrOYC]

What makes it confusing is the pricing model and the heavy focus on “built in Agent CLIs”.

I think maybe the plan was not originally to be used as one Sprite per Customer.

Pricing wise, limiting concurrency on pay as you go while not on fixed price tiers is what confused me even more. Any official clues?

I see the pay as you go option as the one I would use for several hundred users

[eli]

hi! I’ll make sure this info finds its way to the website but the PAYG tier does have limits in place too-- if you’re on the free plan you can see it in the dashboard

we definitely see people using a customer-per-sprite model; in fact, we even initially added more plans with higher concurrency + usage limits to better support this approach!

More Sprites Plans!

Hey folks! We’ve just shipped more Sprites plans for those that want a higher concurrent active Sprites allowance. Plans include the listed monthly allowances. Usage beyond included amounts is billed at standard usage-based rates (see Sprites - Stateful sandboxes): Plan Price/month Max Concurrent Active Sprites Max Warm Sprites CPU/hours RAM/hours Storage/GB-months Support Adventurer Level 20 $20.00 20 20 450 1800 50 Community Veteran Level 50 $50.00 50 50 800 3200 100 Community Her…

[SkrOYC]

@eli

PAYG tier does have limits in place

I am actually saying exactly this!

I have seen that PAYG has a limit of 3 for concurrency which sounds a little counter intuitive for me.

Is there any official statement regarding the mental model for Sprites.dev as a produict? It’s mainly with end users in mind that want to “vibe code” using an agent CLI and the rest of use cases fall into “do your best with what is available” (both features -which are excellent- and pricing)?