Code
Your schema says what the data is. These pages cover what you write beside it, the endpoints, background work and shared objects that a table cannot describe on its own.
Everything here is a file in a directory the generator reads, same as a collection. You write the file, the generator finds it, and it arrives typed on the app object.
| Page | What you write |
|---|---|
| Routes | HTTP endpoints of your own, beyond the five a collection gets. |
| Services | Shared objects injected into handlers. An SDK client, a cache. |
| Jobs | Work that runs off the request path. |
| Emails | Typed templates, rendered with the app's own context. |
| Modules | A bundle of collections, routes and jobs you can share or ship. |
| Codegen | What the generator reads, what it writes, and how to extend it. |
Where the line falls
Schema is what you declare. A collection, its fields, the rules around them.
Code is what you write. A route body, a job handler, a service class.
Infrastructure is what you configure. Storage, queue, search. You pick an adapter rather than writing one, and you can swap it.