1. Create the project
That one command makes the folder, installs CrescoDB into it, builds the database, starts the server and opens the dashboard connected to it. Sign in when it asks, and the dashboard's checklist walks you through the next steps.
Want a head start? Add a starter: npm create crescodb@latest my-app -- --template store. The others are auth, blog, chat, payments and todo.
schema.cresco is the whole thing: your models, your fields, and who is allowed to read them. It is JSON, it lives in your repo, and it is the only place you describe your data.
2. Start it again later
Every model has full CRUD. GET, POST, PUT, PATCH and DELETE on the collection and on /:id, plus bulk insert, filtering, ordering and pagination. You did not write a route.
3. Add auth
Those are real files in your project that you own and can edit. Not a dependency you have to guess at. If you want to change how login works, you open the file.
4. Check it before it ships
This answers "who can read this table" from the schema in your repo, offline. It is worth running before you deploy anything, and cresco deploy refuses to ship on a critical finding.
Where to go next
The full command reference, the SDK, storage, realtime and deployment all live in the docs.