Nhost OSS is an open-source GraphQL backend replacing Firebase and Nhost Pro with PostgreSQL, Hasura, auth, and S3 storage on Docker.
Nhost combines PostgreSQL, the Hasura GraphQL Engine, a dedicated authentication service, and S3-compatible file storage into an integrated container stack. Teams deploy the backend locally through the Nhost CLI or run it on their own servers to generate instant GraphQL APIs over relational tables. The platform replicates Firebase backend capabilities through open relational standards, avoiding vendor lock-in while preserving data sovereignty.
Nhost OSS provides the same core development surface as Nhost Pro by running identical backend services across local and remote environments. Developers interacting with the local stack get the exact Hasura GraphQL engine, PostgreSQL relational database, authentication endpoints, and storage APIs that power the managed cloud platform. Frontend clients built with the Nhost JavaScript SDK, React hooks, or Flutter packages communicate with local containers using the same query syntax and authentication tokens as a hosted cluster. This consistency allows engineering teams to validate schema migrations, Hasura permissions, and serverless functions offline before pushing code.
The operational workflow diverges around infrastructure maintenance and automated platform tooling. Nhost Pro handles database provisioning, daily automated snapshots, point-in-time recovery, managed Grafana telemetry, and automated preview environments. Self-hosting Nhost OSS replaces those cloud conveniences with standard container orchestration. DevOps engineers retain full control over data residency, networking perimeters, and resource allocations, eliminating cloud seat charges and egress tiers. In exchange, the team manages container uptime, PostgreSQL replication, reverse proxy configuration, and custom backup routines. Compared to proprietary GraphQL backends like 8base, Nhost OSS avoids closed schema models and keeps application logic rooted in standard SQL tables.
Is Nhost OSS free for commercial use? Yes. Nhost OSS carries the MIT license, permitting organizations to self-host, modify, and run the backend stack for commercial products without software subscription fees.
Nhost OSS vs Nhost Pro — which should a development team choose? Nhost Pro is suited for teams that prioritize managed infrastructure, automated point-in-time recovery, and zero server maintenance, whereas Nhost OSS fits teams with container operations expertise who need complete infrastructure ownership.
Can Nhost OSS run in production on a single virtual server? Yes. A standard Linux server with four gigabytes of memory can run the full container stack for small to medium production workloads.
Nhost OSS provides an effective backend foundation for teams that want GraphQL agility and PostgreSQL reliability without committing to proprietary cloud runtimes. Active development with ongoing commits in 2026 and an unarchived repository carrying the MIT license ensure long-term stability for organizations prepared to manage their own container infrastructure and database backups.
Lint, codegen, breaking-change checks and dependency management in one Git-native CLI. Open source, no registry lock-in.
Show that Nhost OSS is listed as an open-source alternative. Paste into your README: