Operate Web Fleet

Self-hosting

Web Fleet is being built to remain comfortable on one ordinary VPS or home server even after larger deployment options exist.

Default deployment

┌─────────────────────────────┐
│ webfleet                    │
│  ├── HTTP/dashboard         │
│  ├── monitor scheduler      │
│  └── crawler workers        │
└──────────────┬──────────────┘
               │
            SQLite

Analytics ingestion is implemented in development and remains optional.

That integrated shape is the default. It should not be treated as a toy deployment.

SQLite and PostgreSQL

SQLite keeps installation and backup simple for small/medium deployments. A PostgreSQL storage path is implemented in development for larger installations and enterprise requirements. The remaining product gate is the first-run database chooser and live PostgreSQL parity testing. See First-run setup.

Optional process separation

# Future large-deployment shape
webfleet serve
webfleet worker
webfleet analytics-ingest

These commands would use the same product and configuration model. They are not intended to become a mandatory microservice topology.

Backups and upgrades

Backup/restore and Linux service update/rollback paths are implemented in development and remain public-preview hardening gates. See Hosting and deployment for the intended server shape.