[vsurabhi]

Prisma is used as an ORM for your database, so you would still need to write your own graphql server which sits in front of Prisma.

Hasura is meant to be exposed to the clients directly with declarative access control rules. When you have complex business logic you would write the logic yourselves and expose it alongside Hasura.

Disclosure: I work at Hasura on graphql-engine

[mcintyre1994]

Gotcha! It might just be my inexperience but that completely flew over me from your landing page. I can see how the auth bit implies it, but that sounds pretty cool and isn't really clear IMO!

Do you have something like Prisma's conversion from a very small datamodel to a very complete GraphQL types + functions file going on in the middle then?

[vsurabhi]

> .. completely flew over me

Thanks for the feedback. We thought that the 'BaaS' part would convey it.

> .. small datamodel to a very complete GraphQL types ..

Given any GraphQL server, you can generate the types/functions (using introspection) to access the GraphQL server in a typesafe/idiomatic way for a language. A project which does this: https://github.com/dotansimha/graphql-code-generator.

[yannikyeo]

Is there any sample app / quick start template of a full stack CRUD app (notes, todos etc) with user registration, signin? Not too clear on authn/authz seems to need to go down to Postgres level for such controls.

[praveenweb]

You can take a look at the examples in the repo. Here's one simple todo app with Auth0 integration. https://github.com/hasura/graphql-engine/tree/master/communi...

But we are coming up with a more detailed tutorial on how to build realtime full stack CRUD apps with Auth integration in the coming week.