I just set up an account hoping this would be an amazing addition to the toolbos for our dev team…. But it appears that this is really just a B2C offering.
Are there any plans for business/team plans?
Can you clarify what you mean by team plans and how that differs from the plans available to choose from already?
We absolutely intend Sprites to be something that teams build on top of.
So like the ability to add multiple users to our account, each able to create their own API keys and having a single consolidated billing method. Also, SSO would be a plus.
1 Like
Sprites is a Fly.io product, so all the org management features of Fly.io are relevant.
You can invite members to a Fly.io organisation: https://fly.io/dashboard/ORG_SLUG/team
Once a user is a member of an org, they can go to https://sprites.dev/account/ORG_SLUG and generate an API token and then sprite auth setup --token $TOKEN to auth the CLI (or just sprite login to obviate the need to pre-generate a token).
Fly.io orgs are the means of billing organisation. If everyone is in the same Fly.io org, then you only need to setup billing for this one org and everything is billed through it.
Alternatively, if you want each dev to have their own Sprites plan, you can create a “billing org” for which you attach a payment method, and then you can create one linked org per dev (see image below, from https://fly.io/organizations/new), and invite only one dev to each of those linked orgs.
Setting these up as linked orgs means all the linked org’s charges are billed through the billing org.
You can setup an org to require SSO, see below from https://fly.io/dashboard/ORG_SLUG/settings
If you go the billing org/linked orgs route, you’d need to do this for each linked org in addition to for the billing org.
Users can then setup SSO at https://fly.io/user/settings:
OK … awesome … we are getting started on that.
If we want each Dev to be able to manage their own sprites without having access to each others’ sprites, will they each require a separate (linked) org?
In other words, are sprites automatically shared with all members of an org?
Org per dev is the right approach if you want platform-level isolation, yeh.
Plans can’t be shared between linked orgs or from the parent org though, so if you wanted a plan you’d need one per linked org.
Yup. Similar notion to e.g. Fly.io apps/Machines/Volumes being accessible to all members of a Fly.io org, all Sprites in an org are accessible to any member of that org.
Oh one other possible option that is not as good but might be sufficient is restricted tokens, which are tokens that only permit access to Sprites with a specific name prefix (see https://sprites.dev/account/ORG_SLUG - the gear next to the “Create Token” button)
You can also limit the number of Sprites the token can create.
With the token you can sprite auth setup --token "my-org/abc123/token-id/token-value" to auth the CLI.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.