Documentation

QUESTPIE derives a database schema, a typed API, an admin and a client from one description of your data. These pages cover what you declare, what you write beside it, and what you configure underneath.

Nine groups. These two teach, in order.

Learn

What QUESTPIE is, the one-schema model, and a first app end to end.

Guides

One job each, start to finish. An agent connected, a slow request traced.

The other seven are where you look things up.

Schema

Collections, fields, relations, access rules, hooks.

Code

Routes, services, jobs, emails, modules, codegen.

Infrastructure

Storage, queue, search, realtime, KV, email, sandbox.

Client

The typed client, query helpers, realtime subscriptions.

Admin

The generated workspace and your own views inside it.

Agents

MCP, OpenAPI, and the plain-text docs.

Ship

Configuration, environment, migrations, scaling, monitoring.

The shortest version

You describe a table in a file. The generator reads that file and writes a typed app object, five REST routes and a client that carries the same types. Change the description and all of them move together, because none of it was written twice.

src/questpie/server/collections/news.ts

import { collection } from "#questpie/factories";

export const news = collection("news").fields(({ f }) => ({
	title: f.text(255).label("Title").required(),
	isPublished: f.boolean().default(false),
}));

What QUESTPIE is takes that file apart: what the core builds from it, what the modules add, and which package each piece comes from.