Prisma

and the schema itself doesn't have to be a one to one mapping of your database

Ah ok. I thought that the schema could have _fewer_ fields, if you want to not surface data, but that it could not have fields of its own

is there a schema type that handles a generic object, or do i have to go through the process of defining a custom schema with all of my object properties

in this particular case, it sounds like you're asking about the arguments to the mutation. That can certainly be whatever you need for the mutation to do it's job

There are a few JSON custom scalar types, but my understanding is that it's not a best practice...you sort of break tooling if you do that, and defeats the purpose of having a strongly typed schema

yeah, since you are essentially writing a GraphQL server that bridges Prisma's one then you can resolve however you want your schemas and then pass the necessary stuff to Prisma