Startups & MVPs
Before traction, every rupiah spent on infrastructure is a rupiah not spent building the product. Start on one small instance and one managed database, then add capacity only when the usage graph forces it — not when a capacity plan predicts it.
A Real Story
How this runs in production
Four people, one B2B product, and nine months of runway. The Rapor.id team needed genuinely separate production and staging environments on an infrastructure budget smaller than one junior salary.
They started with a single production instance and a staging box a cron job shuts down every night. The managed database was there from day one — not because the scale demanded it, but because nobody could be spared to run backups.
- first-month bill
- Rp415rb
- from zero to production
- 12 mnt
- of ops per week
- 0 jam
We ran the whole product on two instances for nine months. What saved us was not the price — it was never once staying up late over a backup.
Reference Architecture
Exactly what they run
The plan names below are the same ones listed on the pricing page.
- Virtual Machines2.small × 2One production, one staging that shuts down nightly.
- Managed Databaseg2.mediumManaged PostgreSQL, 7-day PITR, no DBA.
- Object Storage120 GBUser attachments and backups, billed per GB.
What You Get
Built for this workload
Hourly billing
Shut staging down overnight and stop paying for it.
Resize without migrating
Add CPU and RAM to the same instance when traffic arrives.
A managed database from day one
Backups and failover stop being work deferred until an incident.
Built From