devopsly.Let’s talk
HomeWorkFinancial platform
← Selected work

Fintech product / Flyfish

Build what happens
behind the card.

A debit card product needs more than an interface. Devopsly built the financial ledger, cloud infrastructure and delivery pipelines supporting Flyfish’s card issuance platform.

From product to platform
ProductDebit card issuanceApplications + a financial ledger
ReleaseGitHub ActionsDelivery pipelines + blue-green deployments
RuntimeAmazon EKSKubernetes + application infrastructure
FoundationAWS, defined in TerraformNetworking, data services + security controls
System illustration · Platform layers, shown conceptually.

At a glance

Client
Flyfish: business banking and card issuance.
Constraint
A card product to launch across EU and APAC markets under regulatory deadlines.
Contribution
The financial ledger, AWS infrastructure defined in Terraform, Kubernetes on EKS and the release pipelines.
Result
More frequent deployments and shorter recovery times after the platform work.

01 / The brief

The product launch
starts below the surface.

Flyfish was preparing to launch debit card issuance across EU and APAC markets under regulatory deadlines.

The engineering work covered the record of financial activity, the infrastructure running the services and the process for releasing changes. Those parts needed to be considered together.

Security requirements shaped the infrastructure. The delivery included encryption and web application security controls alongside networking, data services and application deployment.

Flyfish business dashboard showing accounts in several currencies, company cards and recent transactions.
Product image · Flyfish’s business dashboard, the product this platform runs. The interface is Flyfish’s own design; the engagement was the ledger, infrastructure and delivery beneath it.

02 / What we built

One platform.
Several connected responsibilities.

The scope ran from financial data design to the repeatable infrastructure and release process around it.

Financial records

A ledger from the ground up.

Devopsly designed the financial ledger to retain transaction history, making the financial record an explicit part of the architecture.

Cloud foundation

Infrastructure defined in code.

Modular Terraform configuration described the AWS infrastructure, including multi-zone networking, EKS Fargate and Aurora RDS.

Application delivery

A repeatable path to release.

GitHub Actions pipelines supported blue-green deployments. KMS encryption and AWS WAF formed part of the platform’s security controls.

The engineering decision

Make the foundation
inspectable and repeatable.

Terraform expresses infrastructure as configuration that can be reviewed and reapplied. Delivery pipelines express the path from a code change to a release.

In this project, both sat alongside the ledger and application runtime. That connected scope is the point: the product and what it runs on were part of the same brief.

03 / The result

A working foundation
for card issuance.

The delivered platform brought financial records, AWS infrastructure and application delivery together for the card issuance product.

After the platform work, deployments became more frequent and recovery times shorter.

A qualitative result, as reported by Devopsly.

A similar challenge?

Bring the product.
And the operational reality.

A platform brief should cover what the product needs to do and how your team will release, observe and recover it.

Discuss your platform

More selected work

Different problems. The same care.