Growth & Digital/Redis Platform — scope
EDIT VIA GITHUB · /content
Single page01 · Platform

Redis Platform

Chapter 01 hub — the platform narrative in full, and the router into the seven product pages.

DESIGN v1.1 LANDED AUG 31 — this scope page was written against v1; verify against the new snapshot before relying on component details.
LAYOUT MOCK — STRUCTURE ONLY
Redis Platform layout mock
Click the mock to open the live template in the design directory (new tab).
TEMPLATE SCOPE
edit content/templates/redis-platform.md

What this page does

The narrative anchor of chapter 01. Where the homepage tells the story in one scroll, this page tells it properly: what the platform is, why the pieces are one system, and where each product fits. It is the page sales sends when someone asks "so what is Redis now?" — and the router that hands traffic to the seven Platform Product pages.

Components on it

  • Platform hero — the platform thesis stated plainly, one H1, one CTA.
  • Platform story sections — the chaptered narrative: serve, search, remember, ingest, scale — each section one platform capability told as a story beat.
  • Product router — cards for all 7 product pages (LangCache, Context Retriever, Agent Memory, Data Integration, Flex, Search, Feature Store) with one-liners.
  • Consolidation proof — the one-platform economics: one client, one SLA, one bill; fewer vendors on the hot path.
  • Proof band — benchmarks + customer evidence (figures illustrative pending review).
  • CTA band — Get Started.

What this page does

The narrative anchor of chapter 01. Where the homepage tells the story in one scroll, this page tells it properly: what the platform is, why the pieces are one system, and where each product fits. It is the page sales sends when someone asks "so what is Redis now?" — and the router that hands traffic to the seven Platform Product pages.

Components on it

  • Platform hero — the platform thesis stated plainly, one H1, one CTA.
  • Platform story sections — the chaptered narrative: serve, search, remember, ingest, scale — each section one platform capability told as a story beat.
  • Product router — cards for all 7 product pages (LangCache, Context Retriever, Agent Memory, Data Integration, Flex, Search, Feature Store) with one-liners.
  • Consolidation proof — the one-platform economics: one client, one SLA, one bill; fewer vendors on the hot path.
  • Proof band — benchmarks + customer evidence (figures illustrative pending review).
  • CTA band — Get Started.
CLASS
Single page
CHAPTER
01 · Platform
RENDERS
1 page — /platform/
PAGES ON THIS TEMPLATE
Redis Platform
SPEC OWNER
Website build program