Small VPS framing for Epure error tracking
Two containers on a small VPS. Quote RAM only with a dated named-box receipt. Sentry self-host guidance is a 16 GB class machine.
On this pageShowHide
Who this is for
Engineers who already use Sentry SDKs for exceptions, can SSH and edit Compose, and do not need session replay, APM, or profiling on the same box.
Framing rules
- Never headline an undated single idle MiB number.
- Quote about 82 MiB only with the 2026-09-12 Docker Desktop receipt, or quote the 2026-09-23 about 53 MiB VPS row.
- Small VPS means a shared low-price box in practice. Verify CPU steal and disk yourself.
- Flood behavior is a different lab: Spike valve.
Dated receipts
2026-09-23
- Host
- 2 vCPU / 769 MiB Linux VPS (Alibaba Cloud)
- Combined idle
- ~53 MiB
2026-09-12
- Host
- Docker Desktop (dev machine)
- Combined idle
- ~82 MiB app + Postgres
| Dimension | Host | Combined idle |
|---|---|---|
| 2026-09-23 | 2 vCPU / 769 MiB Linux VPS (Alibaba Cloud) | ~53 MiB |
| 2026-09-12 | Docker Desktop (dev machine) | ~82 MiB app + Postgres |
Full split and method are on the Sentry self-hosted RAM lab.
Method and the per-container split: Sentry self-hosted RAM.
Install path
Practical runbook: Cheap VPS install and verify. Topology: Two-container.
Questions
Is 512 MB enough?
The 2026-09-23 host was a 769 MiB class box at about 53 MiB idle. That is not a guarantee for your workload. Re-measure under your event rate.
Why not self-host full Sentry on a small VPS?
Public self-host guidance is about 16 GB for Sentry's broader stack. Different job.