Databases and application backends
Managed PostgreSQL through Vitibase, managed Redis on Replov, or any external database
Vitibase
Vitibase is a separate Supabase-like backend platform that Replov works with. Each project provisions an isolated PostgreSQL stack with generated REST APIs, authentication, file storage, realtime changes, and PgBouncer connection pooling.
Create a Vitibase projectManaged PostgreSQL from a Replov project
Replov can create a Vitibase PostgreSQL database for a project and manage it for you. Databases run in AWS Asia Pacific (Mumbai) and are billed by Replov from your wallet, hourly or monthly, with GST added on top of the database price.
- Ask an AI agent connected through the MCP connector to add a Postgres database (
provision_resource), or approve an infrastructure plan that includes one. You see the price and confirm before anything is created. - Each app that uses the database gets its own database login, injected as
DATABASE_URLon its next deployment. Connections use TLS through the connection pooler. - The project page lists its databases under Databases (Vitibase), with Open in Vitibase Studio for tables, auth and storage.
- Deleting a database requires typing its name. Vitibase keeps the data for 7 days, then purges it.
Use an existing Vitibase project
Copy the connection details from Vitibase and store them as Replov environment variables. Use the exact names expected by your application.
DATABASE_URL=postgresql://USER:PASSWORD@HOST:PORT/DATABASEVITIBASE_URL=https://YOUR_PROJECT_HOSTVITIBASE_ANON_KEY=YOUR_PROJECT_ANON_KEY
Replov Redis
Redis is the native managed datastore in Replov. It provides persistent storage, a private Redis endpoint on your project network, metrics, and a sandboxed command console in the dashboard. It is billed by tier, like any Replov service, starting at Micro.
Other external databases
Replov can run an application that connects to any network-reachable database through that database's official driver. Replov does not provision or manage MySQL, MongoDB, Qdrant, or other external database products, so their availability, backups, scaling, and support remain the provider's responsibility.