Product feedback

Add the ability to create multiple API keys linked to the same organization and ability to rotate them.

When we have a plan which we consider a default plan. We can assign this plan to many customers but for some customers we need to give them the default plan but with some modifications for specific values thanks to override feature (which creates a children plan). If any change in the child plan 👉 then these changes should not affect the parent plan if any change in the parent plan 👉 if the child plan inherited these values from the parent then the child plan should be changed 👉 if the child plan has its own version of the these values then no change should be done in the child plan It means: Add a new charge in parent plan -> Add this charge in child plan Remove a charge in parent plan -> Remove this charge in child plan Edit a charge in parent plan -> Do NOT edit this charge in child plan

Native integration with HubSpot to import customers, plans and subscriptions into Lago.

The first version of the billing portal allows customers to access their invoices. Additional features could include: Ability to see current usage; Ability to pay invoices via PSP integration; Ability to manage subscriptions; and Ability to update customer information (e.g. address, email address, etc.). Please feel free to comment on this post if you have any other ideas.

Have tax rates calculated automatically via Anrok.

Description: Allow to get a list of all events within a period so one can perform custom aggregations using that data. Example: GET /api/v1/events?from=X&to=Y This would filter and return all events with timestamps between X and Y. Use case: Implement a billing log to show details of the events Perform 1d/7d/30d custom aggregations which might include other properties from the event.

Ability to export plans, customers, and invoices from the interface into Excel/CSV.

Handling multiple unpaid invoices for a customer can be a hassle when requesting separate payments. We want to simplify this by combining several invoices into a statement and asking for a single total payment amount.

Prices can be fluctuant in a period: July 01 - metric A: $10.00 per unit July 02 - metric A: $9.00 per unit July 03 - metric A: $9.50 per unit Lago apply the correct price based on the date the event is received and bill customers accordingly.

There's always a risk of customers not paying invoices generated at the end of a billing period. It would be beneficial to bill customers at given thresholds (units vs. amount) rather than waiting until the end of the period. This approach would allow for removing customer access if invoices are not paid and prevent having a highest amount of unpaid invoices.