Skip to content

docs: add Enterprise AI Vibe Coding Platform reference architecture#31215

Open
melhuang12 wants to merge 6 commits into
cloudflare:productionfrom
melhuang12:mel/enterprise-vibe-coding-platform
Open

docs: add Enterprise AI Vibe Coding Platform reference architecture#31215
melhuang12 wants to merge 6 commits into
cloudflare:productionfrom
melhuang12:mel/enterprise-vibe-coding-platform

Conversation

@melhuang12
Copy link
Copy Markdown
Contributor

This PR adds a new reference architecture page for enterprise AI vibe coding platforms, extending the existing AI Vibe Coding Platform page with enterprise controls.

New page: /reference-architecture/diagrams/ai/enterprise-ai-vibe-coding-platform/

Covers three architecture planes:

  • Development plane: Access with SSO integration, AI Gateway governance, container execution, outbound handler egress
  • Deployment pipeline: Artifacts/git storage, code review integration, CI/CD
  • Production plane: Workers for Platforms with per-app bindings, custom limits, two-level observability, application registry

Includes four interactive Astro diagram components and an interactive overview diagram on the base vibe coding platform page.

Melody Huang and others added 6 commits June 3, 2026 18:40
- New page: enterprise-ai-vibe-coding-platform.mdx covering development
  service, deployment pipeline, production service, and security model
- New component: VibePlatformOverview.astro interactive diagram replacing
  static SVG on the base vibe coding platform page
- Register VibePlatformOverview in components/index.ts
- Update ai-vibe-coding-platform.mdx to use the interactive component
- VibeCoreDiagram: three-column overview of dev, pipeline, prod planes
  with cross-cutting observability/cost/tagging bar
- VibeDevPlaneDiagram: four-column flow from Access ingress through
  execution paths and AI governance to outbound worker egress
- VibeDeployPipelineDiagram: four-stage pipeline from dev output through
  storage, review, and deployment to Workers for Platforms
- VibeProdPlaneDiagram: three-column flow from Access+dispatch ingress
  through user workers to outbound worker egress with Hyperdrive/VPC/Tunnel
- Register all four components in index.ts
- Clean up enterprise MDX page text and embed diagrams in sections
- VibeCoreDiagram: three clickable boxes with arrows, cross-cutting bar
- VibeDevPlaneDiagram: Access -> container (frontend/agent, sandbox SDK,
  D1 metadata, AI Gateway for LLM calls, MCP Portal for tool calls) ->
  outbound worker
- VibeDeployPipelineDiagram: dev output -> storage (artifacts/git) ->
  review (code review, security, CI/CD) -> deploy (WFP)
- VibeProdPlaneDiagram: Access boundary wrapping dispatch worker ->
  user worker -> outbound worker flow
- All tiles show service names only, descriptions on hover
- Sandbox SDK and Containers merged into single component
…limits, and observability

- Development plane: metadata storage now lists D1, KV, and Durable
  Objects as options, queried by frontend or agent flow
- Production plane: per-app bindings via upload API for complete
  resource isolation per user worker
- Production plane: custom limits (cpuMs, subRequests) set at dispatch
  worker level to prevent compute abuse
- Production plane: two-level observability model with platform-wide
  Logpush and per-app Tail Workers + Analytics Engine
- Dev plane diagram: rebuilt as horizontal three-box layout
@cloudflare-docs-bot
Copy link
Copy Markdown

cloudflare-docs-bot Bot commented Jun 3, 2026

Review

✅ No style-guide issues found in commit 83714d3.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants