Technical Limitations and Community Barriers in the Use of Nhost.io in Self-Hosted Environments

Author: Roberto, Carlos PhD. Abstract This article critically analyzes the Nhost.io platform, a backend-as-a-service (BaaS) tool based on Hasura and PostgreSQL, focusing on its claimed ability to be deployed in self-hosted environments. The research reveals that, despite the existence of public repositories and docker-compose.yaml files for local installation, the tool presents significant technical and social obstacles to full execution outside the environment controlled by Nhost Inc. 1. Introduction The concept of Backend-as-a-Service (BaaS) has evolved significantly with the emergence of platforms such as Firebase, Supabase, and Nhost.io. These tools promise to accelerate application development by offering authentication, real-time databases, storage, and integrated serverless functions. Among them, Nhost.io stands out for offering a modern stack based on GraphQL and Hasura, with the promise of being open-source and self-hosted. 2. Methodology The analysis was conducted based on: studies of public repositories of the Nhost organization; tests of the docker-compose.yaml provided for local environments; interactions with Nhost community members in public forums such as GitHub Issues and Discord; and official and unofficial documentation for installation on VPS servers. 3. Technical Structure and Diagnosis The docker-compose.yaml includes services such as nhost-auth, nhost-storage, nhost-functions, nhost-graphql, nhost-mailhog, nhost-dashboard, PostgreSQL, and Hasura. The environment only works in localhost due to limitations with CORS, internal variables, and dependency on verified domains. On VPS deployments, failures occur due to lack of support for automated TLS, OAuth provider integration, and the CLI being restricted to cloud usage. 4. Ethical and Community Implications User reports indicate blocks in official Discord and GitHub channels after raising questions about these limitations. The CTO, David Barroso (GitHub user dbarrosop), has been cited as responsible for sanctions against users who point out the truth about the non-functional nature of the self-hosted version of Nhost. 5. Discussion Nhost.io is open-source in terms of code, but not in terms of infrastructure. The behavior of the technical team violates principles of openness and collaboration, creating a toxic and centralized environment. Other solutions such as Supabase offer more transparent support for independent hosting. 6. Conclusion The promise of a functional self-hosted Nhost instance does not hold up in practice. The tool only works properly in localhost mode and imposes various technical and community barriers. Alternatives with true independent deployment support are recommended. References Nhost GitHub Repository: https://github.com/nhost/examples/docker-compose Official Nhost Documentation: https://docs.nhost.io Community reports on Discord and GitHub Issues (Feb-May/2025) Technical analysis of docker-compose.yaml containers. Supabase Self-Hosting Guide, 2024.

May 9, 2025 - 20:37
 0
Technical Limitations and Community Barriers in the Use of Nhost.io in Self-Hosted Environments

Author: Roberto, Carlos PhD.

Abstract
This article critically analyzes the Nhost.io platform, a backend-as-a-service (BaaS) tool based on Hasura and PostgreSQL, focusing on its claimed ability to be deployed in self-hosted environments. The research reveals that, despite the existence of public repositories and docker-compose.yaml files for local installation, the tool presents significant technical and social obstacles to full execution outside the environment controlled by Nhost Inc.

1. Introduction
The concept of Backend-as-a-Service (BaaS) has evolved significantly with the emergence of platforms such as Firebase, Supabase, and Nhost.io. These tools promise to accelerate application development by offering authentication, real-time databases, storage, and integrated serverless functions. Among them, Nhost.io stands out for offering a modern stack based on GraphQL and Hasura, with the promise of being open-source and self-hosted.

2. Methodology
The analysis was conducted based on: studies of public repositories of the Nhost organization; tests of the docker-compose.yaml provided for local environments; interactions with Nhost community members in public forums such as GitHub Issues and Discord; and official and unofficial documentation for installation on VPS servers.

3. Technical Structure and Diagnosis
The docker-compose.yaml includes services such as nhost-auth, nhost-storage, nhost-functions, nhost-graphql, nhost-mailhog, nhost-dashboard, PostgreSQL, and Hasura. The environment only works in localhost due to limitations with CORS, internal variables, and dependency on verified domains. On VPS deployments, failures occur due to lack of support for automated TLS, OAuth provider integration, and the CLI being restricted to cloud usage.

4. Ethical and Community Implications
User reports indicate blocks in official Discord and GitHub channels after raising questions about these limitations. The CTO, David Barroso (GitHub user dbarrosop), has been cited as responsible for sanctions against users who point out the truth about the non-functional nature of the self-hosted version of Nhost.

5. Discussion
Nhost.io is open-source in terms of code, but not in terms of infrastructure. The behavior of the technical team violates principles of openness and collaboration, creating a toxic and centralized environment. Other solutions such as Supabase offer more transparent support for independent hosting.

6. Conclusion
The promise of a functional self-hosted Nhost instance does not hold up in practice. The tool only works properly in localhost mode and imposes various technical and community barriers. Alternatives with true independent deployment support are recommended.

References

  1. Nhost GitHub Repository: https://github.com/nhost/examples/docker-compose
  2. Official Nhost Documentation: https://docs.nhost.io
  3. Community reports on Discord and GitHub Issues (Feb-May/2025)
  4. Technical analysis of docker-compose.yaml containers.
  5. Supabase Self-Hosting Guide, 2024.