Deploy Paisa

Personal finance dashboards from plain-text ledger files, with a login

Deploy Paisa

/root/Documents/paisa

Deploy and Host Paisa on Railway

Paisa is an open-source personal finance manager (AGPL-3.0) built on plain-text accounting. You keep your transactions in ledger, hledger or beancount journal files, and Paisa turns them into dashboards for net worth, income and expenses, budgets, investments, goals, credit cards and capital gains. This template deploys Paisa v0.8.0 behind a login.

About Hosting Paisa

Paisa is a single Go binary that serves its web UI and reads your journal with the ledger, hledger or beancount command-line tools. Everything it needs lives in one folder: paisa.yaml (configuration), your journal files, spreadsheets and a SQLite cache (paisa.db). This template runs one service built from the official image, keeps that folder on a Railway volume, and serves it on a Railway domain with a health check. Upstream Paisa has no login until you add one, so the template creates the admin account from a generated password before the UI starts, and the service exits (and Railway restarts it) if Paisa stops.

Common Use Cases

  • Track spending, income and net worth from a ledger, hledger or beancount journal you write by hand or import from bank statements
  • Follow budgets, savings and retirement goals, recurring payments and credit cards in one dashboard
  • Review investments, asset allocation and capital gains (including Indian tax reports such as Schedule AL)

Dependencies for Paisa Hosting

  • Paisa (one service, data on a Railway volume)

Deployment Dependencies

Implementation Details

After you deploy: open the Paisa service's Variables tab and copy PAISA_PASSWORD (generated at deploy). Open the public URL and sign in as admin with that password. Your data starts empty: write transactions in the Editor, import a bank CSV from the Import page, or click "Setup Demo" on the empty dashboard to explore with sample data (it replaces paisa.yaml and main.ledger, so use it only on a fresh deploy). Then open Config to set your default_currency and locale (Paisa defaults to INR and en-IN).

Login: to change the password or the username, change PAISA_PASSWORD or PAISA_USERNAME on the service and redeploy. On every start the template writes that account into paisa.yaml (stored as Paisa's own SHA-256 hash), and it puts it back if Paisa's "Setup Demo" button or a config edit removes all user accounts. Other accounts you add in Config stay.

Data: the volume at /root/Documents/paisa holds paisa.yaml, main.ledger, sheets and paisa.db, so it survives redeploys and restarts. Back up that folder (or keep your journal in git) if your finances matter to you.

Ledger tools: the image includes ledger, hledger and beancount. Pick one with ledger_cli in Config.

Resources: it runs within 0.5 GB of RAM and 1 vCPU, so it works on Railway's Free and Trial plans. Large journals with many years of prices sync faster with more memory.

Updates: the service builds from this GitHub repo, which pins the official image by version and digest. When we bump the version, Railway shows an update in your project; read the changelog in the repo first, then apply it.

Why Deploy Paisa on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Paisa on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0