Integration · RuntimeScale FastClaw with PostgreSQL
Swap FastClaw's default SQLite file for PostgreSQL to run multiple pods behind a load balancer, with automatic schema migrations.
One env var
Set FASTCLAW_STORAGE_TYPE=postgres and FASTCLAW_STORAGE_DSN — users, agents, sessions, API keys and configs move with it.
Auto-migrate
Schema migrations run on boot by default; turn them off with FASTCLAW_STORAGE_AUTO_MIGRATE=false.
Multi-pod ready
Combine Postgres with an S3-compatible object store and Redis to run several replicas on Kubernetes.
What you can do
- Serve many tenants from one horizontally scaled deployment — see FastClaw for SaaS builders.
- Back the runtime API with a database your team already operates and backs up.
Set it up
FASTCLAW_STORAGE_TYPE=postgres
FASTCLAW_STORAGE_DSN="$DATABASE_URL" # a standard postgres:// connection string
For several replicas, also set FASTCLAW_REDIS_ADDR (channel leases and the shared message stream) and the FASTCLAW_OBJECT_STORE_* variables for skill and file hydration. The FastClaw repo includes Kubernetes manifests under deploy/k8s/ and a Compose file that pairs FastClaw with Postgres — see Docker.
Notes
There is no config file: bootstrap settings come from FASTCLAW_* env vars, and everything else lives in the database.
Frequently asked questions
More Integrations
All IntegrationsE2B
Run every FastClaw agent command in an isolated E2B cloud sandbox — skills and workspace hydrated in, files synced back after each call.
Docker
Use Docker as FastClaw's sandbox backend to isolate agent commands on your own hardware — or deploy FastClaw itself with Docker Compose.
MCP
Give FastClaw agents external tools through the Model Context Protocol — add http or stdio MCP servers per agent from the console.
Try it on your own agents
Start free in FastClaw Cloud, or self-host the single binary in a minute.