Case Study

Cloud-Native Membership Platform

Sails Software's cloud-native membership platform helped a financial services provider launch plans 80% faster and speed up KPI reporting by 70%.

Client Context

A subscription-based financial services provider needed one platform to run its entire membership business

The client operates in the financial services space, offering customers access to financial products through flexible, subscription-based membership plans. Rather than a single product, the business runs a portfolio of plans, each with its own eligibility rules, product access, and customer journey — and each partner relationship needed to feel tailored without becoming a one-off build.

Model

Subscription Membership

Customers access financial products through tiered, configurable membership plans rather than a single fixed offering.

Scope

Full Customer Lifecycle

From digital onboarding and plan selection through payments, product access, and ongoing account management.

Constraint

Regulated Environment

A financial services context where reliability, auditability, and secure data handling aren't optional.

Why The Problem Was Hard

Financial membership products can't run on rigid infrastructure

Every new membership plan, partner integration, or referral program had historically meant touching core application logic. That's a slow and risky way to run a financial product, where changes need to move quickly but can't afford to be careless.

Hard-coded journeys

Onboarding and eligibility logic was fixed in the application, making personalization by plan, partner, or referral source expensive to build.

Scaling pressure

As session and transaction volume grew, direct database reads became a performance bottleneck on customer-facing flows.

Fragmented documents

Financial reports, generated exports, and business documents lacked a consistent, secure storage and retrieval approach.

Limited visibility

Without a unified monitoring layer, operations teams often learned about issues from customers rather than dashboards.

What Sails Delivered

A modular, cloud-native platform built to change as fast as the business does

Sails designed and built a microservices-based platform on AWS, replacing rigid application logic with independently deployable services connected through secure APIs — so new plans, partners, and journeys become configuration work, not re-engineering work.

Configurable Customer Journeys

Journey flows that adapt dynamically to eligibility, membership plan, product selection, and referral source.

Microservices Architecture

Independent services for onboarding, membership, payments, referrals, and reporting — each deployed and scaled on its own.

Redis Performance Layer

Session data, feature flags, and frequently accessed business data cached in memory to reduce database load.

AWS Cloud Infrastructure

Application hosting, backups, and object storage on AWS, with Amazon S3 for secure document and report storage.

Request & Service Flow

ClientUsers

HTTPSFrontend

React Frontend — Customer Portal

REST / HTTPSAPI Gateway

Laravel API — Gateway & APIs

Core ServicesCustomer Service

Membership ServicePayment Service

Extended ServicesReferral Service

Product ServicePartner Integration

Data LayerRedis Cache

DatabaseS3 Storage

Cached metrics feed the KPI layer

Analytics & Monitoring

Business KPI DataGrafana

Platform Architecture

How the layers fit together

The platform is organized in layers, with each layer independently scalable and replaceable without disrupting the others.

Customer Layer

Digital Onboarding Portal

Member Account Dashboard

Partner-Facing Journeys

API & Services Layer

Onboarding Service

Membership & Eligibility Service

Payments Service

Referral & Partner Service

Reporting Service

Data & Caching Layer

Redis (Sessions, Config, Feature Flags)

Application Databases

Cloud Infrastructure

AWS Compute & Hosting

Amazon S3 (Documents, Reports, Exports)

Backups

Observability Layer

Grafana Dashboards

Centralized Logging

Application Metrics

Core Platform Capabilities

What the platform actually does, end to end

Digital Onboarding & Journey Orchestration

Configurable journeys guide customers through registration, plan selection, and product access based on eligibility and business rules — without hard-coded paths.

Membership & Eligibility Engine

Membership plans govern which products and services a customer can access, driven by configurable criteria rather than fixed logic.

Partner Integration Framework

Secure APIs connect third-party partners, each with partner-specific journeys and business rules on a unified platform.

Referral & Campaign Management

Referral tracking, partner attribution, and campaign management support customer acquisition through customers and partners alike.

Reporting & Financial Analytics

Customer reports, financial reports, transaction summaries, and downloadable CSV exports support reconciliation and business decision-making.

Monitoring & Observability

Grafana dashboards, centralized logging, and metrics give operations a real-time view of infrastructure and business health.

System Boundary & Governance

Security and operational discipline, in general terms

The platform's data handling follows layered access control across services, secure cloud storage for financial documents and reports via Amazon S3, and environment isolation between services. Specific certifications and compliance frameworks are intentionally not claimed here — those should only be stated with confirmed, current documentation from the engagement team before publishing.

Operational Shift

Before and after

Before

After

  • New membership plans required core application changes
  • Onboarding and eligibility logic was hard-coded
  • Database load grew directly with customer traffic
  • Documents and reports lacked a consistent storage strategy
  • Operations had no unified view of system health
  • Membership plans and partner journeys are configuration, not rebuilds
  • Journeys adapt dynamically to eligibility and referral source
  • Redis caching absorbs repeat reads, easing database pressure
  • Amazon S3 centralizes secure document and report storage
  • Grafana gives real-time visibility into health and KPIs

Outcomes Observed

What changed for the business

Faster Plan & Policy Releases

Enabled new membership plans and financial policy updates to be released 70–80% faster through configuration-driven workflows.

Faster KPI Dashboard Queries

Reduced average query execution time by approximately 70% for business KPI dashboards by caching frequently accessed metrics in Redis.

Full Real-Time Business Visibility

Provided real-time visibility into 100% of key business metrics, including customer signups, unlocks, membership conversions, product-wise signups, and downgrades through centralized Grafana dashboards.

Why This Matters

A platform built for what comes next

Because the platform is modular and API-first, new membership products, partner ecosystems, and reporting requirements can be layered on without disrupting what's already running. The same architecture that supports today's membership plans is positioned to support additional partner integrations, expanded analytics, and future AI-assisted decisioning as those needs emerge — without a rebuild.

Key Takeaways

The short version

  • — Microservices replaced a rigid core, so new plans and partner journeys are configuration work.
  • — Redis caching keeps customer-facing flows fast as volume grows.
  • — AWS and S3 give the platform durable, scalable infrastructure and secure document storage.
  • — Grafana and centralized logging turned operations from reactive to proactive.
  • — The architecture is built to extend — new partners, products, and analytics don't require a rebuild.

Frequently Asked Questions

Common questions

Why microservices instead of a monolith for a financial platform?

A monolith forces every change through the same release cycle. Independent services let onboarding, membership, referrals, and reporting be built, deployed, and scaled separately — which matters when the business changes faster than one codebase can safely absorb.

How does Redis caching improve the customer experience?

Session data, feature flags, and frequently accessed business data live in memory instead of hitting the database on every request. For a financial product, a slow screen reads as an unreliable one — this closes that gap.

Can new membership plans be launched without rebuilding the platform?

Yes. Membership plans and product eligibility run on configurable business rules, so new plans, partner journeys, and referral programs don't require re-engineering the core application.

How is platform health monitored in production?

Grafana dashboards, centralized logging, and application metrics give operations a single view of infrastructure health and business KPIs, supporting proactive detection instead of reactive troubleshooting.

Let's Talk

Building a financial platform that needs to move as fast as your business?

Sails Software designs and builds cloud-native platforms for regulated, high-stakes industries — where speed and reliability both matter.

Have a project?Talk →