Available presets
better-openclaw includes 9 presets that cover common deployment scenarios:Minimal
Services: Redis, Caddy
Memory: ~1 GB
Use case: Lightweight cache and session management
Memory: ~1 GB
Use case: Lightweight cache and session management
Creator
Services: FFmpeg, Remotion, MinIO, Redis, Caddy
Memory: ~2 GB
Use case: Media creation and video processing
Memory: ~2 GB
Use case: Media creation and video processing
Researcher
Services: Qdrant, SearXNG, Browserless, Redis, Caddy, PostgreSQL
Memory: ~2.5 GB
Use case: Research agent with vector search and web scraping
Memory: ~2.5 GB
Use case: Research agent with vector search and web scraping
DevOps
Services: n8n, PostgreSQL, Redis, Uptime Kuma, Grafana, Prometheus, Caddy
Memory: ~3 GB
Use case: Full monitoring and automation stack
Memory: ~3 GB
Use case: Full monitoring and automation stack
Content Creator
Services: Postiz, FFmpeg, MinIO, Redis, PostgreSQL, Umami, Caddy
Memory: ~2 GB
Use case: Social media scheduling with media processing
Memory: ~2 GB
Use case: Social media scheduling with media processing
AI Playground
Services: Ollama, Open WebUI, LiteLLM, AnythingLLM, Redis, Caddy
Memory: ~4 GB
Use case: Local AI experimentation with multiple models
Memory: ~4 GB
Use case: Local AI experimentation with multiple models
Coding Team
Services: Claude Code, OpenCode, Gitea, Code Server, Redis, Caddy
Memory: ~2.5 GB
Use case: AI development environment with coding agents
Memory: ~2.5 GB
Use case: AI development environment with coding agents
La Suite Meet
Services: PostgreSQL, Redis, LiveKit, La Suite Meet (backend/frontend/agents), Whisper, Ollama, Caddy
Memory: ~2 GB
Use case: Open-source video conferencing with AI agents
Memory: ~2 GB
Use case: Open-source video conferencing with AI agents
Full Stack
Services: All core services + all skill packs
Memory: ~8 GB
Use case: Everything enabled for maximum flexibility
Memory: ~8 GB
Use case: Everything enabled for maximum flexibility
Preset structure
Each preset is a JSON file that defines:Using presets
You can use presets in multiple ways:- Interactive CLI
- Non-interactive CLI
- REST API
- Web UI
The interactive wizard presents all presets as options:
Customizing presets
Presets are starting points, not rigid templates. You can customize them in several ways:Add services to a preset
Change proxy configuration
Modify after generation
After generating a stack, you can add or remove services:Listing presets
Preset vs. custom selection
When should you use a preset vs. manually selecting services?Use a preset when:
- You need a quick start for a known use case
- You want a tested, coherent stack
- You’re new to better-openclaw
- You’re deploying for CI/CD automation
Custom selection when:
- You have specific service requirements
- You’re building a unique stack
- You want to minimize resource usage
- You’re experimenting with new services
How skill packs relate to presets
Presets include skill packs that bundle related agent skills. For example:- Researcher preset → includes
research-agentskill pack - DevOps preset → includes
dev-opsskill pack - Creator preset → includes
video-creatorskill pack
Learn more
Explore how skill packs work and what they include
Creating custom presets
You can create your own presets by adding a JSON file to thepresets/ directory:
packages/core/src/presets/registry.ts.
Custom presets are useful for organizations that want to standardize their internal stacks.