Repository navigation
docs: start free with Prisma Postgres and Compute, with the Free plan limits on one page - #8392
Conversation
… limits on one page Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…its, move the porting callout below the section Follow-up to the first commit on this branch. Neighbouring docs pages do not date their pricing numbers, so the "as of 2026-10-05" goes. The "Already have an app?" callout moves after the Free plan tables so the commands and the numbers sit on the first screen. The ORM note becomes a paragraph and no longer calls Prisma ORM "free", which no docs page states. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…he Free limits to the workspace, retitle the page Review fixes on greg/docs-start-free. - The lead no longer quotes an incomplete command recipe. It says what the CLI does and points at the agent prompt for the end-to-end run. - Step 2 shows prisma-composer.config.ts. create-prisma writes it with region us-east-1 for every non-Deno template, so the first deploy has the region that cli/deploy says a new project needs. The agent prompt says not to add one, and step 5 no longer claims "nothing to configure". - Step 4 and the agent prompt say that `dev` keeps running: start it in the background or use a second terminal, then stop it. - Free plan section: the pooled-connections row is removed until /postgres/database/connection-pooling matches the pricing page (50 vs 10); the limits are scoped to the workspace and the word is defined; GB-hours, vCPU-hours, scale to zero, direct connections and point-in-time recovery get a plain clause; the database's unlimited transfer and Compute's 10 GB outbound are reconciled in one sentence; both tables use the same number format; "When you reach a limit" is renamed to what the section answers, because no docs page or pricing source states the Free-plan behaviour at a limit; the ORM paragraph moves under the section intro and says "release candidate". - Title is the question the reader asks, in sentence case, and the same words are used in llms.ts, the sidebar label and the two cards that link here, so the page has one name in the H1, llms.txt and the links. - The "Already have an app?" note moves after Prerequisites and leads with the plain version. - The DATABASE_URL side path creates its project under a different name from the module, so it cannot collide with the project step 5 creates. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (5)
Included review availability: This review used your included allowance. Your plan provides up to 5 included reviews per hour; 2 remain after this review. WalkthroughThe tutorial now covers a TypeScript app using Prisma Postgres and Prisma Compute. It adds Free plan details and updates instructions for local development, Composer configuration, and deployment. Documentation links and titles also reflect the updated tutorial. ChangesFull-stack tutorial
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This updates the full-stack tutorial and its titles and links to describe starting a TypeScript app with Prisma Postgres and Compute on the Free plan. It carries no runtime impact and is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
🍈 Lychee Link Check Report95 links: ✅ All links are working!Full Statistics Table
|
…nd the Free-plan link) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What changed
/docs/full-stack-tutorialnow answers "what is the fastest way to start a TypeScript app with Postgres on Prisma, and what does the Free plan include" on one page. Before this, an agent needed three pages: the tutorial for the commands,/pricingfor the Free numbers, and/compute/pricingfor the Compute meters.npx prisma postgres usage, the Console, and the upgrade path.prisma-composer.config.ts. The scaffold writes it withprismaCloud({ region: "us-east-1" }), so the first deploy has the regioncli/deploysays a new project needs. The agent prompt says not to add one, and step 5 no longer claims there is nothing to configure.devkeeps running: start it in the background or use a second terminal, then stop it.commonQueriesentry, the sidebar label and the two cards that link here use the same words, so the page has one name in the H1, in llms.txt and in its links.metaTitleandmetaDescriptionstay search-oriented.DATABASE_URLside path in step 4 creates its project under a different name from the module, so it cannot collide with the project step 5 creates.apps/docs/src/lib/llms.ts: newcommonQueriesentry for the page.Facts checked (2026-10-06)
https://www.prisma.io/pricing.md("Free forever. No credit card required.", "Free tier with no time limit");apps/site/src/lib/pricing-data.ts(Compute Free: "no usage billing")pricing.mdplan table and spec table;apps/site/src/components/sections/pricing-spec-table.tsxpricing.mdspec table ("Connection limit (direct) 10");pricing-spec-table.tsx;apps/docs/content/docs/postgres/database/connection-pooling.mdxpg_dumpover a direct connectionpricing.md(backups "—" on Free);apps/docs/content/docs/postgres/database/backups.mdxapps/docs/content/docs/postgres/faq.mdx(#what-is-an-operation);pricing.mdFAQ "What counts as an operation?"pricing.md;apps/docs/content/docs/compute/pricing.mdx;pricing-data.ts(computeIncludedRequests.free)compute/pricing.mdx(meters table, intro);compute/faq.mdxpricing.mdFAQ "Are there egress fees?"apps/docs/content/docs/console/concepts.mdx(#workspace);postgres/troubleshooting.mdx("Workspace plan limit reached")npx prisma postgres usage <database>; the Console tracks usage; Compute usage reporting still being builtcli/postgres.mdx;postgres/index.mdx(#billing-and-limits);compute/pricing.mdxpricing.md("You can set a spend limit on any paid plan")postgres/index.mdx;compute/faq.mdx(#do-i-need-prisma-orm-to-use-compute);orm/release-status.mdxprismaCloud({ region: "us-east-1" })inprisma-composer.config.tscli/deploy.mdx;compute/limitations.mdx(region ids);prisma/create-prismatemplates/create/_shared/prisma-composer.config.ts.hbson main, read 2026-10-06devkeeps running and restarts on build changes; SvelteKit and Deno do not deploy to Compute;--yesand--no-deploycli/dev.mdx;guides/frameworks/sveltekit.mdx;(index)/prisma-orm/create-prisma.mdxRemoved on purpose: the "Pooled connections: 10" row. The pricing page says 10 on Free, but
/postgres/database/connection-poolingsays 50 (and 50 / 250 / 500 for the paid plans against the pricing page's 100 / 500 / 1,000). Follow-up: bring that page's table in line with the pricing page, then the row can come back.Not stated on purpose: what happens when a Free limit is reached (block, pause, notify). No docs page and no pricing source says, so the section is named for what it does answer.
Checks run in the worktree
pnpm run lint:links: 0 errors.pnpm run lint:agent-ready: 0 failures, 1 pre-existing warning (llms/orm-v7.txtsize).check-plain.sh,check-staccato.py,check-ai-signs.sh: clean on the three changed pages. cspell on the same pages: clean.oxfmton the two changed TypeScript files.pnpm testinapps/docs: 70 of 71 pass.database-selection.test.tsfails locally withERR_MODULE_NOT_FOUNDfor@prisma/eclipse/dist/index.mjs, a dependency missing from this machine's install and unrelated to this change.Not verified locally
create-prisma@latestrequires npm 11.6 or newer; this machine has npm 10.9.9). Theprisma-composer.config.tsshown in step 2 is the create-prisma template output for a non-Deno, non-Next template. Worth a glance from someone who has run the scaffold this week.Reviewers to ask
The docs owners for the Start section (
apps/docs/content/docs/(index)/),apps/docs/src/lib/llms.tsandsidebar-sections.tsx. Recent reviewers of pages in this section: wmadden, sorenbs.🤖 Generated with Claude Code
Summary by CodeRabbit