Small-Server Operations
Posts and guides for teams that care about self-hosted error tracking on modest infrastructure: SQLite, VPS sizing, error storms, low-end hardware, backups, and operational readiness.
Browse by topic
- Product updates: release notes and product changes across Telebugs versions.
- Migration and compatibility: Sentry-compatible workflows, provider switching, source maps, and alternatives.
- Small-server operations: SQLite, VPS capacity, low-resource deployments, and error-storm guardrails.
- AI and MCP: MCP access, API work, and connected tooling for debugging workflows.
- Practical engineering: implementation notes, production lessons, and small technical walkthroughs.
Operations guides
- Low-resource error tracking for small VPS, ARM, and constrained environments.
- Installation expectations for server, DNS, TLS, backups, and updates.
- Installation readiness checklist for go-live ownership and validation.
- Self-hosted error tracking for the broader operating model.
Telebugs Thrives on SQLite
Why Telebugs leans into SQLite: one app, one server, database-backed jobs and cache, simple backups, and fewer moving parts.
Telebugs 1.18.0: Guardrails for Error Storms
Ingest Protection, Maintenance Activity, and load testing for keeping a small instance steady when errors spike.
How Many Errors Can Telebugs Process on a Small VPS?
A benchmark on a Hetzner CX23 and why processed reports per second is more useful than accepted HTTP requests.
Telebugs 1.7.0: Improved performance on low-end hardware
Lower memory use, faster queries, and maintenance UX for smaller machines.
Telebugs 1.2.0: Timezone fixes, ARM64 support, and auto-refresh on first error
ARM64 Docker support, timezone fixes, first-error refresh behavior, and early self-hosting improvements.