Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


๐Ÿš€ Advanced starter code for a scalable, production-ready GraphQL server written in TypeScript, including authentication and realtime functionality with GraphQL subscriptions.


  • Scalable GraphQL Server: graphql-yoga based on Apollo Server & Express
  • GraphQL-native database: Includes GraphQL database binding to Prisma (running on MySQL)
  • Out-of-the-box support for GraphQL Playground & Tracing
  • Simple data model โ€“ easy to adjust
  • Preconfigured graphql-config setup
  • Authentication based on email & password
  • Realtime functionality with GraphQL subscriptions (coming soon)


You need to have the following tools installed:

  • Node 8+ & TypeScript
  • GraphQL CLI: npm i -g graphql-cli

Getting started

# 1. Bootstrap GraphQL server in directory `my-app`, based on `typescript-advanced` boilerplate
graphql create my-app --boilerplate typescript-advanced

# 2. When prompted, choose the Prisma cluster you want to deploy to
# e.g. prisma-eu1 or prisma-us1 to deploy to a public cluster (recommended)
# or locally (requires Docker)

# 3. Navigate to the new project
cd my-app

# 4. Start server (runs on http://localhost:4000) and open GraphQL Playground
yarn dev
# or
# yarn start # (only starts the server, no access to the Prisma API)

Note: We recommend that you're using yarn dev during development as it will give you access to the GraphQL API or your server (defined by the application schema) as well as to the Prisma API directly (defined by the Prisma schema). If you're starting the server with yarn start, you'll only be able to access the API for the application schema.


add to model

  • add in database/datamodel.graphql
  • prisma deploy
  • yarn graphql prepare # for type generation


  • yarn start starts GraphQL server on http://localhost:4000 (only allows access to the _appl)
  • yarn debug starts GraphQL server in debug mode (open chrome://inspect/#devices to debug)
  • yarn dev starts GraphQL server opens the GraphQL Playground for the projects defined in .graphqlconfig.yml
  • yarn playground opens the GraphQL Playground for the projects defined in .graphqlconfig.yml
  • yarn prisma <subcommand> access to local version of Prisma CLI (e.g. yarn prisma deploy)

Project structure

/ - configuration files

/database - Prisma service

/src - application server

  • src/schema.graphql defines your application schema. It contains the GraphQL API that you want to expose to your client applications.
  • src/index.js is the entry point of your server, putting everything together and starting the GraphQLServer from graphql-yoga.
  • src/resolvers/ contains the actual business logic of your application. In GraphQL, you implement resolver functions that resolve a specific query being requested.
  • src/generated/prisma.graphql defines the database schema. It contains the GraphQL API exposed by the Prisma Database. This file is automatically generated every time yarn prisma deploy is executed, according to the datamodel in database/datamodel.graphql.
  • src/generated/prisma.ts contains the generated TypeScript type definitions from the prisma-binding. You can read more about static bindings in this article.


Your feedback is very helpful, please share your opinion and thoughts! If you have any questions, join the #graphql-boilerplates channel on our Slack.