DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to self-host actors on a Celld fleet with Tardigrade

Deploy the same Worker entrypoint to your own Celld fleet with an S3 bucket.

Credentials. The storage bucket and fleet credentials give write access to actor data, so scope them tightly and avoid committing them.

Who it is forA platform engineer who must run agent actors on infrastructure they control instead of Cloudflare.

The problemTeams that cannot use a hosted edge platform need the same actor model on their own fleet with shared storage.

The outcomeActors running on a self-hosted Celld fleet, using a storage bucket for their data.

What you need first

  • Bun installed, since the README uses bunx and bun add
  • Working knowledge of TypeScript
  • A model and credentials configured for the generated project
  • A Cloudflare account for Cloudflare hosting, or a Celld fleet with a storage bucket for self-hosting

Steps

  1. Read the Celld guide at docs/platforms/celld.mdx for configuration and credentials.
  2. Create a celld.jsonc config for your fleet and set your bucket credentials.
  3. Run celld deploy --config celld.jsonc --bucket s3://actors with your own bucket name in place of actors if different.
  4. Confirm the deployed actors respond at the endpoint your Celld configuration exposes.

Prompt for your agent

In the repo clavia-labs/tardigrade, follow docs/platforms/celld.mdx to write a celld.jsonc for <fleet-name>, then run `celld deploy --config celld.jsonc --bucket s3://<bucket-name>`. Expected output: a deployment summary from celld. Verify that the same Worker entrypoint from createActorWorker is used and that the bucket credentials are read from the environment, not committed to the repo.

Caveat. The README links to a Celld project for its docs, so the exact celld.jsonc fields are not covered here and must come from the Celld guide.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page