feat(blog): add Prisma Compute custom domains post

[rtbenfield]

Adds a Prisma Compute launch blog post explaining how custom domains work, why the setup uses one DNS record, and what trade-offs come with that simplicity.

Validation

• pnpm --filter blog check passed with 0 errors.
• The command reports 8 existing unrelated warnings in blog source files.

Summary by CodeRabbit

• Documentation
  • Added a blog post on Prisma Compute custom domains: end-user setup (add domain, create CNAME, activation), automated TLS via ACME http-01 (vs dns-01 and apex handling), certificate/key storage protections, routing and encrypted certificate selection, and the expected seamless user experience.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 12, 2026 12:24pm
docs	Ready	Preview, Comment	Jun 12, 2026 12:24pm
eclipse	Ready	Preview, Comment	Jun 12, 2026 12:24pm
site	Ready	Preview, Comment	Jun 12, 2026 12:24pm

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fb3a484b-1204-4302-bbee-8a4eda2e50e8

📥 Commits

Reviewing files that changed from the base of the PR and between f9a293f and dd477d7.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-compute-custom-domains/index.mdx

✅ Files skipped from review due to trivial changes (1)

• apps/blog/content/blog/prisma-compute-custom-domains/index.mdx

---

Walkthrough

Adds a new MDX blog post documenting Prisma Compute custom domains: user DNS/CNAME setup, ACME http-01 certificate issuance and trade-offs (including apex handling), encrypted certificate/key storage design, request routing with an encrypted certificate cache, and a brief conclusion.

Changes

Custom Domains Documentation

Layer / File(s)	Summary
Post frontmatter and metadata apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Adds MDX frontmatter (title, slug, date, authors, SEO, hero image, tags, series).
User-facing domain setup flow apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Documents domain addition via API/CLI/Console, create CNAME, DNS verification, TLS provisioning, and CLI monitoring/retry behavior.
ACME http-01 issuance and apex handling apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Explains automated TLS via ACME http-01, trade-offs with dns-01, DNS cutover considerations, and apex-domain support via CNAME-flattening/backing-record resolution.
Certificate/key storage and encryption apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Describes per-service encryption keys, master-key–protected encryption-at-rest, and sensitive in-memory/wrapped handling of private keys and certificates.
Request routing and encrypted certificate cache apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Documents domain→service mapping, certificate selection and on-demand decryption, and use of an encrypted certificate cache to avoid per-request overhead.
Conclusion and infra components apps/blog/content/blog/prisma-compute-custom-domains/index.mdx	Summarizes the intended uneventful UX and enumerates infrastructure pieces (ACME, encryption, routing, caching).

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a new blog post about Prisma Compute custom domains. It accurately reflects the primary objective of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	⚠️ Changes detected (Review)	1 changed	Jun 12, 2026, 12:30 PM

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/blog/content/blog/prisma-compute-custom-domains/index.mdx`:
- Around line 27-32: Update the user-facing step list in the blog content:
clarify that adding a custom domain requires an existing production app with a
promoted, live deployment (replace or augment the "Add a custom domain to a
Prisma Compute service..." line to state this prerequisite) and replace the
current "Deploy your service" step with a step that instructs the user to wait
for DNS propagation and TLS provisioning (e.g., "Wait for the domain to become
active — DNS verification and TLS provisioning happen automatically; use app
domain wait to monitor status"). Ensure the phrasing matches the flow described
in apps/docs/content/docs/compute/domains.mdx and that the terms "app domain
wait", "CNAME record", and "production app with a promoted, live deployment"
appear so readers can correlate steps.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e0ae71e9-716e-4f09-abbf-dc5c66f28f84

📥 Commits

Reviewing files that changed from the base of the PR and between 0ef6b0c and 15dddd9.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-compute-custom-domains/index.mdx