Paisa Hosting

How Paisa works

Paisa builds on Ledger double-entry accounting. Transactions, accounts, commodities, and configuration remain in plain-text files, while the web interface turns that journal into account views, expense reports, budgets, recurring-payment calendars, investment valuations, goals, tax calculations, and other visualisations. An editor adds syntax highlighting, completion, validation, and formatting assistance for the underlying journal.

Import tools can convert configured CSV, spreadsheet, or PDF statements into Ledger entries, but imported transactions still require review and categorisation. Market-price tracking can use supported providers or manual prices. Results depend on the journal, commodity definitions, price sources, locale, tax assumptions, and formulas supplied by the user; Paisa does not reconcile a bank account or certify an accounting result.

Key Paisa features

The catalogue mounts /data as the persistent Paisa workspace. Financial journals and configuration should remain inside that volume so they survive application replacement and are included with scheduled backups. Plain text also permits independent versioning, but a version-control service, repository, encryption key management, and collaborative approval process are not included in the hosted package.

Paisa includes user-authentication options upstream, yet administrators remain responsible for account setup and access policy. External price providers, statement formats, tax rules, exchange rates, and investment identifiers can change. Sensitive reports should be checked against original statements and professional advice before they drive tax, legal, investment, or lending decisions.

Who uses Paisa

Plain-text accounting users can explore a Ledger journal visually, households can track spending and goals, and technically inclined investors can monitor holdings with supported price sources. Consultants may also use separate journals for scenario analysis, provided each dataset has an appropriate access and retention policy.

Paisa is not a bank feed, bookkeeping firm, tax adviser, investment adviser, payment service, audit system, or source of certified market data. People who need automatic institution connections, regulated advice, multi-entity controls, or statutory reporting should use appropriately governed services.

Self-hosting Paisa: requirements and cost

Paisa resource use depends on journal size, imported statements, number of accounts and commodities, price updates, analyses, interactive sheets, and concurrent users. PostgreSQL and MariaDB are Not required in the catalogue; persistent files live in /data. The application carries no separate software charge, while data quality and external price calls usually matter more than raw compute for a personal journal.

On AvaHost, Paisa uses Plan 1 at €2. The hosted Paisa package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package does not include bank connections, a version-control repository, bookkeeping review, tax validation, market-data guarantees, investment advice, encryption-key custody, or professional reconciliation. Users must keep source statements and verify every imported or calculated result.