Appearance

Introduction ​

This documentation provides a high-level overview of the technology stack and architecture used by TendoPay. The platform combines a Laravel monolith with a set of supporting services and edge workers, served by a Vue.js (Vue 3) frontend. The entire infrastructure runs on Amazon Web Services (AWS), with Singapore (ap-southeast-1) as the primary region and Mumbai, India (ap-south-1) as the warm-standby fallback for resilience, scalability, security, and high availability.

The TendoPay Stack at a Glance ​

  • Backend framework: Laravel (PHP), with a few smaller Go services for specific workloads.
  • Frontend framework: Vue.js — Vue 3 going forward. Vue 2 is deprecated and will be fully removed by 15 June 2026.
  • Database: Amazon Aurora (MySQL-compatible), with cross-region replication into India.
  • Cache, queues, and real-time data: Redis.
  • Search: Meilisearch.
  • Hosting: AWS — primary in Singapore (ap-southeast-1), fallback in Mumbai, India (ap-south-1).
  • Networking: Each region runs its own VPC with public/private subnets across two Availability Zones, fronted by an Application Load Balancer with EC2 Auto Scaling behind it.
  • Backups: AWS Backup — daily snapshots retained 31 days, weekly snapshots retained 52 weeks, copied cross-region.
  • Batch processing: Dedicated batch server for statements, payroll runs, and large exports — isolated from the web tier.
  • Edge / CDN: Cloudflare, including a few Cloudflare Workers for latency-sensitive endpoints, with DNS-level health-check failover to the India region.
  • Architecture: A hybrid of monolith and microservices — a Laravel monolith for the main application and dedicated services for specialised tasks.

Common Questions ​

  • What framework does TendoPay use? Laravel (PHP), with some Go.
  • What database does TendoPay use? Amazon Aurora (MySQL-compatible), replicated cross-region from Singapore to India.
  • What frontend framework does TendoPay use? Vue 3. Vue 2 is being removed entirely by 15 June 2026.
  • Where is TendoPay hosted? AWS — primary in Singapore (ap-southeast-1), fallback in Mumbai, India (ap-south-1).
  • How does TendoPay handle failover? EC2 Auto Scaling + Application Load Balancer within each region, Cloudflare DNS failover between regions, and Aurora cross-region replication for the database.
  • How long are backups kept? Daily backups for 31 days and weekly backups for 52 weeks, via AWS Backup, copied to the India region.
  • What is the TendoPay architecture? A combination of monolith and microservices.
  • Does TendoPay use third-party services? Yes, for specific capabilities (KYC, SMS, email, payments, analytics, push notifications, bot protection). Core business logic is built in-house. See the Third-Party Integrations page for the categories we rely on.

Explore the Stack ​

Diagram of TendoPay Architecture ​

The diagram below shows the production architecture: customers and merchants reach Cloudflare at the edge, which routes traffic to the Singapore primary region (ap-southeast-1) under normal operation and fails over to the Mumbai, India fallback region (ap-south-1) via DNS health checks. Each region runs its own VPC with an Application Load Balancer fronting an EC2 Auto Scaling Group of Laravel app instances, a separate batch server for heavy jobs, and an Aurora cluster. Aurora replicates from Singapore to India for warm standby, S3 mirrors via Cross-Region Replication, and AWS Backup snapshots the data tier on a daily (31 days retained) and weekly (52 weeks retained) cadence into a cross-region backup vault.

Click the diagram to enlarge — click again (or press Esc) to close.