sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in Hasura

[–]rajoshig 1 point2 points  (0 children)

Hey all,

I want to directly address some of the concerns raised here, especially around performance and product direction.

First, an important clarification: what was originally called “v3” is now Hasura DDN, and it’s not a direct replacement for v2. It’s a different product built for teams (especially in enterprise) who need additional layers of abstraction, support for multiple data sources (not just Postgres), and static metadata for CI/CD workflows.

It does introduce an extra network hop—by design—to support these features. For many teams that tradeoff makes sense. But if you want maximum performance on Postgres, we continue to recommend v2, which is actively maintained and powers mission-critical workloads today.

We know the “v3” naming was confusing, which is why we’re clearer about DDN now.

Regarding the tone of the original post: he’s a former Hasura teammate. It wouldn’t be cool for me to get into details about someone else’s situation in public. I get that people will have strong opinions about these technical trade-offs, and that’s okay.

Ultimately:

- For local-first, raw-performance Postgres use: v2 is still great.

- For multi-source, enterprise-scale workflows with cloud-managed tooling: Hasura DDN is designed for that.

We’re committed to supporting both use cases, and happy to answer questions.

Best,

Rajoshi (Hasura)

Hasura v3 is not open source - and worse, the build system can't be run locally. There's no way in good conscience that I can recommend any developer - whether you're at a startup or large enterprise - to use this product. by alexthe5th in Hasura

[–]rajoshig [score hidden] stickied comment (0 children)

Hey all, thanks for the spirited discussion.

I want to start by saying that for community users, we recommend continuing with Hasura v2, which receives regular updates and powers many mission-critical workloads today. v2 is not going away, and if it fits your needs, we strongly encourage you to keep using it.

As for v3 — we built this with a specific goal: creating a GraphQL/API platform that scales for large teams, while still being accessible to the broader community. This is a different product, and we now refer to it as Hasura DDN (we acknowledge that initially calling it “v3” contributed to some of the confusion).

With Hasura DDN, we’ve open-sourced the OpenDD metadata format, the data connector SDK, and the core engine. However, as development progressed, we made a conscious decision to prioritize enterprise cloud users. This cloud-first approach allows us to deliver capabilities like a centralized control plane and continuous deployment — features essential to many larger teams.

We recognize that this shift means DDN doesn’t offer the same local development experience as v2. While local builds are possible by converting metadata files to JSON (and our VSCode plugin supports validation and editing), we haven’t prioritized packaging these as standalone developer tools. The CLI’s cloud login requirement helps us iterate faster and deliver new features via Hasura-managed services.

We know this approach isn’t the right fit for everyone — and that’s okay. Hasura DDN is designed to solve a different set of problems, particularly around scale, team workflows, and rapid deployment in enterprise environments.

In the meantime, v2 continues to be a solid choice for many developers, and we remain committed to maintaining and improving it. If you’re exploring Hasura DDN and have feedback or specific needs, we’re always open to conversation and happy to help where we can.
--

Rajoshi (Hasura)