AI/ML Engineer at a tech services company with 11-50 employees
Real User
Top 10
Jul 7, 2026
When setting up a database, a PostgreSQL instance, which is the most popular use of Supabase, instead of having to go and write and run an SQL line to create a pgvector on Supabase, it would be nice if the person creating the database for the project could just be asked with maybe a checkbox whether they want a vector database or not. If the person ticks the box, then you automatically create the vector database in the backend. If the person does not tick the box, which means they do not need it, then it does not happen. That way, you do not even have to go and write and run one line of SQL to create pgvector. In many ways Supabase is good, but there is always space for improvement. There is always also the space for bringing in features that probably developers do not even think should have, maybe because we have accepted it as a normal part of the problems of the industry that we have to just cope with.
Co-Founder at a tech services company with 1-10 employees
Real User
Top 5
Jun 9, 2026
I had problems integrating the vector directly into Supabase, so I had to use Google Vertex to generate the embeddings and the information I needed in the database. It would be nice if all of this could be integrated all in one place with Supabase. I would prefer not to have to use a different or external tool to create these embeddings. It would be nice to have everything integrated in the same way. Apart from that, I think that is one of the cons I found, but it is basic. That was my main concern in that regard. My advice for others looking into using Supabase Vector is to take into account how you are going to create the embeddings, as it is not an option implemented straight away in Supabase. You will need to handle the embeddings with an external tool, so make sure to consider how these integrations are going to be made.
Director at a tech services company with 1-10 employees
Real User
Top 5
May 23, 2026
One improvement I feel Supabase Vector could benefit from is that Supabase SDK stands out when comparing with a conventional Postgres SDK, and it would be even nicer if we could have a more direct way for access. I wish that there was a convenient way to make it compatible with the general Postgres database SDK, but this is actually not about the vector database; it is about the general Supabase SDK.
Software Developer at a performing arts with 1-10 employees
Real User
Top 10
Apr 7, 2026
I think the support system can be better because after Supabase Vector stopped working in India, there is no support. Nobody knows how to deal with the database now. The naming structure is a little difficult. If you are naming a table, the guidance is sometimes not clear. It's a very simple feature to add sometimes but the process is very difficult. When I'm in Supabase Vector, there is a feature where I have to create a table. At the start, for newcomers, it's difficult, and then it becomes hard. You have to look for the documentation and YouTube videos to understand how it works. Supabase Vector stopped working in India due to some government guidelines, so I have to switch with something else now.
The support for React Native CLI is an area with certain shortcomings where improvements are required. There is just one thing wrong with Supabase. In the free plan, if your project is not being used in seven days, then the solution will pause, so it will stop working, causing some stability issues. The tool can extend the period beyond seven days.
One area for the solution improvement is the inclusion of more sample code in various programming languages, particularly PHP. Expanding the support for complex transactional queries and enhancing scalability features for advanced use cases would also be beneficial.
Supabase Vector offers an efficient way to manage and query vector embeddings, catering to the needs of developers and data scientists seeking scalable solutions for vector-based data handling.
Supabase Vector is designed to streamline the process of storing, managing, and querying vector embeddings, essential for applications like machine learning algorithms and personalized recommendations. Its intuitive API and integration capabilities make it a preferred choice for tech professionals...
When setting up a database, a PostgreSQL instance, which is the most popular use of Supabase, instead of having to go and write and run an SQL line to create a pgvector on Supabase, it would be nice if the person creating the database for the project could just be asked with maybe a checkbox whether they want a vector database or not. If the person ticks the box, then you automatically create the vector database in the backend. If the person does not tick the box, which means they do not need it, then it does not happen. That way, you do not even have to go and write and run one line of SQL to create pgvector. In many ways Supabase is good, but there is always space for improvement. There is always also the space for bringing in features that probably developers do not even think should have, maybe because we have accepted it as a normal part of the problems of the industry that we have to just cope with.
I had problems integrating the vector directly into Supabase, so I had to use Google Vertex to generate the embeddings and the information I needed in the database. It would be nice if all of this could be integrated all in one place with Supabase. I would prefer not to have to use a different or external tool to create these embeddings. It would be nice to have everything integrated in the same way. Apart from that, I think that is one of the cons I found, but it is basic. That was my main concern in that regard. My advice for others looking into using Supabase Vector is to take into account how you are going to create the embeddings, as it is not an option implemented straight away in Supabase. You will need to handle the embeddings with an external tool, so make sure to consider how these integrations are going to be made.
One improvement I feel Supabase Vector could benefit from is that Supabase SDK stands out when comparing with a conventional Postgres SDK, and it would be even nicer if we could have a more direct way for access. I wish that there was a convenient way to make it compatible with the general Postgres database SDK, but this is actually not about the vector database; it is about the general Supabase SDK.
I think the support system can be better because after Supabase Vector stopped working in India, there is no support. Nobody knows how to deal with the database now. The naming structure is a little difficult. If you are naming a table, the guidance is sometimes not clear. It's a very simple feature to add sometimes but the process is very difficult. When I'm in Supabase Vector, there is a feature where I have to create a table. At the start, for newcomers, it's difficult, and then it becomes hard. You have to look for the documentation and YouTube videos to understand how it works. Supabase Vector stopped working in India due to some government guidelines, so I have to switch with something else now.
I think there are still many Postgres features that can be developed further by the Supabase team.
The support for React Native CLI is an area with certain shortcomings where improvements are required. There is just one thing wrong with Supabase. In the free plan, if your project is not being used in seven days, then the solution will pause, so it will stop working, causing some stability issues. The tool can extend the period beyond seven days.
One area for the solution improvement is the inclusion of more sample code in various programming languages, particularly PHP. Expanding the support for complex transactional queries and enhancing scalability features for advanced use cases would also be beneficial.