Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:

• The Request and Response types are auto-inferred from the endpoint you write
• Because the types are in Typescript you don’t need to generate a client, you just simply use it with @cuple/client and get instant feedback.
• You don’t have to learn another language. It’s just typescript.

Practically it means less boilerplate and it let’s you focus on the feature you write. Cuple is also not a query language, you get what the server sends you, it’s more likely a type-safe FFI binding. With Cuple you can build a REST API, or anything similar to that with HTTP method, header, path, query, body, and you can use it type-safely.

When I was child I thought they are the same places, even though Austria is our neighbour country. 😄