|
|
Hi there!
|
|
Wondering what we've been up to these past few weeks? Check this out!
|
|
|
|
Dimensions for grouping events
|
When creating a new billable metric, you can define dimensions that will allow you to group events according to their properties.
For example, cloud computing platforms may want to group usage events according to the server region selected by the customer (e.g. vCPU in us-east and vCPU in eu-south).
When creating a plan, they will then be able to set a specific price for each group (e.g. $0.052 per hour for us-east and $0.048 per hour for eu-south).
You can define up to two dimensions for your billable metrics, either through the user interface or the API.
|
|
|
|
|
|
|
|
|
|
|
Have you noticed anything different?
|
|
Our website, of course! As we keep adding new features to Lago, we felt that our website needed a makeover. Kudos to our Product team who have been working hard on this project. Hope you like it!
|
|
|
Which pricing model should you choose?
|
What's actually a 'good' pricing model? Subscription-based, like Typeform? Only usage-based, like Snowflake's pay-as-you-go plans? There is also Retool and their transparent per-seat pricing.
If you're not familiar with these models (and others), we've listed all their advantages and drawbacks in this blog post.
|
|
|
|
|
|
|
How soon should you have a design system?
|
Should we have a design system? How soon should we build it? Are we going to waste our time?
In this article, our Founding Designer and Product Manager Michael Ponrajah explains why early-stage companies should have a design system and how his experiences at Contentsquare and Qonto inspired him to create Lago's design system.
|
|
|
|
|
|
|
Thank you and stay tuned!
|
|
The Lago Team
|
|
|
|
|
Lago is a company backed by
Y Combinator
|
Lago, built with love around the world!
|
|
