Cloudflare Workers & Pages Inventory

This document tracks all Cloudflare Workers and Pages projects used by the PREGO platform. Update when adding, renaming, or removing projects.

English

Workers

Dashboard name	*.workers.dev	Git repository	Wrangler config	Production domain	Notes
admin-web	admin-web.kinybaik.workers.dev	Pregoi/Prego	apps/admin-web/wrangler.jsonc	m.pregoi.com	OpenNext; tenant onboarding & admin shell
control-plane	control-plane.kinybaik.workers.dev	Pregoi/prego-control-plane	wrangler.toml	(Zuplo upstream)	D1, Stripe, provision orchestration
prego-ai	prego-ai.kinybaik.workers.dev	Pregoi/prego_ai	wrangler.toml (workers)	(Zuplo upstream)	My AI / Autopilot / Knowledge
prego-ai-operator	prego-ai-operator.kinybaik.workers.dev	Pregoi/prego_ai	workers-operator/wrangler.toml	—	Internal operator tooling
prego-mcp-server	prego-mcp-server.kinybaik.workers.dev	Pregoi/prego_ai (or separate)	TBD	—	MCP server for AI integrations

Pages

Dashboard name	*.pages.dev	Git repository	Build output / root	Production domain	Notes
platform-devdoc	platform-devdoc.pages.dev	Pregoi/Prego	docs/dist (Starlight)	devdoc.pregoi.com (if configured)	Internal engineering docs (brand-neutral)
marketing-web	marketing-web.pages.dev	Pregoi/Prego	apps/marketing-web/out	www.pregoi.com	Marketing / trial gate
leekimdocs	leekimdocs.pages.dev	(No Git connection)	—	—	Personal / experimental; consider account separation

Brand neutrality status

Project	Current name	Neutral?	Action
admin-web	admin-web	Yes	None
control-plane	control-plane	Yes	None
employee-web	employee-web	Yes	None
platform-devdoc	platform-devdoc	Yes	Migrated from prego-devdoc
marketing-web	marketing-web	Yes	None
prego-ai	prego-ai	No	Managed in separate repo (prego_ai)
prego-ai-operator	prego-ai-operator	No	Managed in separate repo (prego_ai)
prego-mcp-server	prego-mcp-server	No	Managed in separate repo (prego_ai)

Renaming procedure (Workers)

1. Update name in wrangler.toml / wrangler.jsonc.
2. Update CI workflow files (project name, service bindings).
3. Deploy creates new Worker; old name remains until deleted.
4. Update custom domain routing (Cloudflare dashboard or Terraform/Pulumi).
5. Delete old Worker after traffic shifts.

Renaming procedure (Pages)

Cloudflare Pages projects cannot be renamed. To change project name:

1. Create new Pages project with desired name.
2. Connect same Git repo with same build settings.
3. Add custom domain to new project.
4. Delete old project after DNS propagates.

---

한국어

PREGO 플랫폼에서 사용하는 Cloudflare Workers 및 Pages 프로젝트 레지스트리. 프로젝트 추가·이름 변경·삭제 시 갱신한다.

Workers

대시보드 이름	*.workers.dev	Git 저장소	Wrangler 설정	프로덕션 도메인	비고
admin-web	admin-web.kinybaik.workers.dev	Pregoi/Prego	apps/admin-web/wrangler.jsonc	m.pregoi.com	OpenNext; 테넌트 온보딩·관리자 셸
control-plane	control-plane.kinybaik.workers.dev	Pregoi/prego-control-plane	wrangler.toml	(Zuplo 업스트림)	D1, Stripe, 프로비전 오케스트레이션
prego-ai	prego-ai.kinybaik.workers.dev	Pregoi/prego_ai	wrangler.toml (workers)	(Zuplo 업스트림)	My AI / Autopilot / Knowledge
prego-ai-operator	prego-ai-operator.kinybaik.workers.dev	Pregoi/prego_ai	workers-operator/wrangler.toml	—	내부 운영 도구
prego-mcp-server	prego-mcp-server.kinybaik.workers.dev	Pregoi/prego_ai (또는 별도)	TBD	—	AI 통합용 MCP 서버

Pages

대시보드 이름	*.pages.dev	Git 저장소	빌드 출력 / 루트	프로덕션 도메인	비고
platform-devdoc	platform-devdoc.pages.dev	Pregoi/Prego	docs/dist (Starlight)	devdoc.pregoi.com (설정 시)	내부 엔지니어링 문서 (브랜드 중립)
marketing-web	marketing-web.pages.dev	Pregoi/Prego	apps/marketing-web/out	www.pregoi.com	마케팅 / 트라이얼 게이트
leekimdocs	leekimdocs.pages.dev	(Git 연결 없음)	—	—	개인/실험용; 계정 분리 고려

브랜드 중립화 상태

프로젝트	현재 이름	중립?	조치
admin-web	admin-web	예	없음
control-plane	control-plane	예	없음
employee-web	employee-web	예	없음
platform-devdoc	platform-devdoc	예	prego-devdoc에서 마이그레이션 완료
marketing-web	marketing-web	예	없음
prego-ai	prego-ai	아니오	별도 리포(prego_ai)에서 관리
prego-ai-operator	prego-ai-operator	아니오	별도 리포(prego_ai)에서 관리
prego-mcp-server	prego-mcp-server	아니오	별도 리포(prego_ai)에서 관리

이름 변경 절차 (Workers)

1. wrangler.toml / wrangler.jsonc 의 name 수정.
2. CI 워크플로 파일 수정 (프로젝트명, 서비스 바인딩).
3. 배포하면 새 Worker 생성; 구 이름은 삭제 전까지 유지.
4. 커스텀 도메인 라우팅 업데이트 (Cloudflare 대시보드 또는 Terraform/Pulumi).
5. 트래픽 전환 후 구 Worker 삭제.

이름 변경 절차 (Pages)

Cloudflare Pages 프로젝트는 이름 변경 불가. 변경하려면:

1. 원하는 이름으로 새 Pages 프로젝트 생성.
2. 동일 Git 저장소·빌드 설정 연결.
3. 새 프로젝트에 커스텀 도메인 추가.
4. DNS 전파 후 구 프로젝트 삭제.

---

---

Zuplo Gateway Audit

OAS Title Convention

OpenAPI fragments in prego-zuplo/config/*.oas.json use product branding in info.title:

Fragment	Title	Intentional?
01-gateway-parameters	Gateway — shared parameters	Yes (neutral)
02-08 auth-worker-*	Prego Security API	Yes (product)
09-10 auth-zuplo-*	Prego Auth API	Yes (product)
11-billing	Prego Billing API	Yes (product)
12-tenant	Prego Tenant API	Yes (product)
13-14 onboarding-*	Prego Onboarding API	Yes (product)
15-trial-access-*	Prego Trial Access (...)	Yes (product)
20-control-plane-*	Prego Control Plane (...)	Yes (product)
22-attendance-*	Prego Attendance API	Yes (product)
26-email	Prego Email API	Yes (product)
27-business-core-*	Prego Business Core API	Yes (product)

Decision: OAS titles use the product name “Prego” per Product naming & identities. This is the canonical public API name for customers. No neutralization needed for product-facing documentation.

Zuplo Cloud UI (manual audit)

Check in the Zuplo dashboard:

1. Project display name: Visible in Zuplo console project selector.
2. Developer Portal title: Public-facing portal branding.
3. Portal URL: Custom domain if any.

Fork policy:

• When forking the platform, update OAS info.title values to the new product name.
• Consider using a placeholder pattern like {{PRODUCT_NAME}} in CI build if multiple forks share the same repo.
• Update Zuplo portal settings manually in the dashboard after fork.

---

Pending verification (prego_ai repository)

When cloning Pregoi/prego_ai beside this monorepo, verify and document:

1. Main Worker (prego-ai):

   • Path: wrangler.toml or wrangler.jsonc in repo root or workers/
   • Check name field matches dashboard
   • List service bindings to other Workers

2. Operator Worker (prego-ai-operator):

   • Path: workers-operator/wrangler.toml
   • Verify name and bindings

3. MCP Server (prego-mcp-server):

   • May be in same repo or separate
   • Document location and config path

4. Zuplo routing:

   • Check if modules/ reference these Worker names
   • Update OAS descriptions if Worker names change

5. Brand neutralization decision:

   • Decide on neutral names (e.g., ai-worker, ai-operator, mcp-server)
   • Or keep prego-* if product branding is intentional
   • Document decision in this inventory

---

Related

• Fork checklist — Cloudflare account IDs, zone names, Worker names.
• Environment variable neutralization plan — PREGO_* → neutral name migration.
• Product naming & identities — Canonical service name, domain, legal entity, GitHub org.
• Pages project migration — How to rename a Pages project.