Hasura Reviews

My main use case for Hasura is performing database testing. I use Hasura for database testing to find out the query, to determine how many authorizations are there or how many letters are there, and we are matching the same with our application.

Hasura has positively impacted my organization by helping to maintain larger data. I can share specific outcomes that show how Hasura has improved performance and saved time.

The best features Hasura offers include querying, querying on large sets of data, and simplifying the query in a structured way that a layman can also understand the query properly while holding the data in a larger database.

Out of those features, I find myself relying on querying on large data sets the most because our application is very large and has enormous data; Hasura literally helps us to find unique data quickly.

I do not wish to add more about the needed improvements, nor is there anything specific I wish Hasura did better.

I have been using Hasura for one year.

Hasura is stable.

Hasura's scalability is good.

Hasura's customer support is very good. On a scale of 1 to 10, I rate the customer support an eight.

I previously used SQL, but we switched to Hasura because it is really helpful to maintain larger data.

I have seen a return on investment in the form of time saved.

Before choosing Hasura, I evaluated other options, specifically SQL.

Regarding Hasura's AI capabilities, I think the governance and security for the credentials we store for Hasura login are at risk, so that data can be stolen easily.

Regarding Hasura's AI capabilities, I think its accuracy and reliability of output are a bit risky because it might impact the security of data and data leakage can happen also.

My advice for others looking into using Hasura is that it is really the best database to use, so please go ahead and use it.

Public Cloud

I used Hasura for the GraphQL APIs it provided and for RBAC, which would have otherwise taken a lot of time to implement manually and perfectly.

The project I was building was meant to power both mobile applications and web applications, and GraphQL APIs are particularly suited for mobile-based applications. The RBAC is role-based access control, and there was a particular role hierarchy that the client wanted which I implemented using RBAC.

When I used NeonDB, it was particularly easy to integrate with Hasura and the flexibility was great because we could extend it.

The best features Hasura offers, in my opinion, are the production-ready GraphQL features.

The auto generation of APIs was great, and I liked that we could add our own custom requirements as well, so we were not restricted to the standard but could also enhance the API with our custom requirements.

Integrations were fairly easier, and I used the X-Hasura-Claims, and it was not very difficult to figure out. It was pretty easy.

Hasura greatly reduced the time to deliver and also definitely increased the productivity as a result.

I would say that it almost saved around fifty percent of the time because almost half of the time we spent on building that perfect API, and Hasura gave that out of the box.

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.

I have used Hasura for about four months.

I would give the advice that if others are looking to build something fast and want to avoid the overhead of writing boilerplate APIs and implementing RBAC, they can definitely go for Hasura because it saves a lot of time. I give this product a review rating of seven out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

I have used MongoDB and MySQL, and for the last two years, I am using CockroachDB, which is better than these two. I have recommended it to two more of my colleagues who have also started working on CockroachDB, and they are building an application for the global market. They have started using CockroachDB because it has been very helpful.

I am using Hasura just for the GQL, GraphQL.

Hasura has connectivity with CockroachDB, and I am not directly calling CockroachDB, I am just calling Hasura. Internally, Hasura calls CockroachDB, gets the data, and populates it into our application. It serves as middleware.

We have real-time subscription in Hasura.

If I change anything in CockroachDB, it immediately impacts Hasura. For example, if I add new fields, it gets reflected in Hasura.

Integrating microservice architecture with Hasura provides an endpoint to incorporate into your microservices. It works as a connection string, and that's its main role.

Hasura's best feature is that it provides an API gateway, and it also provides remote schemas and monitoring, which are the best methods they are offering.

In the API playground, I can run my query dynamically; it has a GraphiQL integrated system. I can fix my error directly on this playground and then copy my query from it to my code.

Regarding security, Hasura provides API keys and secret keys. It is hosted there and offers these features, which are very good. I have role-based access; I can give four out of five team members access to the Hasura console and manage their access control according to their roles. If assigned as admin, they can do anything. Developers can run queries, and business developers can monitor metrics.

Hasura does not support custom business logic; it just provides Graph Query Language support to get the data. It offers an endpoint where I can fetch the data and create any endpoint, such as ABC, to get a desired output based on some input variables.

Hasura has event triggers, and I have used that feature. I find it effective to have these event triggers in my system.

The main benefits I see from using Hasura include being able to fix my queries on the playground in real-time rather than relying on Google or any AI solutions for error resolution.

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.

I have been working with Hasura for the last six months only.

I have no issues with stability or scalability; everything is good.

I have no issues with stability or scalability; everything is good.

The tech support was fine; they used to reply within one, two, or three days, and that is acceptable.

Positive

Before Hasura, we did not have a chance to work on CockroachDB. We used DynamoDB, DocumentDB, and MongoDB from the AWS platform.

The initial setup of Hasura was very easy. Once redirected to the dashboard, I can add a new project by clicking a button for a new project. It asks if I want to go with a free plan or a professional plan, and if I select the free plan, I provide a provider such as Google Cloud, Azure, or AWS. Based on this, I can create a new project and add my DB connection string, such as CockroachDB. Just put it in and click save to create the connection, after which I can launch the console.

My advice for others considering Hasura is that sometimes it may not support capturing remote schemas effectively; for example, if I change something in CockroachDB, it sometimes fails to capture the change until one or two days later. I discussed this with the sales and technical teams, and they also recognized this issue. This can impact your business deadlines if it's not functioning properly.

Event triggers are required for situations such as creating backups every three or four days. For example, if I need to create an event that runs every three days for backups or integrates payment systems using webhooks such as Stripe, once Stripe updates the database, that data will be updated in my local database.

On a scale of one to ten, I rate Hasura a six out of ten.

Public Cloud

Google

My main use case for Hasura is building my ideas. For instance, back in Turkey, I was trying to create a QR menu application and with my friends, we utilized Hasura.

I haven't been using Hasura at my organization; it's more personal. For my personal projects, I cannot think of a specific example at the moment about how Hasura has made things easier or more efficient for me.

In my opinion, the best features Hasura offers are row-level access policies on top of the database, so I don't have to create my own APIs, allowing me to quickly spin up ideas easily. Those row-level access policies help me a lot because I didn't have to think about writing a specific API on top of my database.

I believe there could be other tools included nearby Hasura, so it's easily extended with other cloud applications and cloud offerings. For instance, I could connect my S3 bucket and utilize all those access policies that my users have.

I have transitioned to Supabase recently, so it's more of an all-in-one solution than Hasura. I would rate Hasura an eight out of ten because it's not perfect and there are cases where I would use a competitor like Supabase.

I have been working in my current field for more than seven years.

I test ideas quickly on the public cloud that is free, which could give me a free tier of usage, such as Neon databases. I use Neon databases for testing ideas on the public cloud because that's free.

I have no idea regarding Hasura's AI capabilities and would be interested to hear details about that.

I haven't used those features regarding Hasura's AI capabilities, so I cannot provide any opinion on the accuracy and reliability of output.

I found this interview a bit challenging because you sometimes didn't listen to me, cutting me off at times, and it doesn't feel natural. I would give this review an overall rating of eight out of ten.

Public Cloud

Other

My main use case for Hasura is to write GraphQL queries that I use in the implementation of APIs on the front end.

I implemented a feature called OKR, Objectives and Key Results, and I used Hasura to write all the GraphQL queries, which have been very helpful for me. Without any back-end developer's help, I can create my own APIs with a limited version of key and data values.

As a front-end engineer with limited knowledge in the back end, since I started using Hasura, I have no dependency on back-end developers, so I don't need to wait for them to create APIs. I can create my own GraphQL queries, which are very simple, or mutations, and I use subscriptions for real-time data retrieval, which is very helpful for me.

The best features Hasura offers include a simple UI that anybody can understand, and that is very helpful.

I appreciate the layout of the UI and the way queries are created; the product development of Hasura is very easy to understand.

Hasura has positively impacted my organization, as the majority of the APIs were integrated through GraphQL, and most of the time we are using Hasura.

It saves the team time; I'm not sure about the cost. Since I'm a front-end developer with limited knowledge in the back end, I can easily get the queries directly from the database, making it a win-win for both the team and time.

Hasura can be improved through the subscription part, as the web socket is a little bit slow compared to other web sockets in the market.

I have used Hasura for around like three to four years.

Hasura is stable.

Hasura's scalability is good; I'm not aware of other tools, so I cannot clearly answer this question.

I have only used Hasura and did not previously use a different solution.

I don't have authority to purchase Hasura, so I have no idea about the pricing, setup cost, and licensing.

I did not evaluate any other options before choosing Hasura, as my organization was currently using Hasura, so I continued to use it.

I suggest to beginners looking into using Hasura who want to learn the back end, or for simple applications that want to build APIs, that instead of going for a REST API, I suggest GraphQL through Hasura. That will be easy to understand, easy to implement, and it's very beginner-friendly for small applications. I gave this product a rating of eight out of ten.

Private Cloud

Amazon Web Services (AWS)

My main use case for Hasura involves dealing with multiple source systems, where we had to create a bunch of repetitive backend work, leading to many APIs that needed to be built. Hasura made development easier because it was useful without wasting time building basic APIs over and over again; instead of creating the controller, service, repository, and DTOs manually, along with filtering and sorting, Hasura has made the work straightforward.

A quick specific example of a project where Hasura helped me save time is our auto-renewal system, which we built in a recent renewal job. Without Hasura, after processing, a backend would need to expose an API endpoint such as /renewals, requiring us to manually build the DTOs, maintain multiple endpoints, support frontend changes, and handle real-time updates separately using WebSockets. With Hasura, the work became straightforward; the .NET jobs update the database, and it automatically exposes the updated data with no need for backend changes, also aiding in the real-time dashboard updates.

The feature that had the most impact on my work was real-time data combined with eliminating the backend API development; that combination greatly sped up building the systems. This mattered most because our system needs to process tasks such as renewal processing, background jobs, and orchestration workflows. Using the AG Grid table was particularly useful, as we have to show renewals that are pending, processing, completed, or failed. Without Hasura, we would have had to create several REST endpoints, polling APIs, and manage WebSockets, along with manual filtering APIs. Hasura has changed our approach by handling API generation, GraphQL queries, subscriptions, and filtering, allowing the frontend to no longer wait for backend APIs to make changes.

Hasura reduced backend boilerplate and enabled real-time operational dashboards by automatically exposing database changes through GraphQL subscriptions, allowing our services to focus only on business processing while Hasura handled API generation and live data.

In my opinion, the best features Hasura offers are the auto-generated GraphQL APIs, as it has auto-generated GraphQL APIs and instantly provides queries, mutations, and real-time subscriptions. The frontend can fetch whatever data it needs, instead of fetching huge payloads. Since we used AG Grid for showing huge datasets in a table, the filtering and querying capabilities were very powerful, and the role-based security implementation with Hasura is also commendable.

Hasura positively impacted my organization by facilitating fast development; we saved a lot of time in development. I can estimate that we saved significant time; we do not need to manually create all the GraphQL queries or API generations. I can say we could build an API within hours instead of taking days.

The time saved reflects a significant return on investment.

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 have been using Hasura for three years.

In my experience, Hasura is stable.

Hasura's scalability is good, but it heavily depends on proper design; while Hasura can scale horizontally, scalability mostly relies on database design, caching, and subscription management.

I have not reached out to customer support, and we have not faced that many issues.

I did not previously use a different solution with this company.

Before choosing Hasura, we evaluated other options; we traditionally used REST APIs by building backend services in ASP.NET Web API, along with using Node.js, Express, and Java Spring Boot. The old approach created too much boilerplate, requiring a controller, service, repository, and mapping validations for every table and making our frontend heavily dependent on the backend.

My advice to others looking into using Hasura is that if they have an automated system such as auto-renewal, or multiple source systems to deal with while using GraphQL, then I would suggest going with Hasura. I rate this product a 9.

On-premises

Microsoft Azure