Are there any plans to support multi-tenancy for Sprites? basically the ability to create sub-accounts and billing via the API.
Sprites uses Fly.io orgs, so you can create “linked” orgs which are orgs that are billed through a “parent” billing organisation (see https://fly.io/organizations/new):
Is this the sort of thing you’re getting at? Sprites plans aren’t shared between these orgs though, so you’d need one plan per linked org if you choose that route.
Yes, orgs could work if they could be provisioned via an API. Also billing details for each org via API. Is there an API for orgs?
Ahh okay yeh there is a non-public API (our GraphQL API - we mention it on the community forum but it’s not technically a public API so there’s a chance of breaking changes) for orgs but it’s not possible to create a linked org via the API.
What exactly are you trying to achieve? Lots of customers of ours are using a Sprite-per-customer sort of setup, so I’m curious what you’re wanting from “sub accounts”?
And what are you imagining is the benefit of a sub account vs a totally separate org? If you want to have each “sub account” have different billing details, that’s just totally separate orgs in Fly.io platform terms.
Basically, an API to track per-sprite usage metrics and/or cost would be good enough. I’m not seeing an obvious way to do that via the sprites api nor the graphql.
After digging around graphQL, I don’t see any sprites-related metrics exposed via the endpoints. Is that accurate or am I missing something?
Yeh the place we put metrics is Grafana, but you are correct that currently we don’t make any Sprites-related metrics available.
I’ve put some feelers out about this internally; we have ambitions to make metrics available, it’s just not been a top priority. I can’t make any promises at all, but I’ll let you know what I hear back 
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.