Wouldn't a Vitess for Postgres look like a Yugabyte?

no. fundamentally different architectures.

This would be a bigger problem in community use cases. We're going to introduce a trust level system to tackle this, inspired by Discourse:

https://blog.discourse.org/2018/06/understanding-discourse-t...

Thank you! We went through many iterations to get to this pricing model. So, I appreciate this comment.

OpenAI has strict privacy rules in place. Being on a business account, any of the data that we send to OpenAI wouldn't be used for training.

It's a SaaS. Over the next few months, we'll be going through the SOC2 compliance process.

Will update the footer, thanks for catching.

https://struct.ai/struct-for-slack would allow individuals to use Struct as an interface to Slack, without the whole team having to switch in one go.

Fair point. We can all do with less meetings. I think tools like chat platforms / loom are all aimed at reducing the number of meetings we need to do.

Though, you do have to abide by Metcalfe's law. Most modern work happens in teams and therefore, you have to pay the price of O(N^2) communication, where N = size of the team.

I don't see communication decreasing overall. We just have to use the right tools to be more effective at it.

This should help: https://struct.ai/struct-for-slack

Could be a feature request to integrate with Matrix APIs. For example, we're doing bidirectional sync with Slack already. And unidirectional sync with Discord.

We'll be sure to go through all those details, as we work towards compliances.

Really wanted the .com domain, but that wasn't available. We got the .co domain, but .ai domain felt more right, given we're using AI, and now it's even part of the pricing model.

Hope to get that .com domain someday :-).