Shameless plug: My org does this, and we deactived our Slack server to dogfood
https://promptql.io
By building Hasura [0], we already had the ability to generate data catalogs + metadata layer from DB's + API's so the foundational infra was there
[0] https://github.com/hasura/graphql-engine
In One Brain to Query: Wiring a 60-Person Company into a Single Slack Bothasura
graphql-engine
TypeScript2018–2026
hasura / graphql-engine
graphql-engine
Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
42Distinct people
98Mentions
1Explicit recommenders
32.1KGitHub stars
What to know before exploring
What it is
Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
The Use The Index Luke material about this is essential background reading, but in terms of actually implementing: My favorite SQL implementation of cursor-based keyset…
dmitryminkovsky used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- marmelab/react-admin · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year98 dated mentions
Observed mentions: 2018-07-16 10:58:24 UTC to 2026-04-09 17:18:26 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 15 | 6 | 9 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 20 | 6 | 14 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 22 | 4 | 18 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 21 | 4 | 17 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 13 | 7 | 6 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Hasura GraphQL Engine
The Hasura engine is an open source project which supercharges the building of modern applications by providing access
to data via a single, composable, secure API endpoint.
Hasura V3
The future of data delivery is GA: Supporting PostgreSQL (and its flavors), MongoDB, ClickHouse, and MS SQL Server. Also supports writing custom business logic using the Typescript, Python, and Go Connector SDKs. Here is the recommended Getting Started guide on DDN.
The Hasura v3 engine code, which powers Hasura DDN, is in the v3 folder of this repo. You can find more detailed
information about this v3 README.
The Hasura DDN architecture includes Data Connectors to connect to data sources. All Hasura connectors are also
available completely open source. Check out the Connector Hub which lists all
available connectors.
Hasura V2
Hasura V2 is the current stable version of the Hasura GraphQL Engine. Please find more
detailed information about the V2 Hasura Graphql Engine in the v2 folder and this README.
Cloning repository
This repository is a large and active mono-repo containing many parts of the Hasura ecosystem and a long git
history, that can make the first time cloning of the repository slow and consume a lot of disk space. We recommend
following if you are facing cloning issues.
Shallow clone
This will only clone the latest commit and ignore all historical commits.
git clone https://github.com/hasura/graphql-engine.git --depth 1
Git checkout with only Hasura V3 engine code
git clone --no-checkout https://github.com/hasura/graphql-engine.git --depth 1
cd graphql-engine
git sparse-checkout init --cone
git sparse-checkout set v3
git checkout @
This checkouts the top level files and only the v3 folder which contains the Hasura V3 Engine code.
Support & Troubleshooting
To troubleshoot most issues, check out our documentation and community resources. If you have encountered a bug or need
to get in touch with us, you can contact us using one of the following channels:
Hasura DDN documentation: DDN docs
Hasura V2 documentation: V2 docs
Support & feedback: Discord
Issue & bug tracking: GitHub issues
Follow product updates: @HasuraHQ
Talk to us on our website chat
Code of Conduct
We are committed to fostering an open and welcoming environment in the community. Please see the
Code of Conduct.
Security
If you want to report a security issue, please read this.
Stay up to date
Join our communities to stay up to date on announcements, events, product updates, and technical blogs.
https://hasura.io/community/
Contributing
Check out our contributing guide for more details.
Brand assets
Hasura brand assets (logos, the Hasura mascot, powered by badges etc.) can be found in the
v2/assets/brand folder. Feel free to use them in your application/website etc. We'd be thrilled if you
add the "Powered by Hasura" badge to your applications built using Hasura. ❤️
Licenses
V3
All the Data Connectors are available under
the Apache License 2.0.
The core V3 GraphQL Engine is intended to be licensed under the Apache License 2.0 (Apache-2.0).
V2
The V2 core GraphQL Engine is available under the Apache License 2.0 (Apache-2.0).
All other contents in the v2 folder (except those in server, cli and
console directories) are available under the MIT License.
This includes everything in the docs and community
directories.
Read the full README on GitHubWhat Hacker News says
98 sourcesYes, it is open source, and Docker containers are freely accessible too
https://github.com/hasura/graphql-engine
https://hub.docker.com/r/hasura/graphql-engine
I run v2.x images myself, not sure what v3 and DDN are, besides monetization efforts for the company*.
Also the migrations are just `up.sql` and `down.sql` files, there is nothing coupling you to a proprietary migration format, the value Hasura offers is generating them for you and tracking their application thru their CLI.
In Why Is Python So Popular in 2025?Here's a sampling of stuff I've semi-recently encountered on Github that all spy on you by default. For some, it's undocumented, for others it's a minor subsection in the docs. (Some of them are source-available not free, I didn't keep track as I collected the URLs.)
https://github.com/zed-industries/zed
https://github.com/microsoft/vscode
https://github.com/keystonejs/keystone
https://github.com/meilisearch/meilisearch
https://github.com/hasura/graphql-engine
https://github.com/manticoresoftware/manticoresearch/
https://github.com/coder/code-server
https://github.com/loft-sh/devpod
https://github.com/quickwit-oss/quickwit
https://github.com/rilldata/rill-developer/
https://github.com/hocus-dev/hocus
https://github.com/firezone/firezone
Here's a write-up of how bad it gets -- it's pretty obnoxious: https://www.roboleary.net/tools/2022/04/
Read the rest
Ask HN: How Can I Make My Front End React to Database Changes in Real-Time?
I'm exploring ways to make my frontend applications reactive to database changes without overloading the backend.
- Traditional methods like polling are resource-intensive and rerun entire queries, which isn't efficient.
- I’m familiar with some libraries and companies are doing this by building materialized views close to the DB [1][2], but I want to update the frontend, not just the backend.
- Some platforms like Supabase Realtime [3] and Firebase offer subscription models to database changes, but these solutions fall short when dealing with complex queries involving joins or group-bys.
My vision is that the modern frontend to behave like a series of materialized views that dynamically update as the underlying data changes. Current state management libraries handle state trees well but don't seamlessly integrate with relational or graph
Read the rest
-like database structures.
The only thing I can think of is to implement it by myself, which sounds like a big PITA.
Anything goes, Brainstorm with me. Is it causing you headaches as well? Are you familiar with an efficient solution? how are you all tackling it?
[1] https://readyset.io/
[2] https://materialize.com/
[3] https://supabase.com/docs/guides/realtime/postgres-changes
[4] https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md
> We are 100% open source
I mean, so is Hasura. https://github.com/hasura/graphql-engine
(Disclaimer: Work at Hasura)
In Show HN: Graphweaver – Instant GraphQL API on Postgres, MySQL, SQLite and Morehttps://github.com/hasura/graphql-engine
https://github.com/hoppscotch/hoppscotch
https://github.com/nestjs/nest
In Ask HN: What are the best open source TypeScript projects I can learn from?Hasura (https://github.com/hasura/graphql-engine) is quite big project. Although it should be less than 100K LOC.
It was only once when I saw problem that could be considered a bug.
In Haskell, Ada, C++, Awk: An Experiment in Prototyping Productivity (1994) [pdf]plenty of projects that use either of the following on a regular basis:
- https://www.aosabook.org/en/posa/warp.html
- https://morpheusgraphql.com/
- https://higherkindness.io/mu-haskell/
- https://github.com/hasura/graphql-engine
- https://postgrest.org/en/stable/
- https://www.shellcheck.net/
- https://dhall-lang.org/
- https://haskell-miso.org/
- https://github.com/jgm/gitit
- https://jaspervdj.be/hakyll/
- https://github.com/IHaskell/IHaskell
- https://tweag.github.io/HaskellR/ (https://idontgetoutmuch.wordpress.com/2018/05/19/cartography...)
The list can go on, it really depends on what level of "real-worldness" you consider to be real.
In School of Haskell: Basics (2013)As a non-Haskeller, the only tool I can think of interacting with that has any Haskell is Hasura's graphql-engine[0], which GitHub stats say is 28% Haskell (and then like 55% web languages, so I assume the backend is all Haskell and the web languages are for the UI it presents etc)
Are there other popular Haskell tools? Or is it more of an academic language? I was surprised to see it on the GitHub repo.
[0]: https://github.com/hasura/graphql-engine
In 2022 State of Haskell SurveyDisclaimer - I work on Hasura, so I won't comment too much on which is better.
They're all similar flavors of producing realtime results - which take similar, but different, methods to their approach.
My understanding (please feel free to correct me if I'm wrong):
- Supabase Realtime uses WAL.
- Hasura Streaming Subscriptions uses a query which will be append-only (could be a sort-by or also WAL).
- Hasura Live Queries uses interval polling, refetching, and multiplexing.
- Supabase uses Postgres RLS for authorization, while Hasura uses an internal RLS system which composes queries (which allows for features like the multiplexing above).
- All 3 use websockets for their client communication.
Supabase Realtime
https://github.com/supabase/realtime#introduction
https://supabase.com/docs/guides/realtime
Hasura Streaming Subscriptions / Live Qu
Read the rest
It is given here: https://github.com/hasura/graphql-engine/blob/master/archite...
In Streaming data in Postgres to 1M clients with GraphQLStreaming data in Postgres to 1M clients with GraphQL
192 points · Open discussionShow HN: Instant streaming GraphQL APIs with built-in authorization for Postgres
We recently added a streaming GraphQL API to Hasura to allow clients to consume data from Postgres as a stream easily.
There are solutions to ingest and store a large amount of data or a stream of data. However, once this data has been captured, securely exposing this data as a continuous stream to a large number of HTTP clients concurrently is a challenge. And that’s where streaming GraphQL API fits in.
4 points · Open discussionShow HN: Instant streaming GraphQL APIs with built-in authorization for Postgres
5 points · Open discussionShowing the 15 most recent of 98 sources. Enable JavaScript to search and browse every indexed mention.