Fluent Commerce Logo
Docs

RFP Essential Knowledge: Disaster Recovery and Business Continuity

Essential knowledgeCore knowledge to understand Fluent Commerce

Intended Audience:

Technical User

Author:

Michael Wholohan

Changed on:

29 May 2026

Overview

Fluent Commerce's disaster recovery and business continuity posture is built on AWS's multi-region, multi-availability-zone infrastructure. The platform is designed for high availability with automatic failover, encrypted backups, and quarterly DR testing. This article covers backup and restore procedures, incident response, DR planning including RTO/RPO targets, and high availability architecture.

Key points

  • Intended Audience: IT Leadership, Security Team, Solution Architect  
  • Classification: Disaster Recovery and Business Continuity

Backup and Restore

All Fluent business and platform software, including client data, is stored on highly available cloud-based AWS infrastructure.

Backup schedule:
  • Hourly point-in-time snapshots to encrypted online storage
  • Daily full backups to encrypted online storage
  • Automated database snapshots are retained for a 7-day period for short-term recovery
Backup characteristics:
  • All backup media is encrypted using AES-256.
  • All data transported for redundancy and failover is transmitted via TLS 1.2 or greater.
  • Sandbox environments can be refreshed with Production data and metadata using CI/CD tools or database backups.
Data deletion at contract end: At the end of a contract, all customer-related data — database entries, files, backups, and logs containing sensitive or identifiable information — is permanently deleted per standard terms and conditions. Storage media is securely erased following data deletion procedures before disposal.

Incident Response

Fluent maintains a formal security incident management process governed by the Service Level Agreement.

Incident severity tiers (4-level scale):
  • Severity 1 (Critical) - Production platform fully unavailable - Up to 15 minutes 
  • Severity 2 - Significant degradation - Defined per SLA tier
  • Severity 3 - Partial degradation - Defined per SLA tier 
  • Severity 4 - Low-impact issue - Defined per SLA tier 
Fluent maintains a publicly accessible Status Page providing real-time updates on platform performance. Customers and partners can subscribe to incident and disruption notifications.

Monitoring stack used for incident detection:
  • AWS Security Hub and AWS GuardDuty for security event detection
  • AWS CloudWatch for infrastructure and application metrics
  • Elasticsearch and Kibana for log-based analysis
  • OpsGenie for alerting and on-call escalation
Annual incident response exercises are conducted based on agreed and documented test plans, with results reviewed and documented for continuous improvement.

Disaster Recovery (DR) Planning, Recovery Time Objective (RTO) and Recovery Point Objective (RPO)

Regional architecture:

Each primary AWS data centre region includes at least three availability zones. All services and data are served and stored across all availability zones simultaneously.
  • In the event of an availability zone failure: the platform automatically redirects requests to alternate zones with no impact to services.
  • In the event of a regional data centre failure: Fluent can restore services to a sister regional data centre. All data is backed up and archived to the sister region.
Current primary regions: Dublin (EU), Sydney (APAC), Singapore (APAC), North Virginia (US). Additional locations can be spun up in nearby regions for DR scenarios.

RTO/RPO targets: Specific RTO and RPO values are defined in the Fluent Service Level Agreement and standard contract terms. The platform targets 99.95% uptime per month (approximately 4.4 hours maximum downtime per year).

All-cloud business continuity: All Fluent business and platform systems are cloud-based. In the event that any physical location becomes unusable, all key staff can work remotely until a new location is identified.

Failover testing frequency: Quarterly. Tests simulate failure to access a service and/or data, triggering the recovery process and checklist.

High Availability

Fluent's infrastructure is designed as active-active across multiple isolated availability zones and data centres, with no single points of failure.

Component - Availability Approach:
  • Application services - Load-balanced, active-active across multiple AZs 
  • Data storage - Replicated and stored across all AZs in region 
  • Database backups - Archived to sister regional data centre 
  • Network connectivity - Multi-AZ Elastic Load Balancers (ELBs) over HTTPS 
  • AWS dependency - Built across diverse, resilient architecture with regional failover 
In the event of a service or node failure, the load balancer automatically redirects requests to healthy nodes with no customer impact.

AWS-level regional outages are the only scenario where Fluent may breach SLA availability thresholds, given that the overwhelming majority of cloud provider outages have not affected Fluent's ability to remain within SLA.