3.1 KiB
layout | home | heroText | heroImage | heroImageMobile | tagline | longTagline | actionText | actionLink | description | features | footer | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HomeLayout | true | Super Graph | /super-graph-web-ui-half.png | /super-graph-web-ui.png | Build web products faster. Instant APIs for your apps | Get an instant high performance GraphQL API for Postgres. No code needed. GraphQL is automatically transformed into efficient database queries. | Get Started, Free, Open Source → | /guide | Super Graph can automatically learn a Postgres database and instantly serve it as a fast and secured GraphQL API. It comes with tools to create a new app and manage it's database. You get it all, a very productive developer and a highly scalable app backend. It's designed to work well on serverless platforms by Google, AWS, Microsoft, etc. The goal is to save you a ton of time and money so you can focus on you're apps core value. |
|
MIT Licensed | Copyright © 2018-present Vikram Rangnekar |
Try the demo
# download super graph source
git clone https://github.com/dosco/super-graph.git
# setup the demo rails app & database and run it
./demo start
# signin to the demo app (user1@demo.com / 123456)
open http://localhost:3000
# try the super graph web ui
open http://localhost:8080
Try a query
query {
users {
id
email
picture : avatar
products(limit: 2, where: { price: { gt: 10 } }) {
id
name
description
}
}
}
Why Super Graph?
After working on several product though my career I found building CRUD APIs (Create, Update, Delete, List, Show) to be a big part of the job. It was always the same thing figure out what the UI needs then build an endpoint for it, if related data is needed than join with another table. I didn't want to write that code anymore I wanted the computer to just do it.
I always liked GraphQL it sounded friendly, but it still required me to write all the same database query code. Sure the API was nicer but it took a lot of work sometime even more than a simple REST API would have. I wanted a GraphQL server that just worked the second you deployed it without having to write a line of code.
And so after a lot of coffee and some Avocado toasts Super Graph was born, a GraphQL server that just works, is high performance and easy to deploy. I hope you find it as useful as I do and there's a lot more coming so hit that ⭐ to stay in the loop.