Introduction
celld-operator is a Kubernetes operator that turns
celld, Deno Land's open-source daemon for
running Cloudflare Workers and Durable Objects on your own machines, into a complete
self-hosted platform. One WorkerApp custom resource provisions and operates a
full celld fleet: workload, networking, security policy, ingress, gated rollouts,
metrics, and autoscaling.
Why an operator?
celld deliberately ships with no account service, no multi-tenant scheduler, and no managed ingress. Its own limitations page says so plainly: a fleet runs one application, and everything around it is your problem. celld supplies the runtime and the data plane; celld-operator supplies the control plane, built almost entirely from Kubernetes-native objects, without patching celld itself.
That last part is a design constraint, not an accident. celld moves fast and its
operator API is explicitly alpha, so the operator's celld-facing surface stays thin:
environment variables, signals, the public health path
(/.well-known/celld/health), the internal /state endpoint, and,
for appVersion: auto, the bucket's deploy/current.json pointer.
Core concepts
| Concept | Meaning |
|---|---|
| Cell | A Durable Object: a small named server with a private SQLite database. One cell per user, document, chat room, or AI agent. Exactly one node serves a cell at a time, fenced by conditional writes to the bucket. |
| Fleet | A set of celld nodes sharing one bucket prefix and serving one application. On Kubernetes, a fleet is a StatefulSet of celld pods. |
| Bucket | The object store (an S3-compatible bucket, a Google Cloud Storage bucket, or an Azure Blob Storage container) that holds deployments, per-cell SQLite data, ownership and node leases, and the peer-authentication secret. The bucket is the source of truth; nodes are replaceable. |
| WorkerApp | The custom resource this operator reconciles. One WorkerApp = one fleet = one application. Tenancy lives at the Kubernetes layer: each app gets its own namespace-scoped resources, bucket prefix, and credentials. |
What the operator gives you
- Fleet provisioning: a hardened StatefulSet, Services, a ServiceAccount, a NetworkPolicy, a PodDisruptionBudget, and (when Istio is present) a mesh AuthorizationPolicy, all derived from one resource. See Architecture.
- Ingress: hostnames routed through Gateway API, classic Istio, or plain Ingress, with drain-aware retry policy where the ingress can express it. See Networking & ingress.
- Gated rollouts: one pod at a time, stepping only when every pod is Ready and the whole fleet reports
restoring=0, with breaking celld upgrades refused unless you ask for a Recreate. See Deploying updates. - Autoscaling: KEDA ScaledObjects driven by resident-cell utilization metrics the operator itself exports, gated on fresh, complete samples. See Autoscaling.
- Observability: celld's built-in tracing wired to your bucket or your OTLP collector, plus Prometheus metrics for capacity, memory, and self-fencing. See Observability.
- Guardrails: operator-level allowlists for images, cloud identities, and bucket endpoints, immutable bucket identity, and an honest per-fleet tenancy model. See Security.
What it is not
This is a platform for your applications, or your customers' applications under your operation. It is not a public PaaS for anonymous hostile code: celld's security documentation states it is not safe for hostile multi-tenant use, and the operator does not pack untrusted tenants into shared celld nodes. WorkerApp authors are trusted workload deployers. The unit of tenancy is a fleet (two to three pods minimum for high availability), not an isolate.
The operator also does not fill Cloudflare platform gaps itself. celld v0.6.2 runs Workers, Durable Objects, KV, Queues, D1, Workflows, R2 bindings, cron triggers, and static assets; it does not run Workers AI, Vectorize, Hyperdrive, Browser Rendering, or Email Workers. The compatibility matrix lists the details, and gaps fail loudly at deploy time or first use.
Status: alpha. celld v0.6.2 is a beta release, and this operator
tracks it release-for-release. Upstream ships security fixes for its latest release
only, and the operator's support policy mirrors that. The API group is
celld-operator.io/v1alpha1 and may change. Read the
production operation guide
before running a fleet you care about.
Where to go next
- Install the operator: Helm or kustomize, trust allowlists, and optional integrations.
- Quick start: from a Wrangler project to a converged fleet.
- Architecture: why everything is the way it is.
- WorkerApp reference: every field, default, and condition.