Decision D20 · 20 of 21
L2 hosting (new)
Self-managed Postgres + Timescale on EC2 until 10 plants, then Tiger Cloud
RECOMMENDED
- Status
- RECOMMENDED — awaiting Vinayak
- Recommendation
- Self-managed Postgres with TimescaleDB on one EC2 instance in ap-south-1 (EBS gp3, daily snapshots, WAL archive to S3) for up to about 10 plants. Move to Tiger Cloud in its Mumbai region with an HA replica when any trigger fires: more than 10 live plants, a customer asks for an availability commitment, or the team spends more than two days a month on database operations.
- Why
- L2 depends on TimescaleDB (hypertables, compression, continuous aggregates). Amazon RDS for PostgreSQL does not offer the timescaledb extension, so the RDS line in the pilot cost note cannot run L2 as built. EC2 is the cheapest correct option; managed Timescale buys HA when it is worth the price.
- Evidence
- AWS RDS supported-extension list (checked 7 Oct 2026); Tiger Cloud pricing page; L2 migrations 001–017.
- Reversible
- Yes. Both are Postgres; migration is dump and restore or logical replication.
- Blocks
- Running-cost estimate (
scripts/pricing/stamped_running_cost.pyandSTAMPED_RUNNING_COST_ESTIMATE.md, built from the sizing table below), deployment profiles, backup and restore runbook.
Page history: last 2 changes
- docs(research): retire stale research to archive/research-2026-10 with a register
ab84821 - docs(technical): split decision board into DECISIONS.md
b4db9d4