The short version
Peren is built for the whole platform.
Looking for a celld alternative? Peren gives platform teams one self-hosted runtime for Workers, Durable Objects, queues, workflows, AI, vector indexes and provider-backed data services. Run it on a VPS, bare-metal fleet or Kubernetes and operate it through the Peren CLI.
celld focuses on deploying supported Wrangler projects into a trusted application fleet. Peren takes a broader operator-first approach, with explicit configuration, host-controlled capabilities and documented compatibility boundaries across the platform.
Side by side
Peren and celld, side by side
| Area | Peren | celld |
|---|---|---|
| Project setup | Import Wrangler, AWS SAM or Serverless configuration into Peren TOML. Anything that needs attention is called out during migration. | Deploy directly from Wrangler JSON or JSONC. Wrangler TOML is not supported. |
| Runtime | Runs JavaScript and WebAssembly in V8 isolates. | Runs JavaScript in V8 isolates and supports WebAssembly modules. |
| Platform services | Includes queues, workflows, scheduled work, AI, vector indexes, analytics, service bindings, dispatch, Hyperdrive metadata and WebSockets. | Includes Durable Objects, KV, Queues, D1, R2, Workflows, Cron Triggers, static assets and dynamic Workers. |
| Durable state | Each cell has SQLite-backed state. Leases and ownership epochs fence stale writers, while snapshots and WAL records support recovery. | Each Durable Object has a private SQLite database, with leases and ownership epochs coordinating the fleet. |
| Storage | Use a configured provider that passes Peren’s conditional-write and ranged-read checks. | Use S3-compatible storage, Google Cloud Storage or Azure Blob Storage, subject to celld’s qualification checks. |
| Compatibility | Clearly documents where support is full, limited or unavailable across runtime APIs, bindings and providers. | Targets Cloudflare Workers behavior and documents unavailable features, limits and observable differences. |
| Trust boundary | Scopes services by tenant, project and service, with capabilities supplied through the host. | Runs one trusted application per fleet, with separate fleets providing the boundary between applications. |
| Networking | Controls outbound access through host-owned capabilities. You provide public TLS and keep the peer port private. | You provide public TLS and protect the internal listener with a trusted private network or encrypted overlay. |
| Kubernetes | Checks deployment assumptions and renders reviewable Helm values without applying them to the cluster. | Runs under an external supervisor such as Kubernetes, systemd or Docker with a restart policy. |
Built into Peren
Bring the services your Workers already expect
Peren keeps runtime APIs and provider-backed bindings in one operator-controlled system, with the limits of each surface documented before you deploy.
Queues and workflows
Build background processing with queues, workflows, scheduled work and Durable Object alarms.
Data and search
Connect Workers to KV, D1-compatible SQL, R2-style object storage, cache and vector indexes.
AI and services
Use AI provider bindings, service bindings, dispatch namespaces, analytics and Hyperdrive metadata through configured providers.
Real-time and outbound
Run WebSockets and connect to external services through allowlisted fetch, client mTLS or host-owned AWS SigV4 signing.
Decision guide
Why teams choose Peren
Build on Peren when
- You want runtime, durable state, application services and fleet operations in one system.
- You want an explicit fleet configuration that is easy to review.
- You are moving from Wrangler, AWS SAM or Serverless and want migration issues surfaced clearly.
- You want the host to control outbound capabilities and provider access.
celld may fit when
- Your project already uses Wrangler JSON or JSONC and you want to deploy it directly.
- celld supports a Cloudflare API or binding your application needs.
- You want its direct S3-compatible, Google Cloud Storage or Azure Blob storage path.
- Your deployment is one trusted application per fleet.
Try the migration
See what Peren can preserve
Run the migration locally. Peren writes supported equivalents and reports fields, flags or bindings that need a decision before you deploy.
peren migrate ./app fleet.toml --from wrangler
peren config validate fleet.tomlBuild with Peren
Go from comparison to implementation
Questions
Peren and celld FAQ
Is Peren a celld alternative?
Yes. Both are open-source, self-hosted runtimes for Workers and durable state. They differ in configuration, compatibility, storage integrations, trust boundaries and fleet operations.
Can either run an existing Workers project unchanged?
celld deploys supported Wrangler JSON or JSONC projects directly. Peren imports Wrangler configuration into Peren TOML and identifies fields that need your input. Review each runtime's compatibility guide for the APIs and bindings your project uses.
How do their trust models differ?
Peren can scope services by tenant and project within a fleet. celld defines one trusted application per fleet and uses separate fleets as the application boundary. Choose the model that matches how you plan to separate workloads and infrastructure.
How should I evaluate storage?
Both runtimes depend on specific object-store behavior for ownership and recovery. Run the supplied storage checks against the provider and endpoint you plan to use in production.
Start with Peren
Run your first Worker. Keep control as the platform grows.
Install the CLI, create a fleet configuration and move from one machine to a production fleet without changing who owns the runtime or the data.
celld is referenced for product comparison. Peren is not affiliated with or endorsed by the celld project.