Workers Deployment Status

This document tracks the deployment status of all Cloudflare Workers in the Prego monorepo.

English

Currently Deployed Workers

Worker	Dashboard Name	Status	Bindings	Notes
apps/admin-web	admin-web	Deployed	Assets, R2 (admin-cache), Service	OpenNext; tenant onboarding & admin shell
apps/employee-web	employee-web	Deployed	Assets, R2 (employee-cache, static-assets), Service	OpenNext; employee portal

Note: control-plane Worker is deployed from the separate prego-control-plane repository.

Undeployed Workers (Code Only)

These Workers have wrangler configuration but are not yet deployed to Cloudflare:

Email System

Worker	Purpose	Bindings	Deployment Decision
email-queue-gateway	HTTP POST → Queue producer	Queue (email-queue)	Deploy when email system goes live
mail-sender	Queue consumer → Resend API	Queue (email-queue)	Deploy with email-queue-gateway

Usage & Billing

Worker	Purpose	Bindings	Cron	Deployment Decision
workers/usage-writer	Usage events → R2	R2 (usage-raw)	—	Phase 2 (usage metering)
workers/usage-aggregator	R2 → D1 rollups	D1, R2	*/15 * * * *	Phase 2 (usage metering)
workers/cycle-close	Billing cycle close	D1	0 0 1 * *	Phase 2 (billing overage)

Infrastructure

Worker	Purpose	Bindings	Cron	Deployment Decision
workers/autoscaler	Health Score, Scale Out/In	D1	*/10 * * * *	Phase 3 (auto-scaling)
workers/tenant-router	Hostname → KV → proxy	KV (TENANT_ORIGINS)	—	Phase 3 (multi-tenant routing)
workers/purge-job	PDPA Hard Purge	D1, R2	0 2 * * *	Phase 3 (data retention)

Legacy / Deprecated

Worker	Purpose	Status
workers/control-plane	Stub for control-plane	Deprecated — use prego-control-plane repo
apps/auth-worker	JWT authentication, OTP	Review — may be integrated into Zuplo or control-plane

Configuration Notes

D1 Database ID Placeholder

Workers using D1 have placeholder IDs that must be replaced before deployment:

database_id = "REPLACE_WITH_D1_DATABASE_ID"

Use the production main-db ID: d354c923-bd21-4b13-b32c-a7f8b52a4eb1

KV Namespace ID Placeholder

tenant-router has a placeholder KV ID:

id = "REPLACE_WITH_KV_NAMESPACE_ID"

Create namespace with: wrangler kv namespace create "TENANT_ORIGINS"

---

한국어

현재 배포된 Workers

Worker	Dashboard 이름	상태	바인딩	비고
apps/admin-web	admin-web	배포됨	Assets, R2 (admin-cache), Service	OpenNext; 테넌트 온보딩 & 관리자 셸
apps/employee-web	employee-web	배포됨	Assets, R2 (employee-cache, static-assets), Service	OpenNext; 직원 포털

참고: control-plane Worker는 별도 prego-control-plane 저장소에서 배포됨.

미배포 Workers (코드만 존재)

다음 Workers는 wrangler 설정이 있으나 아직 Cloudflare에 배포되지 않음:

이메일 시스템

Worker	용도	바인딩	배포 결정
email-queue-gateway	HTTP POST → Queue 프로듀서	Queue (email-queue)	이메일 시스템 가동 시 배포
mail-sender	Queue 컨슈머 → Resend API	Queue (email-queue)	email-queue-gateway와 함께 배포

사용량 & 빌링

Worker	용도	바인딩	Cron	배포 결정
workers/usage-writer	사용량 이벤트 → R2	R2 (usage-raw)	—	Phase 2 (사용량 측정)
workers/usage-aggregator	R2 → D1 롤업	D1, R2	*/15 * * * *	Phase 2 (사용량 측정)
workers/cycle-close	빌링 주기 마감	D1	0 0 1 * *	Phase 2 (초과 요금)

인프라

Worker	용도	바인딩	Cron	배포 결정
workers/autoscaler	헬스 스코어, Scale Out/In	D1	*/10 * * * *	Phase 3 (자동 스케일링)
workers/tenant-router	호스트명 → KV → 프록시	KV (TENANT_ORIGINS)	—	Phase 3 (멀티테넌트 라우팅)
workers/purge-job	PDPA 하드 삭제	D1, R2	0 2 * * *	Phase 3 (데이터 보존)

레거시 / 폐기 예정

Worker	용도	상태
workers/control-plane	control-plane 스텁	폐기 — prego-control-plane 리포 사용
apps/auth-worker	JWT 인증, OTP	검토 필요 — Zuplo 또는 control-plane에 통합 가능

설정 참고사항

D1 데이터베이스 ID 플레이스홀더

D1을 사용하는 Workers는 배포 전 플레이스홀더 ID를 교체해야 함:

database_id = "REPLACE_WITH_D1_DATABASE_ID"

프로덕션 main-db ID 사용: d354c923-bd21-4b13-b32c-a7f8b52a4eb1

KV 네임스페이스 ID 플레이스홀더

tenant-router는 플레이스홀더 KV ID가 있음:

id = "REPLACE_WITH_KV_NAMESPACE_ID"

네임스페이스 생성: wrangler kv namespace create "TENANT_ORIGINS"

---

Related

• Cloudflare inventory — Workers & Pages project registry.
• Cloudflare migration checklist — Resource creation and data migration status.