Planned
C
Cloudflare Pages
Static frontend deployment for fast global delivery.
Infrastructure
Designed for Cloudflare-native deployment.
Kaymai is planned around a lightweight, scalable, and secure architecture that can grow from a static public website to a full AI workflow platform.
Intended architecture
This is planned infrastructure direction. Kaymai does not claim Cloudflare program approval or partnership.
Planned
C
Cloudflare Workers
Planned backend APIs and workflow execution at the edge.
Planned
C
Cloudflare R2
Planned object storage for files, media, and generated outputs.
Planned
C
Cloudflare D1
Planned structured data layer for workflow metadata.
Planned
C
Cloudflare AI / AI Gateway
Planned AI-assisted processing, model routing, and observability.
Planned
C
Cloudflare security tools
Planned protection, DNS, analytics, and application security.
Architecture flow
From frontend to workflow output.
The intended architecture keeps the public site static while future workflow services can move through edge APIs, AI processing, storage, metadata, and dashboard review.
Step 1
Frontend
Step 2
Worker API
Step 3
AI processing
Step 4
R2 storage
Step 5
D1 metadata
Step 6
Dashboard output
S
Static-first public site
The current website remains static and deployable to Vercel or Cloudflare Pages without a backend service.
E
Edge-ready product path
Future product APIs are intended to use edge runtime patterns where they make sense for workflow execution.
S
Security-conscious growth
The platform direction prioritizes protected uploads, controlled access, and clear operational boundaries as product scope expands.