Architecture Overview
The Finaisse/Blitz platform consists of three repositories:
| Repo | Purpose |
|---|---|
blitz | Bun/Elysia microservices monorepo (backend) |
blitz-ui | Vue 3 / Vuetify frontend monorepo |
fin-infra | IaC, CI/CD workflows, operational scripts |
Start here for the platform picture
Platform Architecture (Golden Copy) is the canonical, deck-facing architecture of record — the "layer cake" diagram every external artifact (Platform deck, Security & Trust deck, website) must match. If the code and a slide disagree, that doc — verified against code — wins.
System Design
Component-level reference — what each subsystem is, its parts, and how it fits together.
- Backend Services
- Frontend
- App Switcher Shortcuts — keyboard navigation between apps, and why those keys
- Infrastructure
- Multi-Tenancy Model — how a tenant is put together, routing, adding/deleting a tenant
- AWS Architecture
Decision Records
Point-in-time design decisions and status logs — not living component reference, and not step-by-step procedures (those live under Platform Operations).
- Release Management — Decision note: versioned/identifiable/reversible releases via per-service tags + a release manifest, Railway now and AWS ECS later
- Deploy Scope & Digests — What each deploy target scales up; why digests change; deploy-only-changed vs SHA-pinning
- Observability & Usage Telemetry — One framework for operational and usage signals across the platform
- LLM Token-Usage Capture — Per-call LLM token usage capture design
- AWS Implementation — Progress log for the AWS production setup
- Gaps & Roadmap — Current limitations and future steps