Agent frameworksMemory & context

Celld

denoland/celld

Self-hosted distributed Durable Objects using S3/GCS as the only control plane.

Repository
Stars
1.5k
Forks
95
Open issues
8
Language
Rust
Licence
MIT
Created
2026-07-25
Last push
2026-08-16
Effort to adopt

Some wiring

A few days of integration work — credentials, data mapping, a deploy target.

01

What it actually does

Celld brings Cloudflare's magical 'Durable Objects' architecture to your own infrastructure. It allows you to create stateful, distributed actor models (like AI agents that remember their state forever) without needing to run a complex database or Kubernetes cluster. Amazingly, it uses standard S3 or Google Cloud Storage (GCS) buckets as its entire control plane and state store. You just run `celld` on any server, point it at a bucket, and you instantly have distributed, globally synchronized agent memory.

02

Who it's for

  • 01

    Engineers building massive multi-agent simulations who need a cheap, reliable way to store agent state

  • 02

    Teams migrating away from expensive vendor lock-in who want self-hosted Durable Objects

  • 03

    Startups wanting to deploy stateful AI applications to edge nodes (like Raspberry Pis or cheap VPSs)

EngineeringOperationsSaaSAny industry
03

Where it earns its keep

  • Hosting 10,000 persistent AI companion agents where each agent's memory is simply a Celld actor backed by S3
  • Building a decentralized chat application where chat rooms are stateful objects living on edge nodes
  • Creating a multiplayer game backend without writing complex Redis or Postgres synchronization logic
04

Use it, or skip it

Reach for it when

  • You are building a system where millions of AI agents need isolated, persistent memory states
  • You want the developer experience of Durable Objects without being locked into Cloudflare

Skip it when

  • You are building a standard CRUD application where Postgres works perfectly fine
  • You need ultra-low latency microsecond reads—S3 as a control plane is highly durable but not built for high-frequency trading
05

10 automations

  1. 01Sales

    Persistent Customer AI Twins

    Assign a unique Celld object to every customer. The object permanently remembers every support ticket and purchase, acting as their hyper-personalized AI concierge.

  2. 02Operations

    Global Fleet Tracker

    Use Celld actors to represent physical delivery trucks, constantly updating their state and routes backed securely to S3.

  3. 03Engineering

    Multi-Agent Simulation Orchestrator

    Run a massive economy simulation where 100k agent personas trade resources, with Celld handling all state synchronization flawlessly.

  4. 04Engineering

    Stateful Webhook Queues

    Create a reliable, distributed queue system for handling massive influxes of webhooks from third-party APIs.

  5. 05Operations

    Edge-computed Analytics

    Process real-time stream data on cheap edge VPS instances, aggregating state into Celld objects before pushing to cold storage.

  6. 06Engineering

    Decentralized Chat Rooms

    Spin up Celld instances on various servers worldwide to host localized, high-availability chat rooms for enterprise clients.

  7. 07Operations

    Smart Home Hub Backends

    Represent every smart device in a network as a Celld object, tracking historical sensor data without a heavy local database.

  8. 08Engineering

    AI Game NPCs

    Give video game NPCs permanent memories and dynamic state by running them as Celld actors.

  9. 09Engineering

    Distributed Web Scraper Memory

    Coordinate a fleet of 500 web scraping agents, using Celld to ensure they don't scrape the same URLs twice.

  10. 10Operations

    Document Processing Pipeline

    Track the multi-stage OCR and extraction status of thousands of legal documents across various worker nodes.

Want one of these running by Friday?

LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.

Book a workflow call
07

Source

Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with denoland.

https://github.com/denoland/celld