From 33e278e0af22a8d5393e7674eb95e9561a001af6 Mon Sep 17 00:00:00 2001 From: Luan van der Westhuizen Date: Thu, 25 Jun 2026 11:29:14 +0200 Subject: [PATCH] fix(blog): link pricing post to workload form --- .../content/blog/price-the-work-not-the-workflow/index.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/apps/blog/content/blog/price-the-work-not-the-workflow/index.mdx b/apps/blog/content/blog/price-the-work-not-the-workflow/index.mdx index 0eebb6ff01..14d0b71b04 100644 --- a/apps/blog/content/blog/price-the-work-not-the-workflow/index.mdx +++ b/apps/blog/content/blog/price-the-work-not-the-workflow/index.mdx @@ -245,8 +245,10 @@ 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. Tell us where these meters match -how you actually build, and where they do not. +now in public beta and free during this time. [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. Read the [Compute pricing docs](https://www.prisma.io/docs/compute/pricing) and follow the [Prisma Compute series](https://www.prisma.io/blog/series/prisma-compute)