One area where Hasura can improve is handling complex business logic, and for observability and debugging, improvement is needed. Hasura can improve around complex workflow support and managing large-scale permissions. A few things come to mind regarding documentation. Documentation is generally good, but for advanced production scenarios and architecture patterns, more real-world examples would help. Smoother integration and observability with monitoring and tracing tools would make troubleshooting easier. One improvement I would like is better support for large-scale schemas, and for complex logic. For complex transactional workloads, we still keep business logic in back-end services, so Hasura needs to become more efficient for heavy workloads.
Desarrollador De Software at a outsourcing company with 1,001-5,000 employees
Real User
Top 20
Jun 10, 2026
Hasura could improve with better documentation because I have not always known where to look for certain issues I have encountered. The CLI commands could provide better feedback when something fails. Practical examples in the documentation would be a significant benefit. I am concerned about the LTS that Hasura has for the Community version until January 2027, which is a pain point for us and makes us reconsider the project's architecture.
Senior Data Engineer at a energy/utilities company with 1,001-5,000 employees
Real User
Top 20
May 20, 2026
Regarding limitations, we were using the free version, and perhaps the paid version offers more features. The free version had limitations that made me wish for the paid version. Additionally, GraphQL can be slow and has limitations compared to SQL; extremely complex SQL queries are not possible directly in GraphQL, requiring dependence on sources such as Postgres for complex queries. Hasura could improve by allowing us to build complex queries within it instead of depending on source databases, which might affect response speed. However, I understand why it is structured this way.
Full Stack Developer at a tech services company with 11-50 employees
Real User
Top 20
May 19, 2026
Regarding needed improvements, the complex business logic, nested joins, and over-fetching need to be addressed. Additionally, Hasura needs query limits, caching, monitoring, and better handling of database coupling.
I would recommend that more easy-to-integrate database connectivities can be added, such as NeonDB which was particularly easy to integrate with, but at that time MongoDB had some overhead that was required. I would recommend that and also the authentication part, particularly not RBAC, but I am talking about the authentication; if they were native to Hasura, then I would say that it would be great for that. The documentation can always be made better by adding some real business cases that users can go through at a glance, so they can start using Hasura as fast as possible and can deliver something that users can use as fast as possible. The UI was pretty good. I believe that I chose a seven out of ten because I think the UI can be made better and the navigation could have been better. Currently, I do not complain about that, but it could have been made better.
Hasura could be improved by enhancing the performance of the free tier version, particularly for small applications that can only accommodate around 500 MB. In my scenario, that would have made a noticeable difference.
Business Analyst at a healthcare company with 201-500 employees
Real User
Top 10
May 16, 2026
I'm still using it, so I'm unsure how Hasura can be improved. Perhaps its framework and structure-wise aspects could be enhanced. I feel it's good overall.Regarding needed improvements, many developers feel that the complex workflow and validations can be difficult to manage at scale, and debugging access issues are a little confusing. These aspects could be fixed.
DevOps Engineer at a tech services company with 51-200 employees
Real User
Top 20
May 15, 2026
I have faced some pain points regarding the migration process. Regarding needed improvements about migration, if a company has a single development server and multiple production servers, this segregation can be done at the database level or at the level of tables migration. This could be improved. Regarding my main use case with Hasura, the graphical user interface, GUI, the web interface that is offered is particularly very slow if you have a lot of endpoints configured. It is better to use CLI, which is the preferred method for me. All the endpoints are very fast and responsive, as Hasura servers are very fast. The setup does not take a lot of time as it is just one metadata file, and we can recover all of the set endpoints, making backing up and storing everything very easy. I would like to add that the user interface is particularly very slow and sometimes overwhelmingly slow. This is not about the response of the endpoints, but rather the user interface itself.
Software engineer at a consultancy with 201-500 employees
Real User
Top 5
May 15, 2026
Hasura can be improved in a way such that the setup process could be improved, and the loggings and Hasura logs could be improved. Apart from that, there are some restrictions while defining actions or while using GraphQL. We cannot do certain particular queries while writing GraphQL which we can easily do in SQL while writing a Node API. Those things can be improved in Hasura.There is always a scope for improvement.
Hasura is a GraphQL engine that automates the creation of APIs, providing developers with a real-time data source integration. It streamlines backend development and accelerates the time-to-market for applications by enabling instant GraphQL API generation from existing databases.Hasura empowers developers with its ability to automatically generate GraphQL APIs from databases, offering a solution for quickly developing applications that require real-time capabilities. It allows seamless...
One area where Hasura can improve is handling complex business logic, and for observability and debugging, improvement is needed. Hasura can improve around complex workflow support and managing large-scale permissions. A few things come to mind regarding documentation. Documentation is generally good, but for advanced production scenarios and architecture patterns, more real-world examples would help. Smoother integration and observability with monitoring and tracing tools would make troubleshooting easier. One improvement I would like is better support for large-scale schemas, and for complex logic. For complex transactional workloads, we still keep business logic in back-end services, so Hasura needs to become more efficient for heavy workloads.
Hasura could improve with better documentation because I have not always known where to look for certain issues I have encountered. The CLI commands could provide better feedback when something fails. Practical examples in the documentation would be a significant benefit. I am concerned about the LTS that Hasura has for the Community version until January 2027, which is a pain point for us and makes us reconsider the project's architecture.
Regarding limitations, we were using the free version, and perhaps the paid version offers more features. The free version had limitations that made me wish for the paid version. Additionally, GraphQL can be slow and has limitations compared to SQL; extremely complex SQL queries are not possible directly in GraphQL, requiring dependence on sources such as Postgres for complex queries. Hasura could improve by allowing us to build complex queries within it instead of depending on source databases, which might affect response speed. However, I understand why it is structured this way.
Regarding needed improvements, the complex business logic, nested joins, and over-fetching need to be addressed. Additionally, Hasura needs query limits, caching, monitoring, and better handling of database coupling.
I would recommend that more easy-to-integrate database connectivities can be added, such as NeonDB which was particularly easy to integrate with, but at that time MongoDB had some overhead that was required. I would recommend that and also the authentication part, particularly not RBAC, but I am talking about the authentication; if they were native to Hasura, then I would say that it would be great for that. The documentation can always be made better by adding some real business cases that users can go through at a glance, so they can start using Hasura as fast as possible and can deliver something that users can use as fast as possible. The UI was pretty good. I believe that I chose a seven out of ten because I think the UI can be made better and the navigation could have been better. Currently, I do not complain about that, but it could have been made better.
Hasura could be improved by enhancing the performance of the free tier version, particularly for small applications that can only accommodate around 500 MB. In my scenario, that would have made a noticeable difference.
I'm still using it, so I'm unsure how Hasura can be improved. Perhaps its framework and structure-wise aspects could be enhanced. I feel it's good overall.Regarding needed improvements, many developers feel that the complex workflow and validations can be difficult to manage at scale, and debugging access issues are a little confusing. These aspects could be fixed.
I have faced some pain points regarding the migration process. Regarding needed improvements about migration, if a company has a single development server and multiple production servers, this segregation can be done at the database level or at the level of tables migration. This could be improved. Regarding my main use case with Hasura, the graphical user interface, GUI, the web interface that is offered is particularly very slow if you have a lot of endpoints configured. It is better to use CLI, which is the preferred method for me. All the endpoints are very fast and responsive, as Hasura servers are very fast. The setup does not take a lot of time as it is just one metadata file, and we can recover all of the set endpoints, making backing up and storing everything very easy. I would like to add that the user interface is particularly very slow and sometimes overwhelmingly slow. This is not about the response of the endpoints, but rather the user interface itself.
Hasura can be improved in a way such that the setup process could be improved, and the loggings and Hasura logs could be improved. Apart from that, there are some restrictions while defining actions or while using GraphQL. We cannot do certain particular queries while writing GraphQL which we can easily do in SQL while writing a Node API. Those things can be improved in Hasura.There is always a scope for improvement.
One area I would like to see improved is that they are providing a cloud-based DB system, and aside from that, I don't have any additional requests.