Skip to content
Budgeti

Budgeti

Budgeti is a full-stack mobile finance app built to help people register expenses quickly and make better financial decisions.

Today, the most production-ready component is the backend, so this site documents backend architecture, runtime behavior, and API modules in depth.

Why Budgeti

Section titled “Why Budgeti”

Budgeti addresses common personal-finance friction points:

  • Low visibility into where money goes.
  • Disorder when recording transactions across different moments and channels.
  • Shared-finance coordination pain between people who manage money together.

The product combines core finance workflows (auth, wallets, categories, transactions, budgets, dashboard analytics) with useful AI in the current MVP:

  • Receipt-photo OCR via a capture assistant.
  • Voice-command transaction entry.

Promise: Register quickly and decide better.

Positioning: mobile-first finance with practical AI features that reduce manual effort.

Section titled “Recommended reading path”
  1. Start with What is Budgeti Backend and Architecture Map.
  2. Read Runtime to understand how process boot and dependencies are wired.
  3. Go module by module in API and follow route-to-file traceability tables.
  4. Validate quality posture in Testing and Operations.
  5. Use Quick Testing Access to run a fast reviewer smoke flow.
  6. Use Module Index as a quick file navigation reference.

Documentation scope

Section titled “Documentation scope”
  • Primary scope now: backend technical documentation.
  • Product context included: full Budgeti direction, use cases, and AI trajectory.
  • Goal: keep contributors aligned with both current implementation and product intent.

Product trajectory

Section titled “Product trajectory”
  • Current AI stage: capture assistant for receipt OCR and voice transaction capture.
  • Next stage: richer agentic finance insights that help users act, not only record.
  • Long-term product goal: become the integral app where users centralize finances.

Scope and guarantees

Section titled “Scope and guarantees”
  • API base path: /api/v1.
  • Health endpoint: /health.
  • Categories canonical route: /categories, with compatibility alias /category.
  • Test snapshot used in this docs version: 26 files passed / 217 tests passed (snapshot date noted in testing section).

Source of truth

Section titled “Source of truth”
  • Backend code: budgeti/backend.
  • Backend README contract and operational context: budgeti/backend/README.md.