Hasura Cloud Enterprise

My main use case for Hasura  is a web application. In that web application, I use Hasura  for managing data.

We use Hasura because it's a quick way to prototype, and the GraphQL API is a plus that we really weren't accustomed to using, but that works well for us given our business logic.

The best features that Hasura offers are fast prototyping, meaning that with a Docker  Compose and five minutes, I already have an instance and an API up and running, alongside Hasura's migration tools, with the Docker  container and so on.

There's one feature I've just started to try now, which is Hasura Actions, that may not quite fit our project perfectly, but I find them super powerful.

Hasura has had a positive impact on my organization, as in a team that was one and a half people a year ago, I can prototype and start having an available API to query things in ten minutes.

I think Hasura could improve by making the documentation better, as many times I've found myself not knowing where to look up certain problems I've run into, and I believe the CLI commands could provide better feedback when something fails. Practical examples would be a big plus.

I have been using Hasura for one year.

Hasura's stability is such that in the dev environment on our local machines, some queries can take up to eight, nine, ten seconds to respond, which I don't really understand why, but in the deployed environment, there's no problem.

I have not experienced Hasura's scalability yet, as we're not at that phase of the project.

I have not had experience with Hasura's customer support, as that hasn't occurred.

I have not used any different solution before Hasura.

Before choosing Hasura, I did not evaluate other options; it was a recommendation because there were other projects within the same company that used it, so we needed a way to get started quickly, and Hasura provided exactly that.

I would advise other people considering using Hasura to have version control over their migrations, because we don't have it, which I know goes against what Hasura proposes, and it's a pain. Updating anything related to metadata or migrations or the databases, or rather the Postgres tables, is a pain because I have to tear everything down and bring it back up and a lot of time is lost, so I'd say that it's important to be able to version that folder, and also that custom SQL functions in Postgres are very useful for us because we came from a migration and needed to access data referenced in other tables; those functions have worked very well for us.

I'm a bit worried about the LTS that Hasura has, the Community version, until January 2027, which is a very big pain point for us and makes us rethink the project's architecture a bit.

As an end-user of Hasura , we are using it within our projects. Our usual use cases for Hasura  involve using it as an authorizer; instead of writing our own GraphQL schemas, we use Hasura, which is 10x faster, and we don't need to write as much logic ourselves. Hasura is a GraphQL engine tool that generates schemas automatically to connect with the database, so we do not need to manually write the schemas and APIs. We can directly integrate through our application, making the developer's job easier. Additionally, it connects very fast, with APIs being 10x faster compared to normal APIs.

The features I appreciate most about Hasura include the ability to connect to any database; we are using PostgreSQL , and it automatically generates schemas once connected to the tables. Hasura reads the tables and creates the schemas itself, eliminating the need for users to write their own schemas. Furthermore, it allows for authentication in multiple ways, such as Webhooks and JWT tokens, providing role-based authentication for data, which is a significant feature for us.

We do use Hasura's real-time subscriptions, and they have a substantial impact on our application's interactivity because, with subscriptions, there is no need to refresh the app whenever data changes. Hasura's subscription feature automatically updates data, making it very important for our workflow. All features provided by GraphQL are provided by Hasura, including subscriptions, mutations, and queries.

Hasura's granular data access control helps in securing sensitive information by implementing role-based authentication. For instance, if a user is set up with their username or user ID and email, they only have access to their data and nothing else, unless they are an admin or receive other specific permissions.

Currently, I cannot suggest improvements for Hasura, as it is evolving nicely, and they are releasing the latest versions. I have not encountered any bottleneck problems according to my business logic, and I find the UI and console to be very good, so I have not experienced any issues.

I have been working with Hasura for a considerable time.

Regarding stability and reliability, I find them to be very good since we have been using Hasura for the past three years without any downtime. I would rate stability between 8.5 to 9. It works very smoothly.

Hasura's scalability depends on how we configure it on-premises; we are using 10 servers according to our business logic and throughput needs. Despite high connection loads, Hasura manages well, and our servers may go down, but Hasura never fails and reconnects quickly. I can confidently say they manage scalability very effectively.

I have not had the need to communicate with Hasura's technical support yet.

Before using Hasura, we were utilizing our own custom APIs and schemas for the same use cases, without any other tools.

I did not evaluate other options before choosing Hasura because when I joined this company, they had already introduced Hasura. I am not sure if they did any research on alternatives, but I can confirm that I did not.

To evaluate the effectiveness of Hasura's event triggers, I use metrics such as the time taken for API calls, which we check using Postman, measuring in milliseconds.

I can only assess Hasura's value in integrating with microservices architectures from our experience, as we are only connecting one microservice with one PostgreSQL  database. I cannot speak to how it performs with multiple microservices; however, it integrates very effectively with the database, and the process is straightforward.

The most significant benefit I have seen with Hasura is that it makes the developer's job much easier by eliminating the need to write custom APIs and schemas. It is 10x faster because they maintain some internal cache mechanisms efficiently.

I have used Hasura's official documentation, which is well-provided. If you are a skilled engineer, you can comprehend it effectively, but you need to know the jargon. I would give the documentation a rating of 7 because if someone is not that skilled, they may struggle to understand it without prior knowledge.

I would rate this review an overall 8.

Hasura  was my main tool and platform for exposing all of our APIs for our insights page. Everything on our insights webpage was our analytics products from Atency, and that is where we were using Hasura  for data access control, having security classes, and controlling the data via APIs.

In general, everything related to APIs was via Hasura in my previous company. We had our webpage with reports via Power BI, but for all our API-related components, it was everything via Hasura.

Hasura offers quite user-friendly features. It is easy to adapt, especially since it is GraphQL, which is similar to SQL. It provides a nice interface to build different APIs, and one feature I really appreciated was access control. For example, we had many customers with one single table of data, but data access control prevented one customer from seeing another customer's data.

Access control was vital for our product-based company with more than 100 customers to prevent data breaches and leaks, which are security issues tied to customer trust. To maintain everything and the trust of our customers, it was crucial to have good data access control. Via this API access control, it was easy; we just added company-level access control to Hasura, filtering based on different customers, ensuring each customer received only their data.

Hasura positively impacted our organization through useful access control, allowing us to directly obtain data without extra layers of access control processes, which increased efficiency and speed.

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.

I have been working in my current field for eight to nine years.

I started with the company while Hasura was already in use, so I did not experience a replacement scenario but began using it as a new solution.

My experience while working with it was quite satisfactory.

For others considering Hasura, its effectiveness varies depending on the company size and data amount. For medium-scale or startup companies, it is an excellent option since it is free, but it may not handle immense data for huge companies. I would rate Hasura as a seven out of ten based on my experience because it has some limitations, and I would have preferred more features, such as building complex queries, which are not possible in Hasura.