The problem
Knowing before the month ends whether the family budget closes, with no spreadsheet, on everyone's phone, and with a low, predictable cloud bill.
Only through GitHub. Every push to main runs CI and, when green, the deploy: Pulumi Java applies infra, API and Cloudflare DNS; the site uploads in a safe order; the APK ships only if web or mobile changed. AWS credentials are temporary, through OIDC.
Decisions and why
- OIDC, no keys in GitHub
- GitHub assumes a role, only from main. There is no access key to leak.
- The deploy role lives outside Pulumi
- The deploy cannot change its own permissions.
- Hashed assets before HTML
- Someone with the page open during a deploy never gets new HTML pointing at JS that is not uploaded yet.
- APK only when needed
- It compares the commit stored in version.json: an API-only change does not make the family download a new app.
- Pulumi state in S3
- No paid state service; encrypted and versioned in the deploy bucket itself.
requestresponse
Pick a scenario above to watch the message travel through the architecture.
What it looks like
Replica of the real dashboard with fictional data mesfecho.com/dashboard
Dashboard Novembro de 2026
Transações do mêsR$2,708.80
PagoR$2,199.00
A pagarR$509.80
81% Pagas x pendentesMarque contas como pagas em Transações e veja o gráfico mudar.