Limits

Intentional constraints so you do not plan on a Cloudflare-shaped roadmap that will not ship inside cellp.

Product boundary

You might want	cellp
Signup, orgs, SSO, RBAC	No — two tokens
Git host, GitHub App, PR comments	No — CI calls HTTP
DNS, ACME, CDN, WAF, DDoS	No — your LB
Global edge PoPs	No — your region, your machines
Next.js / Node serverless	No
Hosted cellp cloud	No — you run the binary

Runtime (celld)

You might want	Status
Workers AI, Vectorize, Hyperdrive	No
Browser Rendering, Email Workers, Python Workers	No
Full Cloudflare KV/R2/Queue/DO/Workflows	Partial — see Compatibility
Native Component (native-http-v1)	Experimental 0.x — Wasmtime only; inbound HTTP + vars + KV; no D1/R2/Queue/DO/outbound HTTP/Native WebSocket — Native Component
wrangler tail	No
R2 object manager	No
Workflow pause/resume/restart	No
Wake-on-request for archived versions	No in v1 (explicit wake)

Scale (v1 honesty)

• Ready versions have no small hard cap; idle ones archive to drop processes.
• Registry is SQLite. Fine for a serious single-node (or VIP) control plane; not a multi-region consensus product.
• Deep health returns 503 when the deploy queue is past CELLP_QUEUE_MAX.
• POST /versions returns 503 queue_full when the queue is saturated.
• Very large multi-tenant registry stress beyond SQLite scope is out of v1 honesty for this release.

Elastic replicas (unsupported internal scaffold; default off)

CELLP_ELASTIC_RUNTIME currently exposes only an unsupported internal E1–E5 scaffold. It does not deliver a remote HTTP+mTLS Node Agent, real celld lifecycle management, a Scheduler or complete 0→N scaling, and it is not production-ready. Leave it disabled for supported deployments: every ready version maps to one celld process. POST …/wake applies only to archived versions, not a future “cold but not archived” elastic state.

Data plane

• Child versions should fork a seed/staging parent, not casually fork prod.
• Destroyed versions cannot be rolled back.
• Local celld watch dirs are cache. S3/RustFS is durable.

What we do guarantee as the product

• Isolated runtime per ready version
• Preview and production URL shapes (Host ingress)
• D1/KV/R2/Queue branch on children
• Promote saga + re-promote rollback
• REST + Dashboard over the same API
• Self-host without AWS/Cloudflare accounts