Redis: Cloud plans, data integration and operational responsibilities

Redis Flex combines RAM and SSD storage for workloads whose frequently accessed working set is smaller than the full dataset. Keys remain in RAM. Capacity planning therefore needs to distinguish the size of the entire dataset from the portion that must stay in memory; a headline database size does not describe the full memory requirement.[11]

Iris separates persistent agent memory, retrieval of business context and semantic caching of repeated requests. Availability must be checked for the individual service: Context Retriever is in public preview, requires a Redis Cloud database containing the relevant data and currently excludes Flex and Active-Active databases. An existing Redis deployment is therefore not automatically eligible for every Iris service.[18][19]

The supported client list covers Python, Java, JavaScript, C#, Go, C and Ruby libraries. Redis distinguishes those supported clients from best-effort third-party choices such as Predis for PHP and redis-rs for Rust, and from wider community libraries. Selecting a language binding should include its maintenance and support status, alongside compatibility with the server features the application will use.[10]

Redis Data Integration starts with an initial load and then captures inserts, updates and deletes. Supported source families include Oracle, PostgreSQL, MySQL, MongoDB and SQL Server; Snowflake is labelled preview. YAML transformations produce hashes, JSON or streams. The service documents at-least-once delivery, so downstream consumers should account for replay. The source system remains a separate operational dependency, with its own history retention and access controls.[12]

Active-Active databases use conflict-free replicated data types to accept reads and writes in multiple regions and converge through eventual consistency. Cloud deployment requires a Pro subscription configured for Active-Active, with at most ten regions and ten databases. The deployment guide specifies 99.999% availability when every region has at least three availability zones, falling to 99.99% overall if any region has fewer. Region design and the purchased SLA should be checked together. Applications requiring immediate agreement between regions must also evaluate the eventual-consistency model.[9]

Cloud fees are in US dollars unless the transaction specifies otherwise, with applicable taxes additional. Committed expenditure remains payable even if actual use is lower, and network charges can be passed through. The order and selected capacity therefore matter more than the entry-price example.[4]

Commercial Redis Software uses an agreed licence and support subscription. Its public agreement calls for usage reporting every three months, or another period Redis specifies, with additional usage charged proportionally at the applicable contract or list price. A quote should identify licensed capacity and the treatment of growth, alongside the infrastructure the customer operates.[5]

Data Integration Cloud charges use Redis Processing Units: one for a workspace with a deployed pipeline, two per running collector and two per processor replica. Usage is measured each minute and billed using the hourly peak; unit rates depend on region and plan. Stopping a pipeline can leave the workspace charge in place. Deleting the pipeline ends new pipeline usage, subject to that hourly peak. Target databases and network transfer add separate costs.[13]

Removing data is also different from ending a Cloud subscription. Deleting a database is irreversible, and the documentation says subscription billing continues even when it contains no databases. An Account Owner can delete the subscription when removing its last database. Decommissioning should therefore include both a recoverable export and an explicit subscription decision.[20]

Bring Your Own Cloud places a Redis-managed deployment inside the customer’s cloud account, subject to Redis approval and the required permissions. Redis bills management and licensing; the cloud provider bills underlying infrastructure and network use. The customer must preserve Redis-created resources and permissions. Stopping instances or changing roles independently can interrupt the service and affect SLA coverage. This is a managed operating arrangement even though the infrastructure bill sits with the customer.[14]

Paid Essentials supports manual and daily backups. Pro adds scheduled intervals down to one hour and configurable UTC timing. Backups use RDB files, potentially one per shard, and require access to the chosen destination, such as S3, Google Cloud Storage or Azure Blob Storage. Free databases cannot be backed up or exported through the Cloud console. Recovery planning should establish the export method and destination before relying on a plan for production data.[15]

A Data Integration reset clears saved source positions but does not flush the target database. Debezium sources take a new snapshot in the default initial mode; other configured modes can skip existing rows or ongoing change capture. Old target keys can remain. Flushing instead permanently removes all target data, including application-written records. Recovery therefore depends on the configured load mode and source of record.[13]

Professional Services offers implementation, migration, automation and production-event assistance. Published packages include two-day Cloud jumpstarts, three-day Software jumpstarts and separate Terraform or Ansible automation work. Those durations describe service packages, not a guaranteed end-to-end migration schedule. The statement of work should connect the selected package to data conversion, application changes, performance assessment and the customer’s release process.[21]

These are initial responses for production databases, not resolution deadlines. Basic operates in business hours; Business and higher packages include continuous phone and technical coverage. The policy applies to eligible paid services with the required credits and excludes Free services and previews. Support requests use the English-language portal, with telephone access provided to entitled customers.[6]

The Cloud SLA separately states monthly availability commitments of 99.9% for Standard, 99.99% for Multi-AZ and 99.999% for Active-Active; Essentials qualifies only for Standard. Covered deployments need replication enabled and at least 24 hours of operation. Falling below the applicable threshold can produce a 10% credit, or 25% below 99% uptime, capped at 25% of affected monthly fees. Credits apply to future fees. A support ticket is required within 24 hours of awareness and a documented claim by the end of the second following billing cycle. Customer configuration, maintenance, previews and specified third-party causes are excluded. Deployment eligibility and the contract’s downtime measurement therefore matter alongside the headline percentage.[7]

Cloud security separates console access, database connections and management API credentials. Documented controls include MFA, SAML single sign-on, role-based access, TLS and network restrictions. The management REST API is disabled by default until enabled with the appropriate keys. Each access path should be included in the institution’s control design; protecting a console account alone does not configure every database or API permission.[16]

The shared-responsibility model assigns Cloud platform and operating-system maintenance to Redis, with physical infrastructure handled by the underlying cloud provider. Customers remain responsible for their applications, data, security configuration and region selection. For a financial institution, these are infrastructure responsibilities inside its wider regulated workflow; the documentation does not transfer its brokerage, customer-protection or compliance duties to Redis.[17]

The company traces its origins to 2011 and lists San Francisco as its headquarters. Its commercial footprint includes offices in Europe, North America and Asia. The current company should be distinguished from the wider community of developers and third parties that use or distribute Redis-compatible technology.[22]

Under the Cloud agreement, Redis Inc. contracts with customers in the Americas, Asia Pacific and other unlisted regions; Redis Ltd. covers Israel; Redis EMEA Ltd. covers Europe, the United Kingdom, the Middle East and Africa. The purchaser’s domicile and transaction determine the relevant counterparty.[4]

The company previously used Redis Labs, dropping “Labs” in 2021. Before that, it changed from Garantia Data to Redis Labs in January 2014. These historical names belong to the same company history rather than separate providers.[27][28]

Redis acquired storage-engine company Speedb in March 2024 and feature-store company Featureform in October 2025. These additions broaden its storage and machine-learning data capabilities; an acquisition announcement alone does not establish that every capability is included in every Cloud plan.[24][23]

Operator

Redis Inc.; Redis Ltd.; Redis EMEA Ltd., according to the Cloud customer’s domicile

Service scope

Operational databases, caching, data integration and AI application data services.

Customer types

Financial institutions; Brokerage technology teams; Application developers

Delivery

SaaS; On premises; Hybrid; Managed service

Pricing publication

Public and quoted pricing

Headquarters

San Francisco, California, United States

Platforms

Redis Cloud; Redis Software; Redis Data Integration; Redis Iris

Integrations

Python; Java; JavaScript; C#; Go; Oracle; PostgreSQL; MongoDB; SQL Server

Pricing scope

Published Cloud entry plans; dedicated capacity, support and commercial Software depend on the selected configuration and agreement.

Implementation

Client integration, data design, topology and recovery planning, with optional professional services.

Support

Cloud support tiers have severity-specific initial-response targets; availability credits follow a separate SLA.

Permissions and regulatory scope

Application infrastructure; customers retain responsibility for data, security configuration and regulated workflows.

Provider metadata checked 21 Oct 2026Source 10Source 4Source 22Source 1Source 28Source 18Source 3Source 12Source 27Source 17Source 21Source 7Source 2Source 5

Licensing depends on version and distribution. Redis 7.2 and earlier use BSD 3-Clause; versions 7.4–7.8 use the RSALv2 or SSPLv1 choice; Redis 8 and later add AGPLv3 as a third option. The current licence page says the AGPL option does not change commercial Cloud or Software licensing. Teams embedding, redistributing or offering Redis-based services should select the applicable licence against their actual deployment rather than carrying forward an assumption from an older release.[8]