Nhost is not acting like a sleepy Firebase alternative. ToolVitals sees 23 release events in 30 days, 30 GitHub releases in 90 days, a 100 shipping score, and a 98 ToolVitals score. For a 9,169 star backend platform, that is a loud maintenance signal.
The interesting part is where the release work is landing. Recent first-party releases cluster around Constellation, the CLI, and the dashboard. That points to Nhost tightening the parts developers touch when they model data, expose GraphQL, manage projects, and run the stack locally.
Nhost positions itself as a complete backend stack: SQL database, real-time API, authentication, storage, serverless functions, services in any language, and AI features such as auto-embeddings and assistants. The GitHub repo keeps the simpler pitch: an open-source Firebase alternative with GraphQL. ToolVitals classifies it as OSI-approved OSS with an MIT license signal.
The release stream is mostly practical work
The May 27 Constellation 0.4.0 release added wildcard origins in the CORS allow-list and fixed Content-Type handling for POST /graphql. That is not splashy product marketing. It is the kind of compatibility work that matters when real apps hit edge cases across browsers, clients, and API gateways.
The May 26 CLI 1.48.0 release moved schema tooling from Constellation into the CLI. That is a useful direction. Schema diffing, generation, and local workflows belong close to the developer command line, not hidden in a separate internal component.
The dashboard 2.63.1 release is even more maintenance-heavy: ws advisory work, vulnerable dependency updates, form cancellation behavior, permissions table loading, date and time picker rendering, icon migrations, and Apollo Client header cleanup. Boring? Yes. Good boring. Dashboards rot fast when teams only ship headline features.
What ToolVitals can and cannot infer
ToolVitals can say Nhost is active. The metrics support that: 23 release events in 30 days, 30 releases in 90 days, 96 health score, 100 shipping score, and 99 data confidence.
ToolVitals cannot say the product is pleasant to use in production. It does not measure query performance, migration safety, auth edge cases, support quality, hosted uptime from your region, or whether the dashboard fits your team’s workflow.
The payload also has gaps. GitHub commits in the last 30 days and active contributor counts are null here, so the release cadence is the stronger signal than raw commit activity. Treat the numbers as evidence of shipping, not proof of engineering quality.
How it compares
Nhost is smaller than the related developer tools in star count. LangChain has 138,055 stars and 33 release events in 30 days. Composio has 28,531 stars and 30 release events. Nhost has 9,169 stars and 23 release events.
That makes Nhost less of a mass-adoption story and more of a focused backend-platform story. It is shipping at a serious pace without the huge GitHub footprint of LangChain or Gemini CLI.
PostHog is a useful contrast too. It has 34,773 stars, 48 release events in 30 days, and an open-core classification in ToolVitals. Nhost is smaller, but ToolVitals classifies it as OSI-approved OSS with an MIT license signal. If license posture matters to your team, that distinction is not cosmetic.
Recommendation
If your team wants a Firebase-like backend but prefers SQL, GraphQL, local development through a CLI, and a self-hostable MIT-licensed codebase, put Nhost on the evaluation list.
Do not pick it from release velocity alone. Build a thin real app against auth, storage, GraphQL permissions, schema tooling, and deploy flow. Nhost’s current signal says the project is alive and actively maintained. Your test should answer the harder question: whether its backend model matches how your team actually ships.