code_reader

It was the other way around for us. All active users were interested in building multitenant apps that involved vector embeddings as well. So, it made sense to focus before we expand

Yeah, fair point. We will have nothing to pivot on. It is more of a focus question for us and being true to our users. Where do we see demand, and what do we prioritize? We could market as a general-purpose DB and then not prioritize needs from non-AI use cases. This would leave users frustrated. Instead, the problems we are solving for AI have a massive overlap. This helps us mature faster and onboard more non-AI use cases over time.

Nile is general purpose but we probably do well at this point for new use cases. All the new use case apps we have spoken to are building AI into it and have needs from the database. It made sense for us to focus on this market first and expand over time. You can see this in the YC directory as well. Almost 200 B2B companies in the latest batch and they are all trying to build it in an AI-native way https://www.ycombinator.com/companies?batch=W24&industry=B2B

We mention that there is a spectrum of solutions to this in the blog but plan to go into it in a separate blog. The main thing is that users no longer have to think about any of these options. Nile does it natively by having a page per tenant architecture and can move tenant's data between computes.