CLOUD9S

Azure

Cloud9s — Azure

Production-grade Azure Terraform — zone-redundant VMSS, App Gateway, Flexible Server, architected for three nines.

VNet across 3 availability zones (web + data subnets, NSGs)
Application Gateway v2 with WAF, TLS termination, end-to-end HTTPS
VM Scale Set (zone-redundant) for the web tier with health probes

$299

GCP

Cloud9s — GCP

Production-grade GCP Terraform — regional MIG, global HTTPS LB, Cloud SQL HA, architected for three nines.

VPC + regional subnets across 3 zones, Cloud NAT, firewall rules
Global HTTPS Load Balancer + managed SSL + Cloud Armor policy
Regional Managed Instance Group (3-zone) with instance template + health checks

$299

OCI

Cloud9s — OCI

Production-grade OCI Terraform — multi-AD compute, FLB, DB System HA, architected for three nines.

VCN across 3 Availability Domains (public + private subnets, NSGs, route tables)
Flexible Load Balancer with HTTPS listener + certificate
Instance Pool (multi-AD) with instance configuration + health checks

$299

Support: Email + architecture review · 2 business days response

All CloudsBest value · Save $297

Cloud9s — All-Clouds Bundle

All four clouds. One bundle. Pick your stack — or migrate between them with the same reference design. Save $297 vs. buying separately.

All four single-cloud zips (AWS / Azure / GCP / OCI) at the same scenario parity
Shared README describing cross-cloud equivalences (subnet/AZ mapping, LB equivalents, DB HA equivalents)
Single LEGAL_NOTICE covering all four

$899

Details →Buy — $899

Four-Nines Active-Passive DR

AWS

Cloud9s — AWS DR

Multi-region active-passive DR on AWS — Route 53 health-check failover, warm standby, cross-region RDS replica, architected for four nines.

Two regions: full primary stack + warm standby in a second AWS region
ALB per region with Route 53 health-check DNS failover
EC2 Auto Scaling primary + right-sized warm-pool ASG in the DR region

$799

Azure

Cloud9s — Azure DR

Multi-region active-passive DR on Azure — Traffic Manager priority failover, warm VMSS, cross-region PostgreSQL replica, architected for four nines.

Two regions: full primary stack + warm standby in a paired Azure region
Application Gateway v2 per region + Traffic Manager priority-routing failover
VM Scale Set primary + warm-pool VMSS in the DR region

$799

GCP

Cloud9s — GCP DR

Multi-region active-passive DR on GCP — Cloud DNS health-check failover, warm MIG, cross-region Cloud SQL replica, architected for four nines.

Two regions: full primary stack + warm standby in a second GCP region
Regional LBs with Cloud DNS health-check failover routing
Regional Managed Instance Group primary + warm MIG in the DR region

$799

OCI

Cloud9s — OCI DR

Multi-region active-passive DR on OCI — Traffic Management steering failover, warm Instance Pool, cross-region DB standby, architected for four nines.

Two regions: full primary stack + warm standby in a second OCI region
Flexible Load Balancer per region + Traffic Management steering-policy failover
Instance Pool primary + warm-pool instances in the DR region

$799

All CloudsBest value · Save $797

Cloud9s — All-Clouds DR Bundle

All four clouds, one active-passive DR reference design. Same RPO/RTO posture, cloud-native failover per provider. Save $797 vs. buying separately.

All four single-cloud DR zips (AWS / Azure / GCP / OCI) at scenario parity
Cross-cloud equivalence notes (failover primitives, replica/standby mapping)
Single LEGAL_NOTICE covering all four

$2,399

Support: Email + architecture review · 2 business days response

Four-Nines Database HA

AWS

Cloud9s — AWS Database HA

Four-nines database tier on AWS — Aurora PostgreSQL Global Database with cross-region readers and sub-minute promotion.

Aurora PostgreSQL Global Database — writer region + cross-region readers
Managed cross-region replication with single-digit-second RPO
Sub-minute managed promotion on regional failover

$799

Azure

Cloud9s — Azure Database HA

Four-nines database tier on Azure — Azure SQL auto-failover groups with a listener that survives regional failover.

Azure SQL Database with auto-failover groups across two regions
Read-write listener FQDN survives failover with no app config change
Single-digit-second RPO, managed sub-minute RTO

$799

GCP

Cloud9s — GCP Database HA

Four-nines database tier on GCP — Cloud Spanner multi-region, synchronous, transparent through a regional outage.

Cloud Spanner multi-region — synchronous replication, no failover step
Strong consistency across regions, single-digit-second RPO
Survives a regional outage transparently to the application

$799

OCI

Cloud9s — OCI Database HA

Four-nines database tier on OCI — Autonomous Database with Autonomous Data Guard cross-region standby.

Autonomous Database with Autonomous Data Guard across two regions
Cross-region standby with single-digit-second RPO
Sub-hour managed RTO; failover via connection-string switch

$799

All CloudsBest value · Save $797

Cloud9s — All-Clouds Database HA Bundle

All four clouds, one four-nines database-HA reference design. Highest-tier managed DB per provider. Save $797 vs. buying separately.

All four single-cloud DB-HA zips (AWS / Azure / GCP / OCI) at scenario parity
Cross-cloud equivalence notes (Aurora Global / SQL FOG / Spanner / ADG)
Single LEGAL_NOTICE covering all four

$2,399

Support: Community support · Best-effort response

Two-Nines Starter

Architected for 99.0% availability against the published cloud SLAs — approximately 3 days 15 hours annual downtime budget. One small VM behind a managed load balancer, one single-AZ managed database, encryption at rest, alerts wired from the first apply, daily backups, credentials in the cloud-native secret store. Honest about the tradeoff: single-AZ, single-instance — an AZ failure takes the site down until the zone recovers. What you get in exchange is a production-shaped stack for roughly $65–$96/month instead of $325+, and every variable is a strict subset of Scenario 1 (Three-Nines Web), so your `terraform.tfvars` file carries forward when you outgrow it.

AWS

Cloud9s — Two-Nines Starter (AWS)

Architected for 99.0% availability against the published cloud SLAs — approximately 3 days 15 hours annual downtime budget.

Single EC2 instance (t3.small) with EC2 auto-recovery alarm
Application Load Balancer (minimum config, HTTPS via ACM cert wiring)
RDS PostgreSQL 16 in single-AZ mode with encrypted storage + daily backups

$99

Azure

Cloud9s — Two-Nines Starter (Azure)

Architected for 99.0% availability against the published cloud SLAs — approximately 3 days 15 hours annual downtime budget.

Single Linux VM (Standard_B2s), zone-pinned, Premium SSD
Standard SKU Load Balancer (L4) with health probe
Azure Database for PostgreSQL Flexible Server, single-zone (no HA)

$99

GCP

Cloud9s — Two-Nines Starter (GCP)

Architected for 99.0% availability against the published cloud SLAs — approximately 3 days 15 hours annual downtime budget.

Single Compute Engine VM (e2-small), Shielded, no public IP
Regional External Application LB (Standard network tier)
Cloud SQL for PostgreSQL, zonal, private IP + daily backups

$99

OCI

Cloud9s — Two-Nines Starter (OCI)

Architected for 99.0% availability against the published cloud SLAs — approximately 3 days 15 hours annual downtime budget.

Single Compute instance (VM.Standard.E4.Flex, 1 OCPU / 6 GB)
Flexible Load Balancer (10 Mbps minimum shape) with HTTPS listener
MySQL DB System, standalone (non-HA), automated backups

$99

All CloudsBest value · Save $97

Cloud9s — Two-Nines Starter All-Clouds Bundle

The cheapest defensible way to run a real application with a managed database. All four clouds, one bundle.

All four single-cloud Two-Nines Starter zips (AWS + Azure + GCP + OCI)
Shared README with cross-cloud equivalences (compute / LB / DB / secrets)
Same $65–$96/month cost envelope shape per cloud, comparable line items

$299

Support: Email support · 3 business days response

Three-Nines Containerized

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 45 minutes annual downtime budget. A containerized reference stack on each cloud's managed Kubernetes: HA node pools across three availability zones (or the cloud's equivalent fault domains), cloud-native ingress, an HA managed PostgreSQL-class database, cluster and workload autoscaling, a private container registry, and control-plane plus workload logging/monitoring wired from the first apply. Nodes are private with a locked-down NAT egress path, database credentials are Terraform-generated and stored in the cloud-native secret store, and everything cloud-native ships in the module — with everything in-cluster (ingress controllers, `SecretProviderClass`, your app) as documented post-deploy commands. No `kubernetes` or `helm` provider dependencies, so plan-before-apply review works on a clean checkout.

AWS

Cloud9s — Three-Nines Containerized (AWS)

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 45 minutes annual downtime budget.

EKS 1.34 with a managed node group (3–9 × t3.large) across 3 AZs, IRSA
AWS Load Balancer Controller → ALB (IAM shipped; helm post-deploy)
RDS PostgreSQL 16, Multi-AZ, with private subnets + parameter groups

$299

Azure

Cloud9s — Three-Nines Containerized (Azure)

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 45 minutes annual downtime budget.

AKS Standard tier (1.32), system + user pools across zones 1–3, autoscale 3–9
Application Gateway v2 via AGIC add-on (TF-native, no helm provider)
Azure Database for PostgreSQL Flexible Server, ZoneRedundant HA

$299

GCP

Cloud9s — Three-Nines Containerized (GCP)

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 45 minutes annual downtime budget.

GKE regional private cluster (1.32 floor), autoscaled node pool across 3 zones
GKE Ingress → global external Application LB (TF-reserved IP + managed cert)
Cloud SQL for PostgreSQL, regional HA, private IP + Dataplane V2

$299

OCI

Cloud9s — Three-Nines Containerized (OCI)

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 45 minutes annual downtime budget.

OKE enhanced cluster (v1.34.2), VCN-native CNI, node pool across all ADs
ingress-nginx → OCI Flexible Load Balancer (NSG shipped; helm post-deploy)
Autonomous Database (OLTP, ECPU, private endpoint) + autoscaler add-on

$299

Support: Email + architecture review · 2 business days response

All CloudsBest value · Save $297

Cloud9s — Three-Nines Containerized All-Clouds Bundle

A production-shaped Kubernetes reference stack, per cloud, that you can deploy in an afternoon. All four clouds, one bundle.

All four single-cloud Three-Nines Containerized zips
Cross-cloud equivalence notes (managed k8s, ingress, registry, workload IAM, secrets CSI)
Same k8s-version-pinned floor, same node-pool shape, same NAT egress posture

$899

Details →Buy — $899

Four-Nines Static + API

Architected for 99.99% availability against the published cloud SLAs — approximately 52 minutes annual downtime budget. A globally-edged web product: static front end from the cloud's edge, serverless API tier deployed in two regions behind health-checked failover routing, and a database replicated — or actively multi-writable — across regions. HTTPS, health probes, secrets in the cloud-native store, and alerting are wired from the first apply. Serverless compute in every cloud means nothing to patch and no capacity to babysit; duplicating it into a second region costs almost nothing at low traffic — which is exactly what makes four nines affordable here. The database tier is where the money and the honesty live, and each cloud's ARCHITECTURE.md documents its own contract explicitly.

AWS

Cloud9s — Four-Nines Static + API (AWS)

Architected for 99.99% availability against the published cloud SLAs — approximately 52 minutes annual downtime budget.

CloudFront + private S3 origin (OAC), Lambda@Edge security headers
API Gateway + Lambda in TWO regions; CloudFront origin failover default
Aurora PostgreSQL Global Database (writer + cross-region reader)

$799

Azure

Cloud9s — Four-Nines Static + API (Azure)

Architected for 99.99% availability against the published cloud SLAs — approximately 52 minutes annual downtime budget.

Front Door Standard + Storage static website (RA-GRS, two health-probed origins)
Functions (Consumption) in TWO regions, active/active behind Front Door probes
Cosmos DB with multi-region write and explicit LWW conflict resolution

$799

GCP

Cloud9s — Four-Nines Static + API (GCP)

Architected for 99.99% availability against the published cloud SLAs — approximately 52 minutes annual downtime budget.

Global External Application LB + Cloud Storage + Cloud CDN
Cloud Run functions (Gen 2) in TWO regions as serverless NEGs on the same LB
Cloud Spanner (nam3 multi-region) — synchronous, no failover step

$799

OCI

Cloud9s — Four-Nines Static + API (OCI)

Architected for 99.99% availability against the published cloud SLAs — approximately 52 minutes annual downtime budget.

Object Storage served via API Gateway over HTTPS (no first-party CDN)
Functions + API Gateway in TWO regions with optional DNS Traffic Management
Autonomous Database + cross-region Autonomous Data Guard standby

$799

All CloudsBest value · Save $797

Cloud9s — Four-Nines Static + API All-Clouds Bundle

The dominant modern web shape — static SPA + JSON API — engineered to survive a full regional outage. All four clouds, one bundle.

All four single-cloud Four-Nines Static+API zips
Cross-cloud equivalence notes (edge, serverless API, DB conflict story)
Two-region routing, replication, TLS, and alerting compared side-by-side honestly

$2,399

Support: Email + architecture review · 2 business days response

Pilot Light DR

Architected for 99.9% availability against the published cloud SLAs — approximately 8 hours 46 minutes annual downtime budget — plus a disaster-recovery posture of RPO ≤ 15 minutes and RTO ≤ 4 hours (design targets enforced by alarms and runbooks, not guarantees). The primary region runs a full three-nines production stack; the DR region runs only the data layer continuously (database replicating, object assets replicating) while DR compute is fully modeled but parked at zero instances behind a pre-staged idle load balancer. You pay every month for a second copy of your data and $0.00 for a second copy of your fleet. Recovery is three operator moves in every cloud: light the compute (scale 0 → N), promote the data (replica becomes write master), flip the traffic (DNS). Every step is a documented CLI command with a time budget in each cloud's `RUNBOOK.docx`.

AWS

Cloud9s — Pilot Light DR (AWS)

Primary: ALB → multi-AZ ASG → RDS PostgreSQL 16 Multi-AZ
DR data: encrypted cross-region read replica (DR-region CMK) + S3 CRR with RTC
DR compute: ASG 0/6/0 behind an idle ALB, launch template pre-staged

$799

Azure

Cloud9s — Pilot Light DR (Azure)

Primary: App Gateway v2 → VMSS → Azure SQL DB (GP tier)
DR data: Active geo-replication Standby secondary (~49% cheaper) + RA-GRS
DR compute: VMSS at capacity 0 behind an idle zone-redundant Standard LB

$799

GCP

Cloud9s — Pilot Light DR (GCP)

Primary: regional external ALB → regional MIG → Cloud SQL PostgreSQL 16 (regional HA)
DR data: cross-region read replica (zonal) + dual-region GCS with turbo replication
DR compute: MIG at target_size = 0 behind a pre-staged regional ALB

$799

OCI

Cloud9s — Pilot Light DR (OCI)

Primary: Flexible LB → multi-AD instance pool → Autonomous Database (ECPU, private endpoint)
DR data: Autonomous Data Guard cross-region standby + Object Storage replication
DR compute: Instance pool at size 0 behind an idle 10 Mbps Flexible LB

$799

All CloudsBest value · Save $797

Cloud9s — Pilot Light DR All-Clouds Bundle

The cheapest credible answer to "what if the region goes away?" — data always warm, compute always cold. All four clouds, one bundle.

All four single-cloud Pilot Light DR zips
Cross-cloud equivalence notes (DR data replication + parked compute)
Same three-step recovery model in every cloud (light / promote / flip)

$2,399

Support: Email + architecture review · 2 business days response

Hot Standby DR

Architected for 99.95% availability against the published cloud SLAs — approximately 4 hours 23 minutes annual downtime budget — plus a disaster-recovery posture of RPO ≤ 5 minutes and RTO ≤ 30 minutes (design targets enforced by alarms, runbooks, and drills, not guarantees). A second, identical, fully running copy of production sits in another region taking no traffic, so that recovery from a regional disaster is a DNS flip that happens by itself plus one operator command for the database — minutes, not hours. Shape identity is enforced structurally: one Terraform stack module instantiated twice per region, one set of sizing variables, no `secondary_*` or `dr_*` inputs anywhere. The standby cannot be declared smaller, cheaper, or slower than the primary because the configuration language to do so does not exist. This is production, minus the traffic.

AWS

Cloud9s — Hot Standby DR (AWS)

TWO identical stacks: ALB → multi-AZ ASG (2–6 × t3.medium), fed one set of vars
Aurora PostgreSQL Global Database (storage-level replication, typical lag < 1s)
Route 53 health-checked failover records — flips itself in ~2–3 min

$799

Azure

Cloud9s — Hot Standby DR (Azure)

TWO identical stacks: App Gateway v2 → zone-spread VMSS (2–6 × D2as_v5)
Azure SQL auto-failover group — read-write listener follows the new primary
Traffic Manager priority routing with 10s probes — flips itself in ~1–2 min

$799

GCP

Cloud9s — Hot Standby DR (GCP)

TWO identical stacks: regional external ALB → regional MIG (2–6 × e2-standard-2)
Cloud SQL PostgreSQL cross-region read replica with REGIONAL HA on each side
Cloud DNS health-checked primary-backup routing — flips itself in ~1.5–4 min

$799

OCI

Cloud9s — Hot Standby DR (OCI)

TWO identical stacks: Flexible LB → multi-AD instance pool (2–4 × E4.Flex)
Autonomous Database + cross-region Autonomous Data Guard (Oracle-published RTO < 10m)
OCI Health Checks (30s probes) + DNS Traffic Management FAILOVER (60s TTL)

$799

All CloudsBest value · Save $797

Cloud9s — Hot Standby DR All-Clouds Bundle

A second, identical, fully running copy of production — DNS flip and a database command from recovery. All four clouds, one bundle.

All four single-cloud Hot Standby DR zips
Cross-cloud equivalence notes (identical-stack enforcement, DB failover mechanism)
Same one-variable-set shape rule, no secondary_* or dr_* sizing knobs anywhere

$2,399

Support: Priority + Slack Connect · 1 business day response

Five-Nines Event-Driven

Architected for 99.999% availability of event acceptance and retention against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget. The scoping in that sentence is the product: five nines applies to the backbone's ability to accept an event from a retrying producer and to retain it durably until processed — it does NOT apply to end-to-end processing latency, which every one of these designs deliberately allows to degrade into durable, alarmed backlog. A durable event backbone: an ingest surface producers can (almost) always reach, a work queue with dead-letter/poison containment, an ordered stream, idempotent placeholder workers demonstrating the claim-before-side-effect pattern, cross-region retention (replication and/or a geo-replicated archive), and first-class replay. Buy this when losing an accepted event is unacceptable and minutes-per-year of ingest impairment is the budget.

AWS

Cloud9s — Five-Nines Event-Driven (AWS)

Architected for 99.999% availability of event acceptance and retention against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

SQS FIFO + FIFO DLQ + alarmed events-DLQ for undeliverable targets
Kinesis Data Streams on-demand, 168h replay window
Lambda × 2 regions (ESMs are the evacuation switch); DynamoDB Global Tables (99.999%)

$1,999

Azure

Cloud9s — Five-Nines Event-Driven (Azure)

Architected for 99.999% availability of event acceptance and retention against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

Service Bus Premium queues (work/replay/poison), broker duplicate detection
Event Hubs Standard + Capture (Avro to RA-GRS every ≤300s)
Azure Functions (Consumption) hot/hot in both regions

$1,999

GCP

Cloud9s — Five-Nines Event-Driven (GCP)

Architected for 99.999% availability of event acceptance and retention against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

Pub/Sub subscriptions + dead-letter topic (5 attempts, parking sub)
Same Pub/Sub topic (global service), 7-day topic retention, seek/snapshot replay
Cloud Run functions gen2, two regions active/active

$1,999

OCI

Cloud9s — Five-Nines Event-Driven (OCI)

Architected for 99.999% availability of event acceptance and retention against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

OCI Queue with native DLQ (delivery-count redrive)
OCI Streaming, 168h retention, Connector Hub as the managed trigger
OCI Functions (OCIR images per region), fed by Connector Hub

$1,999

Support: Priority + Slack Connect · 1 business day response

All CloudsBest value · Save $2997

Cloud9s — Five-Nines Event-Driven All-Clouds Bundle

A durable event backbone where losing an accepted event is unacceptable and lateness converts to alarmed backlog, not loss. All four clouds, one bundle.

All four single-cloud Five-Nines Event-Driven zips
Cross-cloud equivalence notes (queue/DLQ, stream, workers, dedup state, cross-region archive)
Same idempotent claim-before-side-effect worker pattern in each cloud

$4,999

Details →Buy — $4,999

Five-Nines Active-Active

Architected for 99.999% availability against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget. TWO regions serve live traffic simultaneously: a regional failure removes capacity, not availability. No standby, no "activate DR" step, no failover runbook on the traffic path. Two complete, identically-sized serving stacks run in two regions of the same cloud, both taking production traffic all day. When a region fails, health-checked routing stops handing it out and the survivor — already warm, already proven, already sized for 100% of peak — absorbs the load. The hard part of active-active was never the compute — it is the data. Each cloud answers differently: single writer both regions reach transparently (AWS Aurora Global with write forwarding), true multi-master with LWW (DynamoDB Global, Cosmos, OCI NoSQL), or synchronously-replicated (Spanner nam3). Per-cloud `ARCHITECTURE.md` files carry the full contracts your application team must accept.

AWS

Cloud9s — Five-Nines Active-Active (AWS)

Architected for 99.999% availability against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

TWO regions serving traffic simultaneously: ECS Fargate behind ALB (2–8 tasks/region)
Route 53 latency routing with health-checked ejection
Aurora Global Database with write forwarding (single writer, zero relational conflicts)

$1,999

Azure

Cloud9s — Five-Nines Active-Active (Azure)

Architected for 99.999% availability against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

TWO regions serving simultaneously: AKS + Application Gateway v2 via AGIC (3–12 user nodes/region)
Traffic Manager Performance routing (health-gated)
Cosmos DB multi-region write, explicit LWW on /_ts — 99.999% read/write SLA

$1,999

GCP

Cloud9s — Five-Nines Active-Active (GCP)

Architected for 99.999% availability against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

ONE global anycast IP served by multi-cluster GKE Gateway
Two fleet-registered regional GKE clusters (6–18 nodes/region), both live
Cloud Spanner nam3, leader-pinned — external consistency, write conflicts designed away

$1,999

OCI

Cloud9s — Five-Nines Active-Active (OCI)

Architected for 99.999% availability against the published cloud SLAs — approximately 5 minutes 15 seconds annual downtime budget.

TWO regions serving via DNS Traffic Management steering, 50/50 weighted, health-gated
OKE enhanced clusters (3–6 nodes/region), both live
NoSQL Global Active Table (true multi-master, LWW)

$1,999