Managed Redis on Replov
Skip to main content
Back to home

Managed datastore

Redis for your Replov applications

Create a Redis service, connect over the private project network, and inspect usage without maintaining the container yourself.

What is included

Standard Redis protocol

Use established Redis clients and libraries from your web services and workers.

Private project networking

Keep the Redis protocol endpoint off public ingress and connect from services in the same project.

Dashboard visibility

Review memory, command, and network samples, then use the sandboxed console for supported operations.

How deployment works

  1. 1

    Create a Redis service in the project dashboard and select an available compute plan.

  2. 2

    Wait for Replov to provision Redis, generate credentials, and attach the private project network.

  3. 3

    Redeploy the services that use it: each one receives REDIS_URL on its next deployment.

  4. 4

    Confirm connectivity, set expiry and memory policies for your workload, and monitor usage.

Pricing

Billed by compute tier, from Micro.

Redis uses the same tiers as other services, starting at Micro. Command counts stay visible for operations analysis and add no per-command fee. See pricing for current tier prices; the dashboard shows the exact price before you confirm.

Frequently asked questions

What does Replov manage?

Replov provisions the Redis container, credentials, project networking, usage collection, and service lifecycle. Your application still owns its data model, expiry rules, and recovery strategy.

How is Redis charged?

A Redis is billed by its compute tier, like any Replov service, starting at Micro (1 vCPU, 1 GB, ₹599 per 30 days). There is no Nano Redis and no per-command fee. New paid resources start with a 3-day trial; the dashboard shows the exact price before you confirm.

How do applications connect?

Linked services receive a REDIS_URL environment variable on their next deployment and connect over the private project network. An optional authenticated HTTP endpoint is available for supported Redis commands.

Which workloads fit Redis?

Common uses include caching, sessions, rate limits, queues, pub/sub, counters, and short-lived application state.

Add Redis to your project

Review the live plan and usage rates in the dashboard before confirming the service.