Finance and accounting decision
TRYA
A capable developer can reproduce the core budgeting, CSV import and recurring-detection features or self-host existing projects (Firefly III, Actual), but reproducing TRY A's bank aggregation across 31 countries, app-store presence and its integrated AI coach at parity is not realistic for a single developer without using third-party paid aggregation services.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off74 h to build
$25/mo4 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All TRYA alternatives, with the arithmetic →
What a replacement has to do
- Import transactions, categorize them, show budgets and balances, detect recurring charges, and answer simple budgeting questions via an LLM assistant.
What it still won’t have
- Bank aggregation / live sync across 31 countries
- Mobile native apps and app-store distribution
- Pre-built store ratings and user acquisition
- Proprietary AI coach tuned to user data (TRYA's 'Sol')
- Lifetime paid tier and its bundled features
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
TRYA does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hostable personal budgeting web app using Postgres, Node.js (Express), a simple worker (Bull or Node cron), and React. In scope: user auth, CSV transaction import with a mapping UI, normalized Postgres schema for users/accounts/transactions/budgets/categories, budget calculation endpoints, a scheduled recurring-payment detection job, a React SPA with transaction list, budget views, and basic reports, and an optional backend route that proxies user prompts to OpenAI for a simple budgeting assistant. Out of scope: direct bank aggregation/PSD2 connectors, mobile native apps, multi-tenant billing. Include error handling, input validation, unit tests for core logic (CSV parsing, budget calculations, recurring detection), and a Docker Compose deployment for Postgres + app + worker.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productTRYA - Application de budget pour tes finances personnelles
- official pricingTRYA pricing
- open sourceactualbudget/actual
- open sourcefirefly-iii/firefly-iii
Integrity checks
What held up, and what did not.
