Fintech · Cross-border payments

Stabled

Moving money across borders in seconds — at a fraction of bank fees.

stabled.co
stabled.co
Client
Stabled
Industry
Fintech · Cross-border payments
Services
Cloud architecture · DevOps · IaC
Platforms
AWS Organizations · ECS Fargate · Aurora Serverless v2
The challenge

Building payments infrastructure that earns trust

Stabled needed a platform capable of settling cross-border USDC transactions the moment they landed — with the reliability and security posture that a fintech demands. The infrastructure had to be auditable, multi-environment, and built from day one as infrastructure as code.

The team was moving fast, but they needed a foundation that could grow without being rewritten — one that separated concerns at the AWS account level, and gave developers clear deployment paths from every commit.

The solution

Multi-account architecture for isolation and speed

  1. We structured Stabled under AWS Organizations from day one, giving production its own account isolated from staging and tooling. A misconfiguration in a non-prod environment literally cannot reach production — the blast radius is bounded by the account boundary.

  2. Three independent microservices — the landing page, the customer-facing web app, and the backend API — each run as a separate ECS Fargate service, scaling independently behind a unified Application Load Balancer. Aurora PostgreSQL Serverless v2 handles persistent state, automatically scaling database compute with workload demand rather than requiring manual resizing. Every resource is defined in Terraform, versioned in Git, and deployable without manual console access.

  3. GitHub Actions drives CI/CD — on every push to the main branch, images are built, tested, pushed to ECR, and deployed to ECS with a zero-downtime rolling update. The pipeline also applies Terraform changes after plan approval, so infrastructure drift is caught before it reaches production.

Architecture
AWS Organizations
Each AWS account is a blast-radius boundary — production cannot be touched by staging accidents.
Tech stack

Tools we used

  • AWS Organizations Multi-account isolation
  • ECS Fargate Serverless containers
  • Application Load Balancer Traffic distribution
  • Aurora PostgreSQL Serverless v2 Auto-scaling managed database
  • ECR Container registry
  • GitHub Actions CI/CD pipeline
  • Terraform Infrastructure as code
  • VPC + Private subnets Network isolation
Results

Production-grade from the start

99.9% uptime SLA
<2s settlement latency
0 production incidents at launch
100% infrastructure as code
"With Pluralty we deployed our platform's infrastructure in an organized way, following cloud best practices from day one. The multi-account structure gave us the confidence to ship fast without breaking things."
Nikolaus Seiguer CEO, Stabled
Want the same for your platform?

Let's talk about your infrastructure

Whether you're starting fresh or modernizing an existing setup, we'll tell you exactly what to build and in what order.

Get your free assessment