I think your example is basically trying to show the difference between generated and self defind schemas.

and I want the self defined with bindings in the playground after deploying to your cloud

I guess it could be a definition in the .graphqlconfig.yml that should point the endpoint to the deployed http. however, that didnt work for me.

Your are visiting the prisma db uri directly which will show the the db schema.

Here is the solution

Run the local server with yarn start which will take you to http://localhost:4000 for your self defined schema queries and mutation

?

Also I need you to understand you can only host your prisma database on the prisma cloud and not your server

basically it is very simple: when I choose "prisma deploy" I can choose to deploy to US or EU. when I do this only the generated Schema is available. i wonder if this is a bug or on purpose

So here is how prisma works

Prisma is a graphql database or more so abstract existing databases into a graphql database. When you run the prisma deploy command you deploy your database schem to prisma cloud and not your query and resolvers those run on a separate server for now. So you need to host your web server too on heroku or any similar hosting solutions

Again see prisma as a database and your query and custom logic as an express application. You need to host ypur db right eo thats what prisma deploy does. You also gotta host your server too right, so thats when ypu need heroku or alternatives. Now how does the server talk to the database, through the prisma endpoint in the Prisma.yml file.

I looked at the pricing page again at prismagraphql.com. It is not so easy to understand. However, the sentence "There will be hosting options in the Prisma Cloud in the future" is saying I guess that in the future it will be possible to deploy even self created resolvers to the prisma cloud. thank you for helping!