Is Hasura v3 / DDN OSS?

[mirzap]

New documentation is confusing and is 100% SaaS focused. I can't figure out is Hasura (v3/DDN) still free to self host? If it is, is there any documentation how to do it?

[rakeshkky]

Hi @mirzap, the Hasura DDN API engine is already open-sourced and available in the graphql-engine repo here.

[mirzap]

I tried running docker-compose in the v3 folder. I get two containers running, but there is no Hasura UI, and I have no idea how to start. I’ve been working with Hasura since v1, and this is quite disappointing.

If I get this right, is there no more UI interface for building tables, APIs, etc?

I’ve long avoided Supabase because I like Hasura; it is a great product. But now I’m considering switching completely. They improve and deliver constantly, while hasura has been stagnating for some time now.

[hgiasac]

If I get this right, is there no more UI interface for building tables, APIs, etc?

@mirzap you are correct. The long-term goal of Hasura v3 is to support many databases. Each database has a different API spec so we no longer take much effort for database migrations. If you only need to connect Hasura with PostgreSQL Hasura v2 is still very good to be used.

I recommend you download the DDN CLI to create the boilerplate and follow the guide in the Hasura v3 docs. The DX of OSS and cloud are the same. If you don't want to deploy the project to the Hasura cloud you can build the metadata locally and run the stack with docker-compose or Kubernetes.

https://hasura.io/docs/3.0/getting-started/quickstart (You can stop at step 7 and browse http://localhost:3000 to run the Graphiql playground)

For metadata development, we maintain the CLI, Language Server Protocol, and VSCode IDE so developers can develop metadata directly in the editor. The downside of web UI development in v2 is that the performance is slow if the metadata is big. The IDE will be more lightweight to run.

Or you can use Hasura v2 as a migration tool to create database migrations and develop metadata in v3. It's a bit tricky but still works well.

[fungiboletus]

I couldn't find the source code of the DDN CLI. Is it open-source or proprietary?

I tried to find the source code of the Language Server Protocol and it seems to be located in this repository: https://github.com/hasura/hasura-lsp-server according to the VSCode plugin metadata. But this is not public, is it open-source or proprietary?

I'm realising that Hasura v3 may require the use of non open-source components. I understand that living well from open-source software is challenging, I don't have a good solution. But I personally have a policy that consists of not relying on proprietary software.

So long, and thanks for all the fish.

[hgiasac]

@fungiboletus Currently, the DDN CLI, Web console, and LSP are proprietary. The following components are open source with Apache license:

• Engine v3.
• Data Connectors.

Most DDN CLI, Web console, and LSP features are for dev tools and the DDN cloud. They won't lock you to run self-hosted environments in production. Therefore you can use Hasura v3 without worrying about the license.

[fungiboletus]

Thanks for the clarification. I understand that I can self host the engine, but I don't like to rely on development tools that cannot be distributed, tweaked, fixed, or replaced.

I also think that having those necessary tools under a proprietary license makes the open-source part of the platform a lot less attractive to open-source contributions, but I may be wrong. I also don't know how much open-source contributions you got anyway.