graphql-engine
hasura/graphql-engine
Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
Ship status
Still shippingPushed in the last 30 days.
- Last push
- Sep 21, 2026
- 11 days ago
- Stars, last 7 weeks
- +14 stars in the 28 days to 2026-09-29
Shipping: pushed in the last 30 days Β· slowed: quiet for 31β120 days Β· silent: no push in over 120 days.
Repo facts
What GitHub reports.
- Stars
- 32.1K
- Forks
- 3K
- Open issues
- 2.4K
- Watchers
- 354
- Primary language
- TypeScript
- License
- Apache License 2.0
- Created
- Jun 18, 2018
- Owner
- hasura Β· Organization
Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license β GitHubβs own license field, not legal advice. 208 startups in the directory ship primarily in TypeScript.
Topics
How it got here
What the classifier decided, and when.
Classified as an open-source startup by Jev, TypeSafeβs classifier, on Sep 22, 2026 β os_startup 98%, self-hostable 77%, hosted offering 93%. The classifier reads only the repositoryβs name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.
Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works β
Embed your status
Put this badge on your README.
[](https://ossean.com/hasura/graphql-engine)
Updates daily, from the last push GitHub saw.
Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=βnofollowβ, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup β your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.
Related projects