|
|
Hi there!
|
|
Quick (but important) update this week...
|
|
|
|
Subscription end date
|
You can now set an end date to schedule the termination of a subscription (e.g. the subscription starts on October 4, 2023 and should automatically end one year later).
Lago will send a webhook message 45 days and 15 days before the subscription is terminated.
The end date can be set via the user interface or the Lago API. If no end date is set, the subscription will renew automatically.
|
|
|
|
|
|
|
|
|
Weighted sum aggregation
|
This new aggregation type allows users to compute usage based on a custom property and the time elapsed between two events (e.g. GB-seconds).
The corresponding metrics can be metered or recurring, and are always billed at the end of the billing period.
|
|
|
|
|
|
|
|
|
|
Open-source alternatives don't win by default
|
It's pretty common to hear people say that a product is the open-source equivalent of a famous closed-source solution. But is it enough to build a successful company around it? Probably not, and here's why.
|
|
|
Heads up! 👇
|
We're currently upgrading our infrastructure and setting up a new event ingestion system. As part of this project, we've decided to remove the validations that are automatically performed when ingesting events through the Lago API.
This means that the API will no longer return error messages when your events include incorrect parameters (e.g. wrong billable metric code, subscription not found, transaction_id already exists, etc.).
This change will take effect next week, when we release the new version of the app. Please contact us if you have any questions.
|
|
|
|
|
Thank you and stay tuned!
|
|
The Lago Team
|
|
|
|
|
Lago is a company backed by
Y Combinator
|
Lago, built with love around the world!
|
|
