Growth & Digital/Deploy — scope
EDIT VIA GITHUB · /content
Section template03 · Deploy

Deploy

Where to run it — three options with Cloud recommended, and the marketplace paths that let buyers pay with cloud commits.

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
Deploy layout mock
Click the mock to open the live template in the design directory (new tab).
TEMPLATE SCOPE
edit content/templates/deploy.md

What this page does

Removes the "but where does it run?" objection. The hub presents three options with a clear recommendation (Cloud), an honest responsibility matrix for who runs what, and the promise that the platform is identical everywhere ("what never changes"). The marketplace pages capture buyers who arrive with cloud commits to spend — AWS Marketplace, Azure first-party, GCP, Snowflake native app, Vercel one-click — each billed against existing commitments where possible.

Components on it

  • Centered hero — where to run Redis, stated without hedging.
  • Three option cards — Cloud (recommended) · Software (on-prem, private cloud, air-gapped) · Open Source (Redis 8, free).
  • Responsibility matrix — who manages what, per option — the honesty component that builds trust.
  • Marketplace paths — the five partner routes with billing framing (buy with commits, billed against your CUD, portal-native ops).
  • "What never changes" strip — same platform, same client, same commands everywhere.
  • CTA band — Get Started (Cloud path primary).

What this page does

Removes the "but where does it run?" objection. The hub presents three options with a clear recommendation (Cloud), an honest responsibility matrix for who runs what, and the promise that the platform is identical everywhere ("what never changes"). The marketplace pages capture buyers who arrive with cloud commits to spend — AWS Marketplace, Azure first-party, GCP, Snowflake native app, Vercel one-click — each billed against existing commitments where possible.

Components on it

  • Centered hero — where to run Redis, stated without hedging.
  • Three option cards — Cloud (recommended) · Software (on-prem, private cloud, air-gapped) · Open Source (Redis 8, free).
  • Responsibility matrix — who manages what, per option — the honesty component that builds trust.
  • Marketplace paths — the five partner routes with billing framing (buy with commits, billed against your CUD, portal-native ops).
  • "What never changes" strip — same platform, same client, same commands everywhere.
  • CTA band — Get Started (Cloud path primary).
CLASS
Section template
CHAPTER
03 · Deploy
RENDERS
9 pages — hub + Cloud · Software · Open Source + AWS · Azure · GCP · Snowflake · Vercel
PAGES ON THIS TEMPLATE
Deploy hubRedis CloudRedis SoftwareRedis Open SourceRedis on AWSAzure Managed RedisRedis on Google CloudRedis on SnowflakeRedis on Vercel
SPEC OWNER
Website build program