Managed Cache

A Redis-compatible cache with an eviction policy you chose on purpose.

What this tier is

Caches fail interestingly. An instance with no memory ceiling takes down its host; an instance with the wrong eviction policy silently discards the session store. We set both explicitly at provisioning and write down which one you chose.

This is a cache and a queue backend, not a database. It is not backed up, and that is intentional: if losing the contents would be a problem, the data belongs in MariaDB or PostgreSQL instead. We will say so during setup.

Specification

Managed Cache specification
EngineRedis-compatible, current stable release
Memory512 MB with an enforced ceiling
EvictionChosen at provisioning and documented
PersistenceOff by default; append-only available on request
AccessPrivate in-cluster hostname only
BackupsNone by design; not a system of record
MetricsMemory, keyspace, and eviction counters on request

What is included

  • Dedicated Redis-compatible instance with its own credentials
  • Explicit maxmemory ceiling and eviction policy, documented
  • Private in-cluster hostname; no public listener
  • Suitable as a Celery, Sidekiq, BullMQ, or RQ broker
  • Memory and keyspace metrics available on request
  • Optional append-only persistence where the workload justifies it

Typical use cases

  • Session storage for an application running more than one replica
  • A job queue broker for background workers
  • Fragment or query caching in front of a database
  • Rate limiting and short-lived token storage

Responsibility split

Written down so there is no argument about it later.

We handle

  • Instance provisioning, memory ceiling, and eviction policy
  • Patching and version upgrades
  • Private networking and credential management
  • Monitoring memory pressure and warning you before eviction bites

You handle

  • Key naming, expiry discipline, and not storing durable data here
  • Client-side reconnection and failure handling
  • Choosing between cache-eviction and queue-durability semantics

How provisioning works

Operator-provisioned, usually same business day, once you confirm the intended use so we can pick the correct eviction policy.

Order

Billing period

We use this for the invoice, provisioning updates, and account sign-in.

Migration deadlines, existing stack, constraints.

Payment is handled by Stripe. We never see or store card details. Continuing means you accept the Terms, Acceptable Use Policy, and Privacy Policy.

Ask a question first

Other tiers in Applications and databases

One application container and one managed database, wired together.

$19 /mo

  • Application container plus a managed database schema
  • Private in-cluster networking to the data tier
  • Daily database backup with a fourteen-day restore window

View details

Redundant application instances, a larger database, and a change process.

$59 /mo

  • Multiple replicas behind health checks with rolling deploys
  • Larger managed database with point-in-time restore requests
  • Staging environment matching production configuration

View details

A dedicated schema on our data tier, backed up and patched by us.

$8 /mo

  • Dedicated schema and credentials, not a shared database
  • Daily logical backup with a fourteen-day restore window
  • Engine patching coordinated with you in advance

View details

A PostgreSQL database with extensions, backups, and an operator.

$10 /mo

  • Dedicated database and role with least-privilege grants
  • Common extensions available on request
  • Daily backup with a fourteen-day restore window

View details