Comment by mdeichmann
2 years ago
This reads like a book, thank you so much for putting this together!
> About value prop: Thanks for the feedback! We are already trying to be as vocal about it as possible by writing great docs etc. but can probably do better.
> PLG & OSS: thanks for the hint, we will be careful around managing deployments within customer VPCs.
> Pricing: Currently picked storage as the first metric to price on as this varies a lot across users. Some use langfuse to track complex embedding processes with a lot of context, others just simple chat messages with relatively low-context, low-value events.
> OTel: We looked into it but did not go into all the details. We wanted to have a product out there fast and liked the experience of e.g. Posthog SDKs. I might reach out to you concerning this topic after investing more time on it. Thanks for the offer!
> OLAP: Agree, i also learned to tackle scaling issues once they appear and so far we are good. Interesting that Supabase has no horizontal scaling. This would be one of the main reasons to use it IMO.
Re: Supabase and timescaledb.
Just want to make a bit more clear, Supabase has the ability to do some distribution via replication, but it isn't a true multi-master DB.
Timescaledb does support a multi-node config (https://docs.timescale.com/self-hosted/latest/multinode-time...) on top of postgres but that isn't in the open-source apache-licensed version, instead it is only in Timescales's community BSL version which isn't license compatible with supabase
And yeah, please don't hesitate to reach out in regards to OTel... lots of opportunity but also not as simple ;)