Introduce milo's billing system and billing accounts#253
Introduce milo's billing system and billing accounts#253
Conversation
scotwells
requested review from
jacobsmith928,
joshlreese,
mksinghtx,
ssmyser917 and
zsmithnyc
|
RFC @datum-cloud/engineering |
|
|
||
| Milo currently lacks a platform-level way to declare financial responsibility | ||
| for usage. Teams need a simple, authoritative place to set who pays for a | ||
| project, support common commercial structures (departments, regions, resellers), |
There was a problem hiding this comment.
This might also be a place to call out locality (e.g. billing account based specifically in EU vs US) which is an important construct for mature cloud billing.
| --> | ||
|
|
||
| - Make **Billing Account** the authoritative payer entity for the platform. | ||
| - Allow **multiple accounts per organization** to model departments, regions, or |
There was a problem hiding this comment.
@scotwells how would this interact with the concept of "root" or global accounts? For instance, Cisco might have 20 sub accounts loosely tied to a root account due to regions (Ireland, US, Taiwan) or entity (Splunk, Isovalent, some new acquisition they just closed).
There was a problem hiding this comment.
I see you address this a bit as a future enhancement
| Why should this Enhancement _not_ be implemented? | ||
| --> | ||
|
|
||
| <!-- ## Alternatives --> |
There was a problem hiding this comment.
@scotwells this could be a place to reference some great examples or how this primitive is inline with emerging standards. Clearly something like GCP or AWS, but maybe also how this approach would allow Milo to interface with financial infrastructure like Orb, Metronome, Stripe, etc in an elegant way.
| project-to-billing-account associations with audit trail | ||
| - **Hierarchical Billing**: Support for billing sub-accounts in reseller and | ||
| channel partner scenarios | ||
|
|
There was a problem hiding this comment.
@scotwells consider breaking out a section for Usage Billing / Metering here before Commits
| ### Service Integration (Planned) | ||
|
|
||
| Planned deep integration with the platform's service catalog: | ||
| - **Entitlement Controls**: Service access and pricing governed by billing |
There was a problem hiding this comment.
I don't love "Entitlements" dual use in my brain for having access to a thing and a one time or recurring instance of a subscription. just want to make sure we find a good way to be clear on language.
zsmithnyc
left a comment
zsmithnyc
left a comment
There was a problem hiding this comment.
added 2 comments to clear up but otherwise looking good.
6 participants
Summary
Introduces the overall vision for Milo's billing platform to support service providers charging their consumers and defines the billing account resource as the core primitive to identity the party responsible for paying for a service costs.
Future enhancements: