Type Name Latest commit message Commit time
Failed to load latest commit information.
.install migrate to prisma-client Dec 10, 2018
prisma migrate to prisma-client Dec 10, 2018
src migrate to prisma-client Dec 10, 2018
.env migrate to prisma-client Dec 10, 2018
.gitignore added env file Dec 19, 2017 migrate to prisma-client Dec 10, 2018
package.json chore(deps): update dependency nodemon to v1.18.8 Dec 10, 2018
tsconfig.json generated schema Dec 19, 2017
yarn.lock chore(deps): update dependency nodemon to v1.18.8 Dec 10, 2018

Boilerplate for an Advanced GraphQL Server w/ TypeScript

🚀 Bootstrap your GraphQL server within seconds
Advanced starter kit for a flexible GraphQL server for TypeScript - based on best practices from the GraphQL community.


  • Scalable GraphQL server: The server uses graphql-yoga which is based on Apollo Server & Express
  • Static type generation: TypeScript types for GraphQL queries & mutations are generated in a build step
  • Authentication: Signup and login workflows are ready to use for your users
  • GraphQL database: Includes GraphQL database binding to Prisma (running on MySQL)
  • Tooling: Out-of-the-box support for GraphQL Playground & query performance tracing
  • Extensible: Simple and flexible data model – easy to adjust and extend
  • No configuration overhead: Preconfigured graphql-config setup
  • Realtime updates: Support for GraphQL subscriptions

Read more about the idea behind GraphQL boilerplates here.


You need to have the GraphQL CLI installed to bootstrap your GraphQL server using graphql create:

npm install -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, deploy the Prisma service to a _public cluster_

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

# 4. Start server (runs on http://localhost:4000) and open GraphQL Playground
yarn start



  • yarn start starts GraphQL server on http://localhost:4000
  • yarn prisma <subcommand> gives access to local version of Prisma CLI (e.g. yarn prisma deploy)

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 database schema). If you're starting the server with yarn start, you'll only be able to access the API of the application schema.

Project structure

File name                Description         

├── .env Defines environment variables
├── .graphqlconfig.yml Configuration file based on graphql-config (e.g. used by GraphQL Playground).
└── database (directory) Contains all files that are related to the Prisma database service
  ├── prisma.yml The root configuration file for your Prisma database service (docs)
  └── datamodel.graphql Defines your data model (written in GraphQL SDL)
└── src (directory) Contains the source files for your GraphQL server
  ├── index.ts The entry point for your GraphQL server
  ├── schema.graphql The application schema defining the API exposed to client applications
  ├── resolvers (directory) Contains the implementation of the resolvers for the application schema
  └── generated (directory) Contains generated files
    └── prisma-client (directory) The generated Prisma client


The GraphQL boilerplates are maintained by the GraphQL community, with official support from the Apollo & Prisma teams.

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