Storage - Replov Docs
Skip to main content

Storage

Choose storage according to the service that owns the data

Application containers are replaceable
Do not store critical user data only in a web, private, worker, cron, or static service container. A deployment, recreation, or host operation can replace that filesystem. Use a volume, Redis or Vitibase for data that must survive.

Volumes

Persistent files for a web service, private service or worker, mounted at a path you choose (for example /data). Survives redeploys and restarts.

Redis persistence

A Replov Redis keeps its data on Replov's storage disk, separate from application containers. Use it for caching, sessions, rate limits, queues and other Redis-compatible state.

Vitibase Storage

Use Vitibase when an application needs PostgreSQL-backed records, user authentication, file buckets, or realtime changes. Manage that data in the Vitibase dashboard.

Volumes

  • Size: 1 to 100 GB per volume (50 GB per account in total). The size is a hard limit: writes beyond it fail. You can grow or shrink a volume at any time without a restart; it cannot shrink below what it holds.
  • Price: ₹15 per GB per month, charged hourly from your wallet for the size you chose, from creation until the volume is deleted, whether or not it is attached.
  • Attach and detach: attaching or detaching restarts the app once; it is not rebuilt. One app can have several volumes at different paths.
  • Deleting the app: its volumes are kept, detached, with their data, and stay billed until you delete them.
  • Deleting a volume: permanently deletes its data. Its existing backups can still be restored for up to 7 days.
  • Where: volumes live on Replov's storage disk in Bangalore (BLR1). It is a single disk, not replicated; backups are what protect against losing it.

AI agents connected through the Replov MCP connector can request a volume (they show you the price first and act only after you approve), and inspect, expand, detach or delete it; deleting needs a second confirmation with the volume's exact name.

Backups

  • What: every Redis on Micro or above, and every volume whose app is on Micro or above, is backed up once a day, about 02:00 India time. Volumes of Nano apps are not backed up.
  • How long: each backup is kept for 7 days. A restore brings back the data as it was at that backup, so up to a day of changes can be lost; there is no point-in-time recovery.
  • Where and how: encrypted before it leaves the server and stored in a different region (Singapore) from the live data, with a checksum verified on restore.
  • Restore: the project owner or a team admin restores from the dashboard. Stop the app (or Redis) first and type its name to confirm. The data it replaces is kept for 7 days.
  • Consistency: a volume backup copies files while the app runs. Files being written at that moment can be captured mid-change; for databases, use Vitibase or your database's own dump in addition.

Review Vitibase's current dashboard and plan terms before relying on its backup features. For data you cannot afford to lose, keep your own exports as well.