PRODUCT · LOCAL-FIRST FINANCEActive app

Aura Finance

Understand what you can safely spend, where your money goes and what still needs attention, while keeping the canonical financial workspace on the device first.

Local-first ledgerDeterministic finance rulesHuman-reviewed automation

See the workflow ↓

Aura Finance Actual home view — Actual · complete month

Aura Finance Net home view — Net · repeatable pattern

One ledger.Two useful views of your month.

Why Aura exists

A personal budget should help you decide.

Aura starts from a simple constraint: understanding your finances should not require a cloud backend to become the owner of your complete financial history.

What can I safely spend?

Budget, recorded spending and remaining days become a direct monthly signal.

Where is my money going?

Local reports show category totals, trends, comparisons and exceptional spending.

What still needs my decision?

Alerts, imports and detected Android payments stay visible until the user chooses what belongs in the ledger.

The goal is not more automation. It is more clarity without giving up ownership or control.

What changes

Useful finance software with fewer hidden trade-offs.

Local-first ownership

Transactions, budgets, reports, settings and attachments live on the device first.

The local workspace is the source of truth.

Explainable numbers

Safe-to-spend, pace, totals and comparisons come from deterministic rules that can be traced back to recorded data.

Human-reviewed automation

Imports and Android payment detection reduce manual work without creating irreversible ledger changes.

Optional encrypted continuity

Cloud backup is disabled by default and encrypted on the client before a payload reaches Firestore.

The idea

One local financial workspace.
Clear signals, explicit control.

Aura keeps the canonical ledger on the device, derives its insights through deterministic finance rules, and treats imports or detected payments as proposals until you confirm them.

RecordIncome, expenses, budgets, recurring commitments and goals.

UnderstandSafe-to-spend, pace, trends, category views and comparisons.

ReviewImports and Android payment candidates never silently enter the ledger.

Keep controlPortable data and optional encrypted backup preserve ownership.

Android-only capability

Faster capture. No silent bookkeeping.

On supported Android flows, Aura can recognize a likely payment locally and prepare a structured candidate. The transaction is created only after explicit review.

Detect locallySelected supported notifications are filtered and parsed on-device.

Store minimallyOnly encrypted structured candidates enter the private native queue.

Confirm firstEdit, confirm or ignore before anything becomes a canonical transaction.

Aura Android payment detection review interface

Product proof

From totals to decisions.

The current mobile product turns the feature list into concrete financial questions.

ACTUAL vs NET

Did one large purchase really change my month?

Actual keeps the complete cash record visible. Net separates marked exceptional spending so the repeatable pattern stays readable.

Actual · complete month

Net · repeatable pattern

BUDGET → HISTORY

Where should I act before the month gets away from me?

Budget alerts expose the immediate exception. Category history then shows whether it is a recurring baseline or a temporary spike.

Budget · what needs attention

History · is it a pattern?

COMPARE → REVIEW

What changed, and what still needs my decision?

Period comparison explains the difference. Detected Android payments remain candidates until edited, confirmed or ignored.

Explain · what changed

Review · before recording

Under the hood

Local-first is an architecture boundary.

The shared React product and deterministic financial domain stay separate from Android-only capabilities, while cloud continuity remains optional and encrypted client-side.

Aura Finance local-first technical architecture

React Native / Expo

Cross-platform core product, offline SQLite database, financial state engine and user experience.

Native Android Service

Background notification parsing, payment candidate detection and secure local IPC queue.

Client-Side Encryption

AES-256 encrypted payload serialization before optional Firebase cloud synchronization.

EVIDENCE & LIMITS

The current proof is about ownership, reviewability and explicit boundaries.

Aura demonstrates a local-first financial workspace and reversible automation. It does not turn those properties into unsupported claims about detection accuracy or financial outcomes.

EVIDENCE BOUNDARY

Implemented product boundaries are not outcome guarantees.

The current implementation supports a local source-of-truth ledger, deterministic finance rules, explicit review of Android payment candidates and optional client-side encrypted cloud continuity.

Supported today

Local workspace remains the canonical source of truth
Safe-to-spend and reporting derive from deterministic recorded data
Detected Android payments require explicit review before recording
Optional cloud payloads are encrypted client-side before synchronization

Not claimed here

Comparative payment-detection accuracy benchmark
Measured financial-outcome improvement versus alternative budgeting tools

CONNECTED SYSTEM

Related Android system work

BUILD · INFRASTRUCTUREHarnexReusable on-device AI runtime work

PRODUCT · LOCAL-FIRSTAura FinanceLocal ownership and reviewable automation

MEASURE · OBSERVABILITYTraffic Monitoring AndroidAndroid network-boundary observability

Local-first personal finance

Understand your money. Keep your data yours.

Aura Finance turns financial tracking into an explicit local workflow: record → understand → review → decide.

Explore Aura Finance ↗