
OpenClaw (Coolify build)
https://github.com/coollabsio/openclaw- Category
- Developer Tools
- Rank
- No. 1052Tools index
Previous survey · No. 1046 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- coollabsio
- GitHub
- 397 stars
- Date
About
Fully featured and automated OpenClaw docker images maintained by the Coolify team for easy self-hosting.
What it does
Packages the OpenClaw gateway behind an nginx proxy, then turns environment variables into persistent JSON configuration at startup. It supports hosted and local model providers, messaging channels, webhook triggers, and an optional browser sidecar whose authenticated sessions survive restarts.
Why it's ranked here
A practical deployment wrapper with unusually broad configuration coverage. Persistent state, provider selection, proxy authentication, browser access, and channel setup share one container workflow. The main concern is operational sharpness: security settings are optional, while documentation and startup behavior disagree about gateway token generation.
What's good
Configuration layers cleanly: custom JSON forms the base, persisted state merges over it, and environment variables take precedence. Removed provider variables can clean stale provider entries. The merge logic blocks prototype-pollution keys, nginx handles WebSocket upgrades, and dedicated volumes preserve projects, tools, browser sessions, and credentials.
Tradeoffs
Startup requires a gateway token and at least one provider credential or local model endpoint. Basic authentication remains optional, so omitting its password leaves nginx unprotected. Direct LAN binding bypasses nginx authentication. The browser feature needs a separate Chromium container, substantial shared memory, and manual login for protected sites. Advanced group rules remain JSON-only.
How to use it well
Best for operators who want one reproducible host for an OpenClaw gateway, messaging channels, webhooks, and authenticated browser automation. Pin the upstream source reference when building, persist both application and browser volumes, set explicit gateway and HTTP credentials, and restrict allowed origins. It does not supply model inference itself unless connected to Ollama; otherwise you still need external provider credentials.
Technical notes+
Dockerfile.base clones upstream source, installs dependencies with pnpm, builds the application and UI, then constructs a Node 22 runtime with Linuxbrew, Go, uv, and build tools. Dockerfile adds nginx and scripts/entrypoint.sh, which validates credentials, runs scripts/configure.js, applies doctor fixes, generates proxy configuration, and launches the gateway. scripts/configure.js merges custom JSON, persisted configuration, and environment overrides while rejecting unsafe merge keys. scripts/utils.test.js exercises coercion, origin parsing, merge safety, and dot-notation parsing. docker-compose.yml adds persistent application storage and the browser image built by Dockerfile.browser.
Observed
- Packaging
- Two-layer Docker build with separate base, final gateway, and optional Chromium sidecar images.
- Install surface
- Runs through Docker directly or Docker Compose, with published container images referenced by the examples.
- Interfaces
- Web control UI, bearer-authenticated gateway, webhook endpoints, and proxied browser desktop.
- Platform support
- Automated image workflow defines builds for amd64 and arm64.
- Implementation
- Deployment logic primarily uses JavaScript, Bash, Dockerfiles, nginx configuration, and YAML workflows.
- Tests
- Repository includes a dependency-free JavaScript utility test suite and a command-line smoke check.
Read from README.md, scripts/smoke.js, scripts/utils.js, scripts/configure.js, scripts/utils.test.js, CLAUDE.md, Dockerfile, .env.example, Dockerfile.base, Dockerfile.browser, docker-compose.yml, docker-compose.local.yml, scripts/build.sh, scripts/entrypoint.sh, .github/workflows/build.yml.
What it can do
Deploy OpenClaw applications using Docker containers
OpenClaw application code and configuration → Running containerized OpenClaw instance
Automate container image building and maintenance
Source code updates and build triggers → Updated Docker images with latest OpenClaw features
Enable self-hosted OpenClaw deployment
Server infrastructure and Docker environment → Self-managed OpenClaw installation
Simplify OpenClaw installation and setup
Basic server configuration requirements → Fully configured OpenClaw environment
Manage OpenClaw application lifecycle
Deployment commands and configuration updates → Updated or restarted OpenClaw services
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.