guides

A schema definition (often abbreviated to "schema") is defined by:

deployment

Keystone files need to be built with keystone build before running in production mode.

deployment

This quick start guide shows how to deploy your first KeystoneJS app to Heroku and use MongoDB Atlas as our database service.

Hooks give developers a way to add custom logic to the framework of lists, fields and operations Keystone provides.

A Keystone instance acts as a function of your schema which creates a GraphQL API for querying and an Admin UI for managing your data:

advanced

As your app grows new features, you'll inevitably need to change some of your existing List definitions. When you do, you'll also need to migrate the data and schema in your database backend.

This cheatsheet summarises the changes needed to update your database to use the new Keystone database schema, introduced in the Arcade release. For full instructions please consult the migration guide.

deployment

Yes, Keystone can be (and is!) used for production websites. Here's a handy list of tips for using Keystone with real workloads:

In the Arcade release of Keystone we changed the database schema which Keystone uses to store its data. This means that if you are upgrading to these new packages you will need to perform a migration on your database in order for it to continue working.

Warning: The Prisma adapter uses Prisma Migrate, which is currently in preview. We do not recommend using the Prisma adapter for production systems yet.