Self-hosting
A self-hosted cronpad is one process (the cronpad binary or container) and a data directory; there is no other service to run. All durable data is in two SQLite files on a local volume, backed up continuously with Litestream, next to a third, rebuildable SQLite file that holds the delivery queue. Self-hosted servers have every feature, no usage limits, and can run shell commands and call services on private networks.
| Step | Page |
|---|---|
| Install with Docker, Compose, Kubernetes or a binary | Installation |
| Every setting and its environment variable | Configuration reference |
| Google and GitHub sign-in | Authentication |
| Continuous backups and restores | Backups with Litestream |
| Before you rely on it | Production checklist |
| Moving to a new version | Upgrading |
| Metrics, logs, traces | Observability |
Requirements
| Minimum | Comfortable for ~1,000 runs/s | |
|---|---|---|
| CPU | 1 vCPU | 4 vCPU |
| Memory | 256 MB | 2 GB |
| Disk | 1 GB local SSD | Local NVMe, sized for your retention; the queue adds ~100 bytes per active job |