ARCHE
FamiliesDocsExamplesBlogGitHub ↗
Documentation

Start

  • Getting started
  • Philosophy

Guides

  • First hour
  • Agent context
  • Verification
  • Package managers
  • Scaffold lifecycle
  • Showcase & portfolio

Walkthroughs

  • TypeScript fullstack
  • Convex product
  • Rust API & fullstack
  • Solana family
  • Customize & experiments
  • Automation (JSON/MCP)

CLI

  • Overview
  • Flags
  • Subcommands
  • Generated output

Presets

  • Preset catalog

Stack

  • TypeScript architecture
  • Convex
  • Rust
  • Solana
  • Authentication
  • Prisma store
  • tRPC

Operations

  • Deployment
  • Environment variables
  • Workers & queues
  • CI & testing
  • Scaling
  • Security
  • Troubleshooting

Reference

  • Stack links
  • Capabilities
  • This source repo
  • Code examples
← Documentation

Prisma store

Database schema, client, and migrations in packages/store.

1 min read

packages/store owns the Prisma schema and generated client for the TypeScript fullstack preset.

Loading diagram…

Commands (generated project)

terminal
bun run db:generate   # prisma generate
bun run db:migrate    # migrate dev / deploy per your workflow

Exact script names are in the generated root package.json and AGENTS.md.

Architecture rules

  • All database access goes through repositories/services—avoid importing Prisma in React components
  • Server-only: package exports prevent accidental browser bundles
  • Migrations live with the schema; run them against DATABASE_URL for the target environment

Providers

Scaffold flags support Postgres (default), SQLite, MongoDB, or none depending on preset and --database. The generated schema and docs match your selection—do not assume Neon unless DATABASE_URL points there.

Production

Use a managed Postgres URL (Neon recommended in Arche deployment docs). Connection pooling and migration strategy are your ops concern; Arche documents the wiring, not SLAs.

Related: Deployment