Deploy ezBookkeeping
Self-hosted personal finance app with SQLite on a volume, no sign-up
ezBookkeeping
Just deployed
/ezbookkeeping/data
Deploy and Host ezBookkeeping on Railway
ezBookkeeping is an open-source (MIT), self-hosted personal finance app. It records daily income, expenses and transfers across accounts and currencies, imports statements from many file formats, and has charts and custom queries for spending analysis. It has separate mobile and desktop web interfaces and can be installed as a PWA.
About Hosting ezBookkeeping
ezBookkeeping is a single Go binary that serves both the web app and its API. This template runs version 2.1.1 from the official Docker image, pinned by digest, as one Railway service with a public HTTPS domain. The SQLite database and uploaded files (avatars, custom icons, transaction pictures) live on one Railway volume, so they survive redeploys and updates. On first boot the start script creates your account from the deploy-form variables, with a generated password. Public sign-up stays off, signing keys are generated, and the app upgrades its own database tables when a new version starts.
Common Use Cases
- Track personal or household income, expenses, transfers and budgets across several accounts and currencies
- Import bank, credit card or other finance-app exports (CSV, OFX, QIF, Camt, MT940 and more) and analyse spending with charts
- Keep a private finance ledger you control, reachable from phone and desktop browsers as a PWA
Dependencies for ezBookkeeping Hosting
- The official
mayswind/ezbookkeepingDocker image (2.1.1) - A Railway volume for the SQLite database and uploaded files
Deployment Dependencies
- ezBookkeeping source and releases: https://github.com/mayswind/ezbookkeeping/releases
- Documentation and configuration reference: https://ezbookkeeping.mayswind.net/configuration
- Template repository: https://github.com/aalfath/ezbookkeeping-railway-template
Implementation Details
The deploy form asks only for ADMIN_EMAIL. After the deploy, sign in at your Railway domain with the username admin (or the ADMIN_USERNAME you set) and the generated ADMIN_PASSWORD from the service's Variables tab, then change the password in the app. Editing the variable later doesn't change it.
Other users: set EBK_USER_ENABLE_REGISTER=true to allow sign-up, or add accounts while it is on and turn it off again.
Any setting from the configuration reference can be added as an EBK_SECTION_KEY variable, for example SMTP mail (EBK_MAIL_ENABLE_SMTP, EBK_MAIL_SMTP_HOST, EBK_MAIL_FROM_ADDRESS), OIDC login (EBK_AUTH_ENABLE_OAUTH2_AUTH), AI receipt recognition (EBK_LLM_...) or the MCP server (EBK_MCP_ENABLE_MCP).
Updates: the service builds from the template repository, so Railway shows an update notice when a new version is merged there. Read its CHANGELOG first and back up the volume before a major upgrade.
Why Deploy ezBookkeeping 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 ezBookkeeping 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
ezBookkeeping
aalfath/ezbookkeeping-railway-templateADMIN_EMAIL
Email address of your first ezBookkeeping account (created on first boot).
