Enterprise IT
Audit and back up every tenant
Snapshot, restore and account for every tenant — S3-portable backups and per-tenant usage reports.
The problem
- You need to prove where each tenant's data is, move it on demand, and recover it if a box dies.
- Finance wants a defensible per-tenant usage number, not a single blended cloud bill.
- Backup and restore that accept arbitrary paths are a classic path-traversal foot-gun in a multi-tenant system.
With OpenClawMU
- S3-compatible backup produces tenant-portable snapshots to AWS S3, MinIO, GCS or R2; restore rehydrates a tenant on any gateway. Both endpoints are path-traversal hardened.
- Per-tenant cost accounting records token usage per tenant; the report generator rolls it into per-period CSV totals against your rate card.
- Because state is per-tenant on disk, an audit is a directory, and a migration is a snapshot — not a database extraction.
How it works
Getting there, step by step.
- 1
Schedule snapshots
Back up each tenant to your S3-compatible bucket on a schedule with `openclaw tenants backup <tenant> --to s3://...`.
- 2
Test restores
Restore a tenant onto a staging gateway with `openclaw tenants restore --from s3://...` to verify recoverability.
- 3
Produce usage evidence
Generate per-tenant CSV usage reports for finance and audit.
# one gateway, many tenants
npm install -g openclaw@latest
openclaw onboard --install-daemon
# a tenant per customer / team
openclaw tenants create acmeFrequently asked
FAQ — audit and back up every tenant
Every question here is also emitted as FAQPage JSON-LD — so Google AI Overviews, Perplexity, and ChatGPT browsing extract the answers cleanly. Crawler-friendly fallback below for screen readers and bots that don't run JS.
Yes. A backup snapshots the tenant's directory to an S3-compatible bucket; restore rehydrates it on any gateway. Path-traversal protection applies to both the backup target and restore source paths.
Yes. Every model call records a token-usage row scoped to the tenant; the report generator rolls token counts against your rate card into per-period CSV totals.
Related use cases
-
Run AI assistants as a service
Offer a self-hosted AI assistant as a paid product to many customers, each isolated and independently billed.
Read → -
Give internal teams a shared gateway
One internal gateway your departments share — isolated tenants per team, admin-controlled, no data crossover.
Read → -
How isolation works
The load-bearing change vs. upstream — tokens, per-tenant directories, path-traversal hardening.
Read the deep dive →
EXFOLIATE!
Run your own gateway today.
Apache-2.0, self-hosted, no SaaS layer between you and your users. Install the CLI, create your first tenant, mint a token — you're routing traffic in 60 seconds.