OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Redis exposes string values through GET and key identities through SCAN. This review covers string keys in one selected database.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Redis GET string values ↗
GET semantics and wrong-type errors · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Iterate SCAN until its cursor returns zero, then GET selected string keys. SCAN can return duplicates and is not an atomic snapshot.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Redis GET string values ↗
GET semantics and wrong-type errors · Checked 2026-10-22
Query expressiveness 7.5/10
Fixed object or report retrieval
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
SCAN supports key-pattern and type selection; GET retrieves one string value. Expiry and concurrent writes can change results during traversal.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Access cost barrier -
-
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Administrators configure ACL users, passwords, command permissions and key patterns. Client access is restricted to the granted commands and keys.
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
Downstream permission -
-
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
SET writes string values and supports expiry and conditional options. Other Redis data types are outside this scope.
Redis SET operation ↗
SET syntax, expiry and conditional options · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Repeat SCAN plus GET for current state. Concurrent changes and expiring keys mean a scan is not a consistent backup or retained event stream.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Limit visibility -
-
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Redis GET string values ↗
GET semantics and wrong-type errors · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Redis GET string values ↗
GET semantics and wrong-type errors · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Retain selected key/value records and separately record expiry where needed. SCAN plus GET alone does not preserve every type, TTL or complete database state.
Redis SCAN traversal guarantees ↗
SCAN guarantees, cursor iteration and TYPE · Checked 2026-10-22
Redis GET string values ↗
GET semantics and wrong-type errors · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
Rights to custom logic -
-
Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Redis ACL users and key permissions ↗
ACL rules, command categories and key permissions · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Administrators configure ACL users, passwords, command permissions and key patterns. Client access is restricted to the granted commands and keys.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Iterate SCAN until its cursor returns zero, then GET selected string keys. SCAN can return duplicates and is not an atomic snapshot. SCAN supports key-pattern and type selection; GET retrieves one string value. Expiry and concurrent writes can change results during traversal.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Redis Open Source selected-database string keys through SCAN, GET and SET | database credentials | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
SET writes string values and supports expiry and conditional options. Other Redis data types are outside this scope.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat SCAN plus GET for current state. Concurrent changes and expiring keys mean a scan is not a consistent backup or retained event stream.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 Redis GET string values ↗GET semantics and wrong-type errorsChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain selected key/value records and separately record expiry where needed. SCAN plus GET alone does not preserve every type, TTL or complete database state.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Redis exposes string values through GET and key identities through SCAN. This review covers string keys in one selected database. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 Redis GET string values ↗GET semantics and wrong-type errorsChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Iterate SCAN until its cursor returns zero, then GET selected string keys. SCAN can return duplicates and is not an atomic snapshot. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 Redis GET string values ↗GET semantics and wrong-type errorsChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. SCAN supports key-pattern and type selection; GET retrieves one string value. Expiry and concurrent writes can change results during traversal. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Administrators configure ACL users, passwords, command permissions and key patterns. Client access is restricted to the granted commands and keys. | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. SET writes string values and supports expiry and conditional options. Other Redis data types are outside this scope. | Redis SET operation ↗SET syntax, expiry and conditional optionsChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Repeat SCAN plus GET for current state. Concurrent changes and expiring keys mean a scan is not a consistent backup or retained event stream. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 |
| How are integration limits disclosed? | -Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 Redis GET string values ↗GET semantics and wrong-type errorsChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRedis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Retain selected key/value records and separately record expiry where needed. SCAN plus GET alone does not preserve every type, TTL or complete database state. | Redis SCAN traversal guarantees ↗SCAN guarantees, cursor iteration and TYPEChecked 2026-10-22 Redis GET string values ↗GET semantics and wrong-type errorsChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Redis / Redis Open Source selected-database string keys through SCAN, GET and SET; Redis Cloud control plane, non-string payloads, keyspace events and native backups are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Redis ACL users and key permissions ↗ACL rules, command categories and key permissionsChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.