Database & Prisma

Overview

SiteKnock's data layer is built on Prisma 7. You choose your database engine in config, define your models in schema partials, and the generator assembles everything for you.

Supported databases

Choose a provider

"features": {
  "database": {
    "enabled": true,
    "provider": "postgres"
  }
}

Switch providers at any time:

pnpm db:select -- mysql
pnpm sk:generate

Schema partials

Partials live under your backend app:

apps/backend/prisma/
├── schema.prisma            # GENERATED — do not edit
└── partials/
    ├── auth.prisma.part     # auth models (from the auth feature)
    ├── orgs.prisma.part     # organization models
    ├── billing.prisma.part  # billing models
    └── custom.prisma.part   # your models

Add a model

1. Add it to a .prisma.part file:

   model Article {
     id        String   @id @default(cuid())
     title     String
     content   String?
     createdAt DateTime @default(now())
     updatedAt DateTime @updatedAt
   }
   

2. Generate the client and run a migration for your backend app:

   pnpm app db generate my-app
   pnpm app db migrate my-app
   

Everyday database commands

These run from your project root and target a backend app:

Frontend never touches the database

The frontend never imports Prisma. It calls your /api/* routes, which handle all database access server-side. This keeps credentials and queries on the backend where they belong.

Next steps