Clawdinators
github.com/openclaw/clawdinators- Category
- Developer Tools
- Rank
- No. 1375Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- openclaw
- GitHub
- 158 stars
- Date
About
Declarative infrastructure plus NixOS modules for CLAWTINATOR hosts — reproducible servers configured for the OpenClaw agent stack.
What it does
Clawdinators is a retired reference system for operating coding agents on AWS. It builds NixOS machine images, provisions EC2 hosts, injects encrypted secrets during boot, and starts agents that watch GitHub and answer maintainers through chat. Multiple hosts can share persistent memory, while a separate control path dispatches infrastructure changes through GitHub Actions.
Why it's ranked here
The repository is valuable as a worked infrastructure design, not as a ready production tool. It documents image creation, host configuration, secret delivery, shared state, token refresh, and controlled replacement together. However, the fleet is decommissioned, deployment workflows are disabled, and several architecture documents describe planned or draft behavior.
What's good
The strongest idea is strict separation between disposable agent hosts and durable state. Images and locked Nix inputs define machines, agenix keeps plaintext secrets out of the repository, and shared storage preserves memory across replacements. The control design also keeps deployment credentials outside agents, routes changes through auditable automation, and explicitly blocks self-deployment.
Tradeoffs
Operating this design requires Nix familiarity, AWS credentials, OpenTofu, encrypted secret material, chat bot tokens, model provider keys, and GitHub App access. Image import is slow, cache misses can delay releases, and service switching causes brief downtime. Fleet size is constrained by unique Discord tokens. Most importantly, the documented deployment automation is intentionally disabled.
How to use it well
Use it as a study base for NixOS image provisioning, disposable AWS hosts, runtime secret injection, or maintainer-only coding agents. Borrow individual patterns and validate them against current dependencies before production use. It fits teams already committed to Nix and AWS. It does not provide a hosted service, active fleet, general agent scheduler, elastic scaling system, or turnkey installation.
Technical notes+
flake.nix exports nixosModules.clawdinator, overlays, packages for x86_64-linux and aarch64-linux, and four NixOS configurations, while host system builds are limited to x86_64-linux. devenv.nix supplies nixos-generators, AWS CLI, curl, and OpenTofu. infra/opentofu/aws is the documented AWS provisioning surface. docs/SECRETS.md specifies agenix files, S3 bootstrap bundles, and short-lived GitHub App tokens. control/api/handler.js implements a Lambda handler that authenticates requests, rejects self-deployment, and dispatches a GitHub Actions workflow. docs/DEPLOYMENT_MODEL.md and AGENTS.md state that former image and release workflows reside under .github/workflows-disabled/ and require explicit operator action. README.md declares the project retired and the authoritative fleet registry empty.
Observed
- License
- MIT License
- Implementation stack
- Nix and NixOS configuration, OpenTofu infrastructure, shell tooling, and a JavaScript AWS Lambda handler
- Packaging surface
- A Nix flake exports a NixOS module, overlays, gateway packages, host configurations, and system builds
- Deployment platform
- AWS EC2 provisioned from imported NixOS AMIs, with S3 bootstrap storage and optional shared EFS memory
- Interfaces
- Discord and optional Telegram chat channels, GitHub monitoring, a NixOS module, and an authenticated control API
- Architecture support
- Flake packages cover x86_64-linux and aarch64-linux; declared host configurations use x86_64-linux
- Project status
- Retired historical reference implementation with deployment workflows disabled and an empty fleet registry
Read from README.md, docs/POC.md, docs/SECRETS.md, docs/PHILOSOPHY.md, docs/ARCHITECTURE.md, docs/SKILLS_AUDIT.md, docs/CONTROL_PLANE.md, docs/SHARED_MEMORY.md, docs/DEPLOYMENT_MODEL.md, docs/PUBLIC_S3_PR_INTENT.md, control/api/handler.js, LICENSE, AGENTS.md, flake.nix, devenv.nix.
What it can do
Configure OpenClaw agent stack servers
Server specifications and requirements → Configured servers with OpenClaw agent stack
Deploy declarative infrastructure
Infrastructure configuration files → Deployed infrastructure resources
Apply NixOS modules to hosts
NixOS module definitions and target hosts → Configured NixOS systems
Create reproducible server configurations
Server requirements and environment specifications → Reproducible server setup configurations
Manage CLAWTINATOR host environments
Host configuration parameters → Managed and configured CLAWTINATOR hosts
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.