Pricing Plans

understanding pricing plans in amberflo, pricing plans are collections of rate templates that define how customers are billed these plans determine how usage is measured, priced, and rolled up into a final invoice available rate templates amberflo provides out of the box support for several common pricing models usage based customers are charged based on actual usage during the billing period seat based customers are billed for the number of active entities (such as users, files, or devices) at the end of the billing cycle flat rate customers pay a fixed amount per billing period flat rate plans can also include overage charges if usage exceeds predefined limits subscription based customers subscribe to a defined number of instances (similar to aws reserved instances) additional usage beyond the subscription is billed at overage rates service fees a percentage based charge is applied to the total invoice (for example, as a support or platform fee) default pricing plan amberflo always maintains a default pricing plan if there is only one pricing plan, it is automatically set as the default if multiple plans exist, you can configure which one is the default when a new customer is created and no pricing plan is explicitly assigned, the default plan will be applied automatically when their first usage event is ingested assigning pricing plans to customers pricing plans can be assigned to customers in two ways via the amberflo console use the customer page to manually assign a pricing plan via api programmatically assign plans using the amberflo api or sdks once a pricing plan is assigned, the customer’s usage will be rated according to the plan’s rules invoices are then generated at the defined billing frequency using those rates