# Who Maintains the denoland/celld Repository: Complete 2025 Guide

> Discover who maintains the denoland/celld repository. Learn about the Deno Land team and Ryan, the primary contact for contributions in this 2025 guide.

- Repository: [Deno/celld](https://github.com/denoland/celld)
- Tags: getting-started
- Published: 2026-09-05

---

**The denoland/celld repository is maintained by the Deno Land team, with Ryan (ry@deno.com) serving as the canonical point of contact for contributions and maintenance.**

The **celld** project is an open-source daemon designed for deploying and running durable JavaScript/TypeScript workloads at the edge. This article explains who maintains the repository, how to reach them, and how the project is structured for contributors.

## Who Maintains denoland/celld

The **denoland/celld** repository is maintained by the **Deno Land team**, with specific oversight from **Ryan**, a core member of the Deno organization.

According to the repository's README at [[`README.md`](https://github.com/denoland/celld/blob/main/README.md)](https://github.com/denoland/celld/blob/main/README.md), the official contact for contributions is:

> "Send a `git format-patch` attachment to ry@deno.com."【/cache/repos/github.com/denoland/celld/main/README.md†L20-L22】

This makes Ryan the primary maintainer responsible for reviewing patches, coordinating releases, and guiding the project's development direction on behalf of **Deno Land, Inc.**

## Project Governance and Licensing

The celld project operates under clear governance:

- **License**: Apache-2.0 — permissive for commercial and non-commercial use
- **Contribution model**: Patch-based via email to `ry@deno.com` rather than pull requests
- **Organization**: Backed by Deno Land, Inc., the company behind the Deno runtime

## How celld Works: Core Usage Examples

To understand what the Deno Land team maintains, here are typical **celld** commands as implemented in the source:

```bash

# Run a local celld node (no external bucket needed)

celld dev

```

```bash

# Deploy a Worker bundle to a shared bucket

celld deploy . --bucket s3://my-cells-bucket

```

```bash

# Start a fleet node that serves the deployed application

celld \
  --bucket s3://my-cells-bucket \
  --listen 0.0.0.0:8080 \
  --internal-listen 10.0.0.12:8081 \
  --advertise node-a.internal:8081

```

The CLI entry point is implemented in [[`crates/celld/main.rs`](https://github.com/denoland/celld/blob/main/crates/celld/main.rs)](https://github.com/denoland/celld/blob/main/crates/celld/main.rs), which parses these commands and delegates to the core logic in [[`crates/logic/lib.rs`](https://github.com/denoland/celld/blob/main/crates/logic/lib.rs)](https://github.com/denoland/celld/blob/main/crates/logic/lib.rs).

## Key Source Files Maintained by the Team

| File | Purpose |
|------|---------|
| [[`README.md`](https://github.com/denoland/celld/blob/main/README.md)](https://github.com/denoland/celld/blob/main/README.md) | Project description, installation, and maintainer contact |
| [[`Cargo.toml`](https://github.com/denoland/celld/blob/main/Cargo.toml)](https://github.com/denoland/celld/blob/main/Cargo.toml) | Workspace configuration and dependency management |
| [[`crates/celld/main.rs`](https://github.com/denoland/celld/blob/main/crates/celld/main.rs)](https://github.com/denoland/celld/blob/main/crates/celld/main.rs) | Binary entry point and CLI implementation |
| [[`crates/logic/lib.rs`](https://github.com/denoland/celld/blob/main/crates/logic/lib.rs)](https://github.com/denoland/celld/blob/main/crates/logic/lib.rs) | Durable object behavior, replication, and scheduling |

## How to Contribute to denoland/celld

Since Ryan maintains the repository, contribution follows a specific workflow:

1. **Prepare your changes** in a local Git clone
2. **Format patches** using `git format-patch`
3. **Email to ry@deno.com** with the patch attachment

This email-based workflow differs from typical GitHub pull requests and reflects the project's preference for thoughtful, complete contributions over rapid iteration.

## Summary

- **denoland/celld** is maintained by the **Deno Land team** with **Ryan** as primary contact
- Reach the maintainer at **ry@deno.com** for contributions
- The project uses **Apache-2.0 licensing** and email-based patch submission
- Core source files are organized as a Rust workspace with clear separation between CLI and logic crates

## Frequently Asked Questions

### Who is the main maintainer of denoland/celld?

**Ryan** is the canonical maintainer, reachable at `ry@deno.com`. He oversees contributions and maintenance on behalf of Deno Land, Inc.

### How do I contribute to the celld project?

Send a `git format-patch` attachment to `ry@deno.com` rather than opening a GitHub pull request. This email-based workflow is explicitly documented in the repository's README.

### What license does denoland/celld use?

The project is released under the **Apache-2.0 license**, a permissive open-source license that allows commercial use, modification, and distribution with proper attribution.

### Is celld related to the Deno runtime?

Yes. The **celld** daemon is maintained by **Deno Land, Inc.**, the same organization that develops the Deno JavaScript/TypeScript runtime. It extends Deno's capabilities for edge deployment scenarios.