feat(blog): add Compute time sync blog post

[aqrln]

Write a blog post about time synchronization in long running Compute VMs.

Summary by CodeRabbit

• Documentation
  • Added a new blog post describing how Prisma Compute maintains accurate guest wall-clock time in long-running Firecracker microVMs.
  • Explains key sources of clock drift and limitations of common in-guest time-sync approaches in minimal environments.
  • Introduces a host-assisted “better clock” method using KVM PTP to align guest time without relying on network time exchanges.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 26, 2026 3:34pm
docs	Ready	Preview, Comment	Jun 26, 2026 3:34pm
eclipse	Ready	Preview, Comment	Jun 26, 2026 3:34pm
site	Ready	Preview, Comment	Jun 26, 2026 3:34pm

[argos-ci]

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

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jun 26, 2026, 3:40 PM

[coderabbitai]

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: 74ff3f7c-5114-4514-a2bb-03e96945c0e9

📥 Commits

Reviewing files that changed from the base of the PR and between e7baf6b and dc885d1.

⛔ Files ignored due to path filters (2)

• apps/blog/public/prisma-compute-time-synchronization/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-compute-time-synchronization/imgs/meta.png is excluded by !**/*.png

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx

---

Walkthrough

Adds a new blog post with frontmatter and article text about Prisma Compute guest clock drift, the drawbacks of running NTP inside minimal microVMs, and using the host-paired KVM PTP clock to keep CLOCK_REALTIME aligned.

Changes

Prisma Compute time synchronization post

Layer / File(s)	Summary
Article content apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx	Adds frontmatter and article text describing guest time drift, why in-guest NTP is undesirable for minimal microVMs, and how /dev/ptp0 with ptp_kvm steps CLOCK_REALTIME.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 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 matches the change: a new blog post about Compute time synchronization.
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.

---

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

[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-time-synchronization/index.mdx`:
- Around line 40-42: The consumer-hardware comparison in this prose is too broad
relative to the probe’s measured drift, so either add a citation for the 10x to
50x claim or soften it to a clearly qualified estimate. Update the wording in
the blog content around the drift discussion to keep the `13.75 ms/hour` result
clearly scoped to the experiment and avoid presenting the consumer-grade
comparison as an unqualified fact.

🪄 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: be9f32cd-915e-4938-880b-012ce21b93ae

📥 Commits

Reviewing files that changed from the base of the PR and between a68fbbe and fc4dd23.

⛔ Files ignored due to path filters (2)

• apps/blog/public/prisma-compute-time-synchronization/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-compute-time-synchronization/imgs/meta.png is excluded by !**/*.png

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx

[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-time-synchronization/index.mdx`:
- Around line 28-30: The `LoadSnapshot` paragraph in
`prisma-compute-time-synchronization` conflates `clock_realtime: true` with
`VMClock` support; update the wording to clearly separate these features. In the
relevant prose around `clock_realtime` and `VMClock`, state that
`clock_realtime: true` is x86_64-only and requires host Linux 5.16+, while
`VMClock` has its own partial support in recent Firecracker releases, limited to
snapshot-safety/restore-detection rather than broad clock drift handling. Keep
the feature/version matrix precise and avoid the current blanket statement about
restore detection support.

🪄 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: 822d60a2-0984-4247-8370-78e96140485b

📥 Commits

Reviewing files that changed from the base of the PR and between 47ea829 and e7baf6b.

⛔ Files ignored due to path filters (2)

• apps/blog/public/prisma-compute-time-synchronization/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-compute-time-synchronization/imgs/meta.png is excluded by !**/*.png

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-compute-time-synchronization/index.mdx