Project

Woko - AMKA Platform

I built the full-stack AMKA portfolio management platform for Woko, covering the web app, API services, infrastructure, and CI/CD (the mobile client was delivered by a separate team).

  • AWS
  • Serverless
  • Go
  • React
  • CI/CD
Woko - AMKA Platform architecture diagram preview
Key outcomes
  • We unified back-office flows for credit origination, payments, and portfolio management.
  • Serverless API foundation with secure identity flows and notification pipelines.
  • Infrastructure and repeatable deployments with CloudFormation and CI/CD in GitLab.
Role and stack
Full-stack and infrastructure lead AWS Serverless Go + Laravel CI/CD (GitLab)

Scope note: I owned the web platform, the APIs, and the infrastructure. The mobile client was delivered by a separate team.

Architecture overview

A high-level view of Woko's request flow, the serverless services, the identity layer, and operational telemetry.

Open full size
Key: Solid = request/data path. Dashed = control + telemetry. Thin solid = CI/CD automation.
Woko AMKA architecture diagram
Key points
  • Request path: Route 53 routes customer traffic through API Gateway to Lambda services.
  • Service layer: domain functions manage user identity, credit lifecycle, and payment operations.
  • Controls: Cognito, SNS notifications, and CloudWatch logs support security and traceability.
Core components
API Gateway Lambda DynamoDB Cognito SNS S3 CloudWatch

SRE approach

Reliability architecture
  • Edge: Route 53 + API Gateway for managed ingress and routing.
  • Services: Lambda-based domains for user flows, credit, and payments.
  • Data: DynamoDB tables tuned for customer access and credit requests.
Security and compliance
  • Identity: Cognito user pools and token validation in APIs.
  • Access: IAM roles scoped per Lambda service.
  • Auditability: CloudWatch logs and notification traces for operations.
Operational excellence
  • IaC: CloudFormation templates for API and service stacks.
  • CI/CD: GitLab pipelines for build, test, and deploy.
  • Ops: Repeatable environment setup and automated releases.

Results

Serverless API foundation Automated releases Portfolio operations ready Audit-ready logs

AMKA now provides a reliable, secure operational backbone for credit flows, keeping deployments lightweight and operations lean.

Outcome

A unified back-office platform that enables daily credit operations and portfolio oversight.

How

Modular Lambda services backed by DynamoDB and IaC-driven deployments.

Project URL

Public marketing site for Woko.

Visit woko.com.mx Marketing site

Lessons learned

Owning the full-stack platform reinforced the value of clear domain boundaries, serverless scale, and repeatable infrastructure. Designing the admin experience, APIs, and operations together helped the team ship faster and with higher reliability.