# Technology Stack

## Backend
- PHP 8.4 baseline
- Laravel 13
- Modular Monolith
- Blade server-rendered views
- Laravel queues/jobs for later asynchronous work

## Database
- MySQL 8-compatible production database
- SQLite supported for local/testing
- InnoDB/transactional tables required for financial phases

## Frontend
- Blade Components
- central CSS design tokens/components
- small native JavaScript layer
- Vite production build with hashed assets

## PWA
- Web App Manifest
- Service Worker
- standalone install mode
- offline fallback
- hashed immutable static assets
- service-worker file served with no-cache

## Why this stack

The product has strongly transactional financial operations and several
server-side integrations. A Laravel modular monolith gives one transactional
database boundary and mature authentication, validation, migrations, queues,
cache and filesystem abstractions, while avoiding the operational overhead of
microservices before scale justifies them.

Blade + a central component/design system keeps the admin/user interface
fast, mobile-first and easy to host without requiring a separate SPA runtime.