| Meter | -Expected price | +Price | What it represents |
- $1.00 / 1M requests
+ $1 per million
|
The familiar per-request anchor that keeps a normal app easy to estimate | @@ -230,12 +229,12 @@ actually consumed while work runs. There is one line worth watching before you ship: outbound bandwidth. For streaming, media, exports, file-heavy apps, and high-transfer APIs, transfer can become the largest part of the bill. We expose it as its own meter rather than -burying it inside a blended unit, and we expect to learn from it during beta. +burying it inside a blended unit. -This is still a beta model. Rates, limits, included usage, and policy details may -change before production billing turns on. But the direction is deliberate: -familiar meters, no tax on shipping, no hidden Prisma unit, and usage data humans -and agents can both reason about. +Every plan also includes a monthly request allowance — 1M requests on the Free +plan, up to 100M on Business — before the request meter starts. The direction is +deliberate: familiar meters, no tax on shipping, no hidden Prisma unit, and +usage data humans and agents can both reason about. ## The future we are building for @@ -244,8 +243,9 @@ the Prisma ORM. The principle in this post is not only about Compute, it is how we think the platform should treat builders. To get that right, we need to learn from real workloads. How long apps stay -alive, how much they compute versus wait, how much data they send out. Compute is -now in public beta and free during this time. [Share the shape of your +alive, how much they compute versus wait, how much data they send out. You can +start on the Free plan, which includes 1M requests a month. [Share the shape of +your workload](https://tally.so/r/NpEZXB?source=blog&post=price-the-work-not-the-workflow&campaign=compute-pricing-feedback&cta=blog_end_cta) so we can see where these meters match how you actually build, and where they do not. diff --git a/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx b/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx index 855331c319a..7bf355073fc 100644 --- a/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx +++ b/apps/blog/content/blog/prisma-7-ama-clearing-up-the-why-behind-the-changes/index.mdx @@ -6,9 +6,9 @@ authors: - "Ankur Datta" metaTitle: "Prisma 7 Explained: Performance, Architecture, and AMA Answers" metaDescription: "Prisma 7 introduces major architectural changes. We answer community AMA questions on performance, database support, the new client generator, and what’s next." -metaImagePath: "/prisma-7-ama-clearing-up-the-why-behind-the-changes/imgs/meta-64c44281ee8d3e0fe5e7e9bbd309603e5496945d-1266x711-26d35e93c9.png" -heroImagePath: "/prisma-7-ama-clearing-up-the-why-behind-the-changes/imgs/hero-fed37f83921ceeba6d0395d774c48ae9d5b68dcc-844x474-7cca11ee09.png" -heroImageAlt: "Prisma 7 is a structural release focused on long-term architecture rather than surface-level features. Some things improved, others became stricter. This post answers questions from our recent AMA on X and explains where Prisma 7 stands today and where it’s headed." +metaImagePath: "/prisma-7-ama-clearing-up-the-why-behind-the-changes/imgs/meta.png" +heroImagePath: "/prisma-7-ama-clearing-up-the-why-behind-the-changes/imgs/hero.svg" +heroImageAlt: "A question and answer from the Prisma 7 AMA set in large type: Prisma 7 vs Prisma 6 performance, is it faster or slower, answered with the line that it depends heavily on how you measure performance, with that phrase in cyan." tags: - "orm" --- diff --git a/apps/blog/content/blog/prisma-compute-config-file/index.mdx b/apps/blog/content/blog/prisma-compute-config-file/index.mdx index 8cdcc2dd06d..52539f68420 100644 --- a/apps/blog/content/blog/prisma-compute-config-file/index.mdx +++ b/apps/blog/content/blog/prisma-compute-config-file/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "Configure Prisma Compute deploys in TypeScript" metaDescription: "Prisma Compute now reads a typed TypeScript config file, so deploys are reproducible and monorepos work: declare one app or several, then ship the whole system with one command." heroImagePath: "/prisma-compute-config-file/imgs/hero.svg" -heroImageAlt: "One typed file for every app target: a prisma.compute.ts declaring an api app on Hono and a web app on Next.js" +heroImageAlt: "An ink prisma.compute.ts code card declaring a monorepo config: an api app rooted at apps/api on Hono and a web app rooted at apps/web on Next.js" metaImagePath: "/prisma-compute-config-file/imgs/meta.png" excerpt: "Prisma Compute now reads a typed prisma.compute.ts, so deploys are reproducible and monorepos work: declare one app or several, then ship the whole system with one command." series: prisma-compute @@ -153,4 +153,4 @@ Starting fresh? [`create-prisma`](/create-prisma-deploy-prisma-compute) scaffold For the full field reference, see the [configuration docs](https://docs.prisma.io/docs/compute/configuration). For everything else about deploying on Compute, start with the [quickstart](https://docs.prisma.io/docs/prisma-compute/deploy). -One config file is the point: the same repo describes your data with [Prisma Postgres](https://www.prisma.io/postgres), your app with [Prisma Compute](https://docs.prisma.io/docs/compute), and your deploys with `prisma.compute.ts`, so a person or an agent can reason about the whole system in one place. Compute is in public beta and free while the beta lasts. Tell us what you ship in [#prisma-compute](https://pris.ly/discord-compute) on Discord. +One config file is the point: the same repo describes your data with [Prisma Postgres](https://www.prisma.io/postgres), your app with [Prisma Compute](https://docs.prisma.io/docs/compute), and your deploys with `prisma.compute.ts`, so a person or an agent can reason about the whole system in one place. Every plan [includes Compute usage](https://pris.ly/pricing-compute), starting with 1M requests a month on the Free plan. Tell us what you ship in [#prisma-compute](https://pris.ly/discord-compute) on Discord. diff --git a/apps/blog/content/blog/prisma-compute-custom-domains/index.mdx b/apps/blog/content/blog/prisma-compute-custom-domains/index.mdx index fb486f57639..fcea9a9676a 100644 --- a/apps/blog/content/blog/prisma-compute-custom-domains/index.mdx +++ b/apps/blog/content/blog/prisma-compute-custom-domains/index.mdx @@ -6,8 +6,9 @@ authors: - "Tyler Benfield" metaTitle: "We Launched Prisma Compute with Custom Domains" metaDescription: "Prisma Compute launched with custom domain support. Here's how we made the setup one DNS record while handling TLS certificate provisioning, storage, and routing behind the scenes." -heroImagePath: "/prisma-compute-custom-domains/imgs/hero.png" -heroImageAlt: "Custom domain in browser address bar" +heroImagePath: "/prisma-compute-custom-domains/imgs/hero.svg" +heroImageAlt: "The one DNS record a custom domain needs: a CNAME for shop.acme.com pointing at switchboard.cdg.prisma.build with a TTL of 300, and a status row reading active" +metaImagePath: "/prisma-compute-custom-domains/imgs/meta.png" tags: - "platform" series: prisma-compute diff --git a/apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx b/apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx index af83ff717c1..14250bf53f8 100644 --- a/apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx +++ b/apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "How Prisma Compute Keeps Time Accurate in Long-Running Applications" metaDescription: "How Prisma Compute keeps wall-clock time accurate in long-running Firecracker microVMs, using the host-paired KVM PTP clock instead of an in-guest NTP daemon." heroImagePath: "/prisma-compute-time-synchronization/imgs/hero.svg" -heroImageAlt: "Average clock skew on an awake VM, drifting about 13.75 ms/h (3.82 ppm): -13.8 ms at one hour, -27.5 ms at two, -55 ms at four, -82.5 ms at six" +heroImageAlt: "A drift drawing: the host paired clock read from /dev/ptp0 holds flat while an awake microVM's guest CLOCK_REALTIME falls away at 13.75 ms per hour (3.82 ppm), reaching about -82.5 ms after six hours" metaImagePath: "/prisma-compute-time-synchronization/imgs/meta.png" series: prisma-compute seriesIndex: 9 diff --git a/apps/blog/content/blog/prisma-compute-vs-vercel-pricing/index.mdx b/apps/blog/content/blog/prisma-compute-vs-vercel-pricing/index.mdx index 910bb8302eb..812d5cf6928 100644 --- a/apps/blog/content/blog/prisma-compute-vs-vercel-pricing/index.mdx +++ b/apps/blog/content/blog/prisma-compute-vs-vercel-pricing/index.mdx @@ -5,7 +5,7 @@ date: "2026-07-01" authors: - "Martin Janse van Rensburg" heroImagePath: "/prisma-compute-vs-vercel-pricing/imgs/hero.svg" -heroImageAlt: "The same 20M-request month costs about $98 on Prisma Compute at planned rates versus about $236 on Vercel (Pro), saving about $138 or 58% every month." +heroImageAlt: "A line by line table of the same 20M-request month: about $98 total on Prisma Compute at planned rates against about $236 on Vercel (Pro)" metaImagePath: "/prisma-compute-vs-vercel-pricing/imgs/meta.png" series: prisma-compute tags: @@ -17,14 +17,14 @@ metaDescription: "Prisma Compute vs Vercel, priced line by line: the same worklo You're weighing [Prisma Compute](https://www.prisma.io/compute) against Vercel to host a TypeScript app, and you want the hard numbers quick. Here they are, with some _musings_ about them after. :::note -Prisma Compute is in **public beta** and free right now. The rates cited here are the [_expected_ production prices](https://www.prisma.io/docs/compute/pricing); they might still change by the time actual billing starts. [Vercel's pricing](https://vercel.com/pricing) is live. +Prisma Compute pricing is **live**: the rates cited here are the [production prices](https://www.prisma.io/docs/compute/pricing). Every plan also includes a monthly request allowance — from 1M requests on the Free plan to 100M on Business — which this raw meter-by-meter comparison leaves out. [Vercel's pricing](https://vercel.com/pricing) is live too. ::: ## Comparing Prisma Compute and Vercel by usage meter Both are usage-based and scale to zero, so once an app goes idle, it costs nothing. -| Meter | Prisma Compute (Beta) | Vercel (Pro) | Cheaper | +| Meter | Prisma Compute | Vercel (Pro) | Cheaper | |---|---|---|---| | Requests / invocations | $1.00 / 1M | $0.60 / 1M | **Vercel** (~40% less) | | Provisioned memory | $0.006 / GB-hour | $0.0106 / GB-hour | **Prisma** (~43% less) | @@ -33,13 +33,13 @@ Both are usage-based and scale to zero, so once an app goes idle, it costs nothi | Edge requests _(workflow)_ | None | $2.00 / 1M | **Prisma** | | Seat fee _(workflow)_ | None | $20 / user / mo (incl. $20 credit) | **Prisma** | -**Note:** Vercel has a defined free tier and a more mature platform including a global edge network and a big ecosystem. Prisma Compute's production free allowance is work-in-progress, and it is a brand new product. +**Note:** Vercel has a more mature platform including a global edge network and a big ecosystem, and it is a brand new product on Prisma's side. On included usage, Prisma's Free plan comes with 1M Compute requests a month, and paid plans include 5M–100M requests before the request meter starts. ## Comparing a 20M-request app on Prisma Compute vs Vercel Here's a single growing app for a month. Let's assume 20M requests, 2 GB of memory held while running (call it always-on for a 730-hour month, so 1,460 GB-hours), 300 vCPU-hours of actual compute, and 2 TB of outbound traffic. One seat. -| Line | Prisma Compute (Beta) | Vercel (Pro, 1 seat) | +| Line | Prisma Compute | Vercel (Pro, 1 seat) | |---|---|---| | Requests / invocations (20M) | $20.00 | $12.00 | | Memory (1,460 GB-hrs) | $8.76 | $15.48 | @@ -86,14 +86,14 @@ Beyond the free tier, it doesn't always go that way. The bill can jump with no j In the [same thread](https://www.reddit.com/r/nextjs/comments/1qnld0e/is_anyone_else_frustrated_with_vercel_pricing/), another developer drew a sharp line between the two sides of Vercel: the frontend is "really nice and cheap/free," the backend "absolute highway robbery." Others pointed at workflow charges, like a $150 bill "for Deployment Protection Exceptions." The recurring frustration is not just that bills get high, it's that teams feel they discover the shape of the bill after the workflow has already run. -On the other hand, Prisma Compute is still in public beta, so developers haven't been able to use it in a way that would lead to meaningful feedback yet. I am sure there will be, and I will update this article when this feedback starts to arrive. +On the other hand, Prisma Compute has only just left beta, so developers haven't been able to use it long enough for meaningful pricing feedback yet. I am sure there will be, and I will update this article when this feedback starts to arrive. ## Summary -On planned rates, Prisma Compute is a lot cheaper than Vercel for the parts of a bill that usually dominate (CPU, memory, egress) and it doesn't bill the seat, deploys, or previews. Vercel is cheaper on raw request price and has a more mature platform, an established free tier, and an ecosystem Prisma needs to catch up with. +At today's rates, Prisma Compute is a lot cheaper than Vercel for the parts of a bill that usually dominate (CPU, memory, egress) and it doesn't bill the seat, deploys, or previews. Vercel is cheaper on raw request price and has a more mature platform and an ecosystem Prisma needs to catch up with. Finally, don't trust a blog article over your own math (or common sense). Figure things out for yourself before making a big commitment. :::ppg[Run the math on your own app] -[Prisma Compute](https://www.prisma.io/compute) is free while the beta lasts. [Deploy a TypeScript app](https://www.prisma.io/docs/compute/getting-started) next to your [Prisma Postgres](https://www.prisma.io/postgres) database and watch the usage meters before billing ever starts. +[Prisma Compute](https://www.prisma.io/compute) includes 1M requests a month on the Free plan. [Deploy a TypeScript app](https://www.prisma.io/docs/compute/getting-started) next to your [Prisma Postgres](https://www.prisma.io/postgres) database and watch the usage meters as it runs. ::: diff --git a/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx b/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx index f370de8c269..c8ce37ce13f 100644 --- a/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx +++ b/apps/blog/content/blog/prisma-next-call-for-extension-authors/index.mdx @@ -8,7 +8,7 @@ authors: metaTitle: "Prisma 8: A Call for Extension Authors" metaDescription: "Prisma 8 has a tiny core that knows nothing about specific databases. Postgres, vector search, and JSON-with-schema are extensions, on the same surface that's open to you. An invitation to build." heroImagePath: "/prisma-next-call-for-extension-authors/imgs/hero.svg" -heroImageAlt: "Prisma 8: A Call for Extension Authors" +heroImageAlt: "A dark manifest card for an extension package listing the four layers it can contribute: contract, query, runtime and migration, over the line that registers it" metaImagePath: "/prisma-next-call-for-extension-authors/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx b/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx index 66ce1d81501..1f4d228f3f1 100644 --- a/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx +++ b/apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx @@ -7,8 +7,8 @@ authors: - "Will Madden" metaTitle: "Prisma 8 Early Access: Write Your Contract, Prompt Your Agent, Ship Your App" metaDescription: "Prisma 8 is open for Early Access. Define your data layer as a contract and the framework handles migrations, type-safe queries, and continuous upgrades, safe to delegate to your agent." -heroImagePath: "/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/meta.png" -heroImageAlt: "Prisma 8 Early Access" +heroImagePath: "/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/hero.svg" +heroImageAlt: "A three-step pipeline of cards: write your contract in contract.prisma, prompt your agent to run prisma-next migration plan, then ship your app with prisma-next migrate" metaImagePath: "/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx b/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx index a36aa9faed8..28f5811c6a1 100644 --- a/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx +++ b/apps/blog/content/blog/prisma-next-ltree-extension/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "Extending Prisma 8 with Typed Postgres ltree" metaDescription: "Use PostgreSQL ltree in Prisma 8 with prisma-ltree: typed path columns plus ancestor and descendant queries." heroImagePath: "/prisma-next-ltree-extension/imgs/hero.svg" -heroImageAlt: "Typed ltree for Prisma 8: the prisma-ltree extension pack shown as a hierarchical path tree" +heroImageAlt: "A typed ltree path tree on a light card: essays branches into essays.drafts and essays.published, each with a chapter leaf, above the isDescendantOf operator" metaImagePath: "/prisma-next-ltree-extension/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx b/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx index da25a35eaae..6151e5ae506 100644 --- a/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx +++ b/apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "Prisma 8 Is ~90% As Fast as Raw PG" metaDescription: "Prisma 8 performance benchmarks achieves ~90% of the raw pg driver's peak throughput, holds latency low under load, and ships as a 148.5 KB gzipped bundle for serverless and edge workloads." heroImagePath: "/prisma-next-performance-benchmark/imgs/hero.svg" -heroImageAlt: "Bar chart showing Prisma 8 outperforming Prisma 7 in throughput benchmarks" +heroImageAlt: "Peak sustained throughput bars on the same Postgres workload: the raw pg driver at 14,350 requests per second, Prisma 8 at 12,500, Prisma 7 at 8,300" metaImagePath: "/prisma-next-performance-benchmark/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx b/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx index d6e7ea92742..d1249ad8951 100644 --- a/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx +++ b/apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx @@ -7,6 +7,7 @@ authors: metaTitle: "Prisma 8: April milestone complete, the extension API is open" metaDescription: "April shipped the first four extensions on the new Prisma 8 extension API: pgvector, arktype-json, ParadeDB, and CipherStash. The extension API is open to outside authors. May shifts to Early Access." heroImagePath: "/prisma-next-roadmap-april-milestone/imgs/hero.svg" +heroImageAlt: "A milestone panel: pgvector, arktype-json, ParadeDB and CipherStash checked off as shipped in April, with streaming subscriptions in a dashed card carried into May" metaImagePath: "/prisma-next-roadmap-april-milestone/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-next-roadmap/index.mdx b/apps/blog/content/blog/prisma-next-roadmap/index.mdx index 89eec2b06a9..d48b080d436 100644 --- a/apps/blog/content/blog/prisma-next-roadmap/index.mdx +++ b/apps/blog/content/blog/prisma-next-roadmap/index.mdx @@ -6,7 +6,8 @@ authors: - "Will Madden" metaTitle: "Prisma 8 Roadmap" metaDescription: "Have you been wondering when you can start using Prisma 8 in your app? Take a look at our roadmap to find out." -heroImagePath: "/prisma-next-roadmap/imgs/hero.png" +heroImagePath: "/prisma-next-roadmap/imgs/hero.svg" +heroImageAlt: "A horizontal milestone track with three nodes: April for external contributions, May for early access, and June to July for Postgres general availability" metaImagePath: "/prisma-next-roadmap/imgs/meta.png" tags: - "orm" diff --git a/apps/blog/content/blog/prisma-orm-7-3-0/index.mdx b/apps/blog/content/blog/prisma-orm-7-3-0/index.mdx index 7e70cbdef0a..c683d6dba57 100644 --- a/apps/blog/content/blog/prisma-orm-7-3-0/index.mdx +++ b/apps/blog/content/blog/prisma-orm-7-3-0/index.mdx @@ -6,7 +6,9 @@ authors: - "Mike Hartington" metaTitle: "Prisma ORM 7.3.0: Faster Query Compilation, Safer BigInt JSON, Better Adapters" metaDescription: "Prisma ORM 7.3.0 adds a new compilerBuild option (fast or small), speeds up raw queries by bypassing compilation, improves MSSQL and better-sqlite3 stability, reverts mapped enum behavior, and preserves BigInt precision in relationJoins JSON aggregation." -heroImagePath: "/prisma-orm-7-3-0/imgs/hero-e84b7eb35dc73daddb55d22bb7a24b71f40d3d5d-844x474-552f491d83.svg" +metaImagePath: "/prisma-orm-7-3-0/imgs/meta.png" +heroImagePath: "/prisma-orm-7-3-0/imgs/hero.svg" +heroImageAlt: "A Prisma ORM 7.3.0 version badge beside four changelog items: the new compilerBuild generator option, raw queries skipping the compiler, the MSSQL adapter on version 12.2.0, and BigInt precision preserved in relationJoins JSON aggregation." tags: - "orm" --- diff --git a/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx b/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx index b0cbf869f07..6697909b9c3 100644 --- a/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx +++ b/apps/blog/content/blog/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/index.mdx @@ -6,8 +6,9 @@ authors: - "Mike Hartington" metaTitle: "Prisma ORM v7.4: Query Caching & Performance Boost" metaDescription: "Prisma ORM v7.4 introduces query caching, partial indexes, and BigInt precision fixes—delivering significant performance improvements under load." -metaImagePath: "/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/imgs/meta-e94d09878c3f2ac3e105a920dea3556ac0f9917a-1688x948-a991da7a72.png" -heroImagePath: "/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/imgs/hero-fef1bbb68459cebeece803f612fd0b95571d3d57-844x474-c0e399ac58.png" +metaImagePath: "/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/imgs/meta.png" +heroImagePath: "/prisma-orm-v7-4-query-caching-partial-indexes-and-major-performance-improvements/imgs/hero.svg" +heroImageAlt: "A Prisma ORM 7.4 release card with three named rows: query caching highlighted in cyan, with per-query compilation cost falling from 0.1-1ms to 1-10 microseconds, partial indexes behind the partialIndexes preview feature, and a typical cache hit rate near 100 percent." tags: - "orm" --- diff --git a/apps/blog/content/blog/prisma-postgres-on-stripe-projects/index.mdx b/apps/blog/content/blog/prisma-postgres-on-stripe-projects/index.mdx index 82f2e81f4dc..c47e405f1f5 100644 --- a/apps/blog/content/blog/prisma-postgres-on-stripe-projects/index.mdx +++ b/apps/blog/content/blog/prisma-postgres-on-stripe-projects/index.mdx @@ -6,8 +6,8 @@ authors: - "Sampo Lahtinen" metaTitle: "Prisma Postgres on Stripe Projects" metaDescription: "Add a Prisma Postgres database to your Stripe project with one command: spending limits out of the box, plan changes from the CLI you already use." -heroImagePath: "/prisma-postgres-on-stripe-projects/imgs/hero.png" -heroImageAlt: "Prisma Postgres on Stripe Projects" +heroImagePath: "/prisma-postgres-on-stripe-projects/imgs/hero.svg" +heroImageAlt: "A Stripe Projects provider card for prisma/database, provisioned and ready on the free plan, beside the starter, pro and business plan prices" metaImagePath: "/prisma-postgres-on-stripe-projects/imgs/meta.png" tags: - "announcement" diff --git a/apps/blog/content/blog/prisma-postgres-vs-neon-pricing-2026/index.mdx b/apps/blog/content/blog/prisma-postgres-vs-neon-pricing-2026/index.mdx index 8b414a3a3fb..2d42d76b328 100644 --- a/apps/blog/content/blog/prisma-postgres-vs-neon-pricing-2026/index.mdx +++ b/apps/blog/content/blog/prisma-postgres-vs-neon-pricing-2026/index.mdx @@ -9,7 +9,7 @@ metaTitle: "Prisma Postgres vs Neon Pricing 2026: Tables + Worked Examples" metaDescription: "Prisma Postgres vs Neon pricing side by side: per-plan tables with exact unit prices, five worked cost examples with reproducible math, and a worksheet for your own workload." heroImagePath: "/prisma-postgres-vs-neon-pricing-2026/imgs/hero.svg" metaImagePath: "/prisma-postgres-vs-neon-pricing-2026/imgs/meta.png" -heroImageAlt: "Prisma Postgres vs Neon Pricing 2026" +heroImageAlt: "A table comparing Prisma Postgres and Neon on billing unit, free tier, paid entry and top plan, using the published plan prices from the post." tags: - "education" --- diff --git a/apps/blog/content/blog/prisma-schema-as-llm-context/index.mdx b/apps/blog/content/blog/prisma-schema-as-llm-context/index.mdx index 34d08e4d4fc..7f8d1fb2795 100644 --- a/apps/blog/content/blog/prisma-schema-as-llm-context/index.mdx +++ b/apps/blog/content/blog/prisma-schema-as-llm-context/index.mdx @@ -102,9 +102,9 @@ You can test the qualitative half on your own project in five minutes. Give your All three are answerable from the schema plus the ORM's documented defaults, including the trap in the first: `Invoice.organization` declares no `onDelete`, and Prisma's default for a required relation is `Restrict`, so an organization with invoices cannot be deleted at all. To be clear about what this test shows: a single-file Drizzle schema passes it too. It separates agents that have the data model in context from agents reconstructing it from application code; the sections above are about what that context costs. -## Prisma Next treats schema-as-context as a feature +## Prisma 8 treats schema-as-context as a feature -[Prisma Next](https://www.prisma.io/docs/orm/next), the next generation of the ORM currently in early access, makes this a design goal rather than a side effect: the schema stays small, dense, and machine-readable, treated as first-class LLM context rather than an implementation detail, and errors are structured for agent consumption, carrying documentation URLs that resolve to a stable reference for the exact error. +[Prisma 8](https://www.prisma.io/docs/orm/v8), the next generation of the ORM currently in release candidate, makes this a design goal rather than a side effect: the schema stays small, dense, and machine-readable, treated as first-class LLM context rather than an implementation detail, and errors are structured for agent consumption, carrying documentation URLs that resolve to a stable reference for the exact error. The schema answers "what is the data model." The other half, "how do we change it safely here," belongs in your agent rules file; we covered a copy-pasteable version in [What to Put in Your AGENTS.md](/agents-md-for-databases). diff --git a/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx b/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx index 370b9bf395f..ca09212e72d 100644 --- a/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx +++ b/apps/blog/content/blog/prisma-studio-migrations-view/index.mdx @@ -9,7 +9,7 @@ metaTitle: "Prisma Studio Migrations View: See Your Migration History" metaDescription: "The Prisma Studio Migrations view shows every applied Prisma 8 migration as a timeline with a visual diff, the executed SQL, and a schema diff." heroImagePath: "/prisma-studio-migrations-view/imgs/hero.svg" metaImagePath: "/prisma-studio-migrations-view/imgs/meta.png" -heroImageAlt: "The Prisma Studio Migrations view: a timeline of applied migrations beside a visual diff canvas" +heroImageAlt: "The Prisma Studio Migrations panel listing six applied migrations newest first, with the destructive Drop Legacy Username entry selected" tags: - "announcement" - "orm" diff --git a/apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx b/apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx index 3b005cfcc70..ce81f70186a 100644 --- a/apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx +++ b/apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx @@ -8,8 +8,8 @@ authors: metaTitle: "Rebuilding the Prisma Docs: A New Framework, Design, and Structure" metaDescription: "Learn how the Prisma team rebuilt their docs from scratch using Fumadocs, improved search with Mixedbread, and launched without disrupting day-to-day work." metaImagePath: "/rebuilding-the-prisma-docs/imgs/meta.png" -heroImagePath: "/rebuilding-the-prisma-docs/imgs/hero.png" -heroImageAlt: "Image of the new Prisma documentation site showing the redesigned navigation and layout" +heroImagePath: "/rebuilding-the-prisma-docs/imgs/hero.svg" +heroImageAlt: "An information architecture drawing of the rebuilt Prisma docs: a versioned entry point serving /docs and /docs/v6, branching into the four top-level sections Getting Started, ORM, Prisma Postgres, and Guides." tags: - "education" - "announcement" diff --git a/apps/blog/content/blog/rethinking-database-migrations/index.mdx b/apps/blog/content/blog/rethinking-database-migrations/index.mdx index b4cc5dc62b2..848ebd728f6 100644 --- a/apps/blog/content/blog/rethinking-database-migrations/index.mdx +++ b/apps/blog/content/blog/rethinking-database-migrations/index.mdx @@ -9,7 +9,7 @@ metaTitle: "Rethinking Database Migrations" metaDescription: "Database migrations are brittle and they break when you're most vulnerable; when you're deploying to production. Prisma 8 migrations make them explicit, verifiable and safe to retry." metaImagePath: "/rethinking-database-migrations/imgs/meta.png" heroImagePath: "/rethinking-database-migrations/imgs/hero.svg" -heroImageAlt: "Rethinking Database Migrations" +heroImageAlt: "A migration history graph: an empty database leads to abc123 createTable(user), which branches to def456 addColumn(user.email) and on to the ghi789 target" tags: - "orm" series: prisma-next diff --git a/apps/blog/content/blog/search-prisma-docs-from-your-coding-agent/index.mdx b/apps/blog/content/blog/search-prisma-docs-from-your-coding-agent/index.mdx index 43cfbc9e1ac..27fca707e1e 100644 --- a/apps/blog/content/blog/search-prisma-docs-from-your-coding-agent/index.mdx +++ b/apps/blog/content/blog/search-prisma-docs-from-your-coding-agent/index.mdx @@ -6,8 +6,8 @@ authors: - "Ankur Datta" metaTitle: "Search the Prisma Docs Using Your Coding Agent" metaDescription: "The Prisma MCP server now answers documentation questions in your editor. Ask about ORM, Postgres, or Compute and get a cited answer, no tab-switching, no extra setup." -heroImagePath: "/search-prisma-docs-from-your-coding-agent/imgs/hero.png" -heroImageAlt: "Your coding agent can now search the Prisma docs" +heroImagePath: "/search-prisma-docs-from-your-coding-agent/imgs/hero.svg" +heroImageAlt: "A docs search panel for the search_prisma_documentation tool: one question about deploying to Prisma Compute, and the docs pages its cited answer comes from" metaImagePath: "/search-prisma-docs-from-your-coding-agent/imgs/meta.png" tags: - "ai" diff --git a/apps/blog/content/blog/serverless-postgres/index.mdx b/apps/blog/content/blog/serverless-postgres/index.mdx index 252e65558af..a01692736a6 100644 --- a/apps/blog/content/blog/serverless-postgres/index.mdx +++ b/apps/blog/content/blog/serverless-postgres/index.mdx @@ -11,7 +11,7 @@ metaTitle: "Serverless Postgres: How It Works and Who Offers It (2026)" metaDescription: "Serverless Postgres separates compute from storage and bills for usage instead of provisioned servers. How scale-to-zero, cold starts, and the three pricing models compare across Neon, Prisma Postgres, Supabase, Aurora, and PlanetScale." metaImagePath: "/serverless-postgres/imgs/meta.png" heroImagePath: "/serverless-postgres/imgs/hero.svg" -heroImageAlt: "Serverless Postgres providers compared: logos for Prisma Postgres, Neon, Aurora, Supabase, and PlanetScale grouped by the three pricing models — operations, compute-time, and instances. Prisma wordmark top-right." +heroImageAlt: "A compute usage curve that suspends after five minutes idle and wakes a few hundred milliseconds later, drawn under a flat always ready line." --- Serverless Postgres is PostgreSQL you never provision or manage: the platform allocates compute on demand and bills you for usage, not for a server size you picked up front. One label, though, covers very different products, and they differ on two things that decide your cost and your latency: **what they bill for**, and **whether compute sleeps when idle**. diff --git a/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx b/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx index 621d9b38ff4..03ada96366a 100644 --- a/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx +++ b/apps/blog/content/blog/ship-risky-schema-changes-without-a-shared-staging-database/index.mdx @@ -9,7 +9,7 @@ draft: true metaTitle: "Ship risky schema changes with per-branch databases" metaDescription: "Prisma Compute gives every branch its own Prisma Postgres database. Rehearse expand-and-contract migrations in isolation before they touch production." heroImagePath: "/ship-risky-schema-changes-without-a-shared-staging-database/imgs/hero.svg" -heroImageAlt: "Per-branch databases let each pull request run its own migrations in isolation" +heroImageAlt: "Two branches fork off main into separate branch databases, one adding the displayName column and one dropping the legacy name column" metaImagePath: "/ship-risky-schema-changes-without-a-shared-staging-database/imgs/meta.png" tags: - "platform" diff --git a/apps/blog/content/blog/sunsetting-prisma-optimize/index.mdx b/apps/blog/content/blog/sunsetting-prisma-optimize/index.mdx index ba39fec3c8c..d6ca4ed3a64 100644 --- a/apps/blog/content/blog/sunsetting-prisma-optimize/index.mdx +++ b/apps/blog/content/blog/sunsetting-prisma-optimize/index.mdx @@ -6,8 +6,9 @@ authors: - "Mike Hartington" metaTitle: "Sunsetting Prisma Optimize" metaDescription: "Prisma Optimize is being sunset as we move query observability directly into Prisma Postgres through Query Insights." -heroImagePath: "/sunsetting-prisma-optimize/imgs/optimize-sunset.svg" -metaImagePath: "/sunsetting-prisma-optimize/imgs/optimize-sunset@2x.png" +heroImagePath: "/sunsetting-prisma-optimize/imgs/hero.svg" +metaImagePath: "/sunsetting-prisma-optimize/imgs/meta.png" +heroImageAlt: "A dated wind-down notice: the Prisma Optimize client extension gives way to Query Insights in Prisma Postgres, with the command that removes the old package" tags: - "announcement" - "prisma-postgres" diff --git a/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx b/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx index 700c3809084..91b763c14f7 100644 --- a/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx +++ b/apps/blog/content/blog/the-next-evolution-of-prisma-orm/index.mdx @@ -7,9 +7,9 @@ authors: - "Ankur Datta" metaTitle: "The Next Evolution of Prisma ORM" metaDescription: "A look at Prisma 8, a ground-up rethink of Prisma that improves queries, extensibility, migrations, and AI-friendly workflows while keeping Prisma’s schema-first approach." -metaImagePath: "/the-next-evolution-of-prisma-orm/imgs/meta-558fe7eccfd12d3b52c325d62e5fa463a1b5f619-1200x640-3212708663.png" -heroImagePath: "/the-next-evolution-of-prisma-orm/imgs/hero-61773d2cc286213d32b63e59605b0f5e0df4fe52-844x474-cb41e2fab7.svg" -heroImageAlt: "The Next Evolution of Prisma ORM" +metaImagePath: "/the-next-evolution-of-prisma-orm/imgs/meta.png" +heroImagePath: "/the-next-evolution-of-prisma-orm/imgs/hero.svg" +heroImageAlt: "A lineage of three Prisma ORM generations: Prisma 6 shipping Rust native binaries, Prisma 7 with the query system rewritten, and Prisma 8 stepped up and outlined in cyan, rebuilt in TypeScript and extensible by default." tags: - "orm" series: prisma-next diff --git a/apps/blog/content/blog/typescript-7-native-compiler-faster-type-checking/index.mdx b/apps/blog/content/blog/typescript-7-native-compiler-faster-type-checking/index.mdx index b114ddac35f..f2827b33bee 100644 --- a/apps/blog/content/blog/typescript-7-native-compiler-faster-type-checking/index.mdx +++ b/apps/blog/content/blog/typescript-7-native-compiler-faster-type-checking/index.mdx @@ -9,7 +9,7 @@ metaTitle: "TypeScript 7 Native Compiler: 3x Faster Type Checks in a Real Monore metaDescription: "TypeScript 7 ships the compiler as a native Go port. We migrated a large TypeScript monorepo to it: whole-repo type checking went from ~74s to ~24s with no memory tuning. Here are the numbers, the exact config diffs, the sharp edges, and who should migrate now." metaImagePath: "/typescript-7-native-compiler-faster-type-checking/imgs/meta.png" heroImagePath: "/typescript-7-native-compiler-faster-type-checking/imgs/hero.svg" -heroImageAlt: "Headline 'Type checking, 3x faster' beside a before/after bar chart: a tall slate bar labeled TS 5.x at 74 seconds and a short glowing blue bar labeled TS 7 at 24 seconds, with a '3x faster' callout. TypeScript logo top-left, Prisma wordmark top-right." +heroImageAlt: "Two proportional bars comparing a whole-repo type check: tsc 5.8.2, the classic compiler, at about 74 seconds in grey, and tsc 7.0.2, the native Go compiler, at about 24 seconds in cyan with a 3x faster pill, above a note that the Node heap flag went from 8 GB to none." tags: - "education" - "platform" diff --git a/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx b/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx index 84c9ee22ced..1b6e266ac75 100644 --- a/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx +++ b/apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx @@ -7,9 +7,9 @@ authors: - "Ankur Datta" metaTitle: "TypeScript Migrations in Prisma 8" metaDescription: "In Prisma 8, migrations are TypeScript files you can read, edit, and re-run with confidence. Every step is verified before it runs and again after, and every failure points directly at the operation that caused it." -heroImagePath: "/typescript-migrations-in-prisma-next/imgs/typescript-migrations-in-prisma-next.png" -metaImagePath: "/typescript-migrations-in-prisma-next/imgs/typescript-migrations-in-prisma-next.png" -heroImageAlt: "TypeScript Migrations In Prisma 8" +heroImagePath: "/typescript-migrations-in-prisma-next/imgs/hero.svg" +metaImagePath: "/typescript-migrations-in-prisma-next/imgs/meta.png" +heroImageAlt: "A dark migration.ts code card showing the createTable, addUnique and createIndex operation factories that a Prisma 8 migration is built from" tags: - "orm" - "education" diff --git a/apps/blog/content/blog/you-dont-need-a-job-queue-postgres-already-has-skip-locked/index.mdx b/apps/blog/content/blog/you-dont-need-a-job-queue-postgres-already-has-skip-locked/index.mdx index 3c4b056460c..87c4b812e5f 100644 --- a/apps/blog/content/blog/you-dont-need-a-job-queue-postgres-already-has-skip-locked/index.mdx +++ b/apps/blog/content/blog/you-dont-need-a-job-queue-postgres-already-has-skip-locked/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "Build a Postgres Job Queue with SKIP LOCKED, No Redis" metaDescription: "Postgres can run a reliable background job queue with FOR UPDATE SKIP LOCKED. Build a worker queue with retries using pg and Prisma Postgres, no broker required." heroImagePath: "/you-dont-need-a-job-queue-postgres-already-has-skip-locked/imgs/hero.svg" -heroImageAlt: "You Don't Need a Job Queue, Postgres Already Has SKIP LOCKED" +heroImageAlt: "A dark SQL card holding the post's claim query, with FOR UPDATE SKIP LOCKED highlighted in yellow, beside the line 'The job queue is a table'." metaImagePath: "/you-dont-need-a-job-queue-postgres-already-has-skip-locked/imgs/meta.png" tags: - "prisma-postgres" diff --git a/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx b/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx index 0b00a922c09..84c6d6ba44d 100644 --- a/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx +++ b/apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/index.mdx @@ -8,7 +8,7 @@ metaTitle: "You Don't Need a Vector Database, Postgres Already Has pgvector" metaDescription: "pgvector turns Postgres into a vector store; Prisma 8 makes it type-safe. Build working semantic search on a temporary Prisma Postgres database in minutes." heroImagePath: "/you-dont-need-a-vector-database-postgres-already-has-pgvector/imgs/hero.svg" metaImagePath: "/you-dont-need-a-vector-database-postgres-already-has-pgvector/imgs/meta.png" -heroImageAlt: "You Don't Need a Vector Database, Postgres Already Has pgvector" +heroImageAlt: "The post's movie vectors plotted on the action and scifi axes, with The Terminator highlighted and lines drawn to its nearest neighbours." tags: - "prisma-postgres" - "education" diff --git a/apps/blog/content/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search/index.mdx b/apps/blog/content/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search/index.mdx index 1f699a22504..b5347c091d2 100644 --- a/apps/blog/content/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search/index.mdx +++ b/apps/blog/content/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search/index.mdx @@ -7,7 +7,7 @@ authors: metaTitle: "Postgres Full-Text Search Instead of Elasticsearch" metaDescription: "Build full-text search with tsvector, GIN indexes, and pg_trgm typo tolerance on Prisma Postgres. For most apps, no Elasticsearch cluster required." heroImagePath: "/you-dont-need-elasticsearch-postgres-already-has-full-text-search/imgs/hero.svg" -heroImageAlt: "You Don't Need Elasticsearch, Postgres Already Has Full-Text Search" +heroImageAlt: "A struck-out Elasticsearch tile above a highlighted Postgres tile labelled tsvector plus GIN index, beside the line 'The search index is a column'." metaImagePath: "/you-dont-need-elasticsearch-postgres-already-has-full-text-search/imgs/meta.png" tags: - "prisma-postgres" diff --git a/apps/blog/content/blog/you-dont-need-redis-postgres-already-has-pub-sub/index.mdx b/apps/blog/content/blog/you-dont-need-redis-postgres-already-has-pub-sub/index.mdx index 6bae207c84b..4798534bb62 100644 --- a/apps/blog/content/blog/you-dont-need-redis-postgres-already-has-pub-sub/index.mdx +++ b/apps/blog/content/blog/you-dont-need-redis-postgres-already-has-pub-sub/index.mdx @@ -6,9 +6,9 @@ authors: - "Ankur Datta" metaTitle: "You Don't Need Redis, Postgres Already Has Pub/Sub" metaDescription: "Postgres includes a lightweight Pub/Sub mechanism through LISTEN and NOTIFY. In this post, you'll build a small real-time Pub/Sub app with Bun, pg, and Prisma Postgres." -heroImagePath: "/you-dont-need-redis-postgres-already-has-pub-sub/imgs/you-dont-need-redis-postgres-already-has-pub-sub.png" -metaImagePath: "/you-dont-need-redis-postgres-already-has-pub-sub/imgs/you-dont-need-redis-postgres-already-has-pub-sub.png" -heroImageAlt: "You Don't Need Redis, Postgres Already Has Pub/Sub" +heroImagePath: "/you-dont-need-redis-postgres-already-has-pub-sub/imgs/hero.svg" +metaImagePath: "/you-dont-need-redis-postgres-already-has-pub-sub/imgs/meta.png" +heroImageAlt: "A publisher running NOTIFY app_events, fanning out through the app_events channel to two subscribers running LISTEN app_events." tags: - "education" series: postgres-features diff --git a/apps/blog/content/blog/your-database-might-not-be-the-bottleneck/index.mdx b/apps/blog/content/blog/your-database-might-not-be-the-bottleneck/index.mdx index 9deaf797262..89d09efdac7 100644 --- a/apps/blog/content/blog/your-database-might-not-be-the-bottleneck/index.mdx +++ b/apps/blog/content/blog/your-database-might-not-be-the-bottleneck/index.mdx @@ -7,7 +7,8 @@ authors: metaTitle: "Your Database Might Not Be the Bottleneck" metaDescription: "Slow APIs are not always a database problem. Here’s how request parsing, middleware, and repeated object work can become the real bottleneck before Postgres is even involved." metaImagePath: "/your-database-might-not-be-the-bottleneck/imgs/meta.png" -heroImagePath: "/your-database-might-not-be-the-bottleneck/imgs/hero.jpg" +heroImagePath: "/your-database-might-not-be-the-bottleneck/imgs/hero.svg" +heroImageAlt: "Request composition bars for the post's slow and fast apps: the query segment is the same size in both, while the slow bar fills with middleware, URL parsing and serialization." --- When an API feels slow, the database is usually the first thing people blame. That makes sense because databases often do the most expensive work in the stack: filtering, joins, sorting, counts, pagination, and serialization. If a route suddenly takes 400ms, most people immediately start looking for missing indexes. diff --git a/apps/blog/next.config.mjs b/apps/blog/next.config.mjs index 87446f7dc1c..a6a338b1783 100644 --- a/apps/blog/next.config.mjs +++ b/apps/blog/next.config.mjs @@ -201,9 +201,7 @@ const securityHeaders = [ }, ]; -const allowedDevOrigins = ( - process.env.ALLOWED_DEV_ORIGINS ?? "localhost,127.0.0.1,192.168.1.48" -) +const allowedDevOrigins = (process.env.ALLOWED_DEV_ORIGINS ?? "localhost,127.0.0.1,192.168.1.48") .split(",") .map((origin) => origin.trim()) .filter(Boolean); diff --git a/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.png b/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.png deleted file mode 100644 index 621f47d8fb9..00000000000 Binary files a/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.png and /dev/null differ diff --git a/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.svg b/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.svg new file mode 100644 index 00000000000..2a4e87919af --- /dev/null +++ b/apps/blog/public/agentic-engineering-at-prisma/imgs/hero.svg @@ -0,0 +1,79 @@ + diff --git a/apps/blog/public/agentic-engineering-at-prisma/imgs/meta.png b/apps/blog/public/agentic-engineering-at-prisma/imgs/meta.png index 4350e3dff96..f1b054d89ee 100644 Binary files a/apps/blog/public/agentic-engineering-at-prisma/imgs/meta.png and b/apps/blog/public/agentic-engineering-at-prisma/imgs/meta.png differ diff --git a/apps/blog/public/agents-md-for-databases/imgs/hero.svg b/apps/blog/public/agents-md-for-databases/imgs/hero.svg index ecc56918bc6..4be82439e62 100644 --- a/apps/blog/public/agents-md-for-databases/imgs/hero.svg +++ b/apps/blog/public/agents-md-for-databases/imgs/hero.svg @@ -1,69 +1,63 @@ - - -
|---|