VeUP
← All case studies
Amazon OpenSearch Service Delivery · Digital Signage + FinOps
Displai wordmark

A digital-signage SaaS moves 30-day to 1-year commitments on Amazon CloudFront

AdvisoryPer-service spend attributionCommitment & RI optimizationCost-optimization deep diveManaged billing & resellLog & telemetry cost tuningStanding cost-optimization mechanismWell-Architected ReviewHigh-risk-issue remediation roadmapBlast-radius & tenancy isolation review
One picture
multi-region spend visible per region, per service
Savings Bundle
applied straight onto the core delivery cost driver
30-day → 1-year
commitment coverage modernized
Amazon CloudFrontAmazon OpenSearchAmazon RDSAmazon CloudWatch

For Displai (formerly Raydiant), a digital-signage SaaS, VeUP ran a multi-region FinOps optimization across its AWS estate: the CloudFront Savings Bundle on delivery, long-lived instances moved off 30-day GRIs onto 1-year commitments, CloudWatch log-cost cuts, and an RDS extended-support fix.

The challenge

Displai (formerly Raydiant) runs an interactive digital-signage SaaS that turns in-venue TVs into connected media experiences for customers from SMB to global enterprise. Its product economics depend on efficient multi-region content delivery and storage, but spend was spread across us-west-2 (Oregon), us-east-1 (N. Virginia), and an EU/Canada footprint with no clear per-region/per-service picture: CloudFront delivery costs were uncommitted, modernized long-lived instances sat on 30-day GRIs, CloudWatch logging cost was high (custom/3rd-party dashboard metrics in Oregon), and RDS carried EU extended-support charges. The Raydiant -> Displai entity change also had to be handled mid-contract.

The solution

A multi-region digital-signage content-delivery platform on AWS, FinOps-optimized across its delivery, search, data, and observability tiers: Amazon CloudFront for global edge delivery of media to in-venue signage screens (CloudFront Savings Bundle applied), Amazon OpenSearch Service (concentrated in us-west-2) for search/indexing, Amazon RDS as the relational data tier, and Amazon CloudWatch for observability. VeUP started by giving Displai the thing it lacked — one clear picture of spend per region and per service, with Oregon and N. Virginia identified as the primary cost regions. From there the levers followed: the CloudFront Savings Bundle on delivery, CloudWatch log retention and volume trimmed in Oregon, the RDS EU extended-support charges dealt with, OpenSearch workload locality analyzed, and modernized long-lived instances moved off 30-day GRIs (Archera) onto 1-year commitments.

Architecture

The multi-region digital-signage estate — from the pre-FinOps baseline (uncommitted CloudFront delivery, 30-day GRIs, fragmented cost visibility) through to the production CloudFront edge, per-region OpenSearch/RDS/CloudWatch estate, and the Archera-managed cost-governance plane.

Target-state architecture on AWS: Amazon CloudFront with the Savings Bundle applied delivering signage media globally, a centralized multi-region cost-visibility dashboard, us-west-2 (Oregon) running Amazon OpenSearch Service, Amazon RDS, and Amazon CloudWatch, us-east-1 (N. Virginia) signage application compute, a minor EU/Canada RDS footprint, and an Archera-managed cost-governance rail.
The optimized estate — CloudFront delivering signage media worldwide under the Savings Bundle, with every region's spend visible on one dashboard.
Previous state: uncommitted CloudFront delivery costs, 30-day GRI compute commitments, unclear OpenSearch workload locality, RDS EU extended-support charges, high CloudWatch log cost, and fragmented multi-region cost visibility.
Where it started — uncommitted delivery, 30-day commitments, and no single view of multi-region spend.

Production outcomes

KPIResult
Production outcomesDisplai now sees its multi-region spend clearly, per region and per service, with Oregon and N. Virginia identified as the primary cost regions. The CloudFront Savings Bundle went straight onto the core content-delivery cost driver; modernized long-lived instances were steered off 30-day GRIs onto 1-year commitments; CloudWatch log retention in Oregon was marked for cutback; the RDS EU extended-support charges were flagged and addressed; and OpenSearch workload locality was analyzed for the next round of savings.
Engagement windowThe engagement began as a FinOps review spanning the Raydiant-to-Displai transition, and the optimization work is ongoing.
Cost / TCO postureThe FinOps review was the heart of the engagement: per-region, per-service spend mapping across the estate, the CloudFront Savings Bundle on delivery, commitment coverage modernized from 30-day GRIs to 1-year terms, CloudWatch log-source cost analysis, and the RDS extended-support review — every lever tied to protecting the content-delivery economics a signage platform lives on.
Lessons & continuationFor a multi-region signage media platform, establishing centralized per-region/per-service cost visibility is the precondition for every other lever; the CloudFront Savings Bundle is the direct reduction on the core delivery cost driver; modernized long-lived instances belong on 1-year commitments not 30-day GRIs; and high-cost custom/3rd-party dashboard log metrics are a recurring CloudWatch cost driver worth tuning.
AWS services in production
Amazon CloudFrontAmazon OpenSearch ServiceAmazon RDSAmazon CloudWatch