Vibecode Finary
track this build5 steps, step by step0%KINDA · weekend project
The dashboard half of Finary is a weekend project: a table of holdings, a price fetcher, a few charts, a history table so you can see net worth over time. The hard half is the plumbing, connecting to hundreds of European banks and brokers through PSD2 aggregators, which needs either a licensed provider or a lot of scraping you do not want to maintain. You can get most of the way with CSV imports from your broker plus public price APIs for equities and crypto, refreshed on a cron. That gets you honest numbers with a monthly chore attached. If the chore is the reason you were paying, this is not a replacement.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Finary. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Finary indie build ## Goal Build the smallest trustworthy replacement for the core Finary workflow for one developer or a tiny team. ## Scope A local dashboard that tracks manually entered or CSV imported holdings, refreshes prices from public APIs, and charts net worth and allocation over time. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Automatic bank and broker sync across hundreds of institutions - Mobile apps with push updates and Face ID - Automated real estate valuation estimates and loan tracking - Benchmarking against other users and the community and content layer - Someone else fixing the connector the day your bank changes its API If those capabilities are essential, use Finary instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local personal net worth tracker. Single user, runs on my machine, no accounts, no cloud, no telemetry. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through better-sqlite3 with plain SQL migrations in /db, Recharts for charts. No ORM, no auth library, no external UI kit. Data model: - accounts: id, name, institution, type (cash, brokerage, retirement, crypto, property, loan), currency - holdings: id, account_id, symbol (nullable), quantity, manual_value (nullable), cost_basis (nullable) - prices: symbol, date, close, currency - snapshots: date, total_value, breakdown_json Features: 1. CRUD pages for accounts and holdings. Holdings are either priced by symbol or carry a manual value for things like property and cash. 2. CSV import at /import: paste or upload a CSV, map columns to symbol, quantity, cost basis, pick the target account, preview before commit. 3. A price refresh route that pulls crypto quotes from CoinGecko and equity or ETF quotes from a single configurable HTTP quote endpoint. Cache into the prices table, never hit the network on page render. 4. A snapshot script, npm run snapshot, that recomputes total net worth and writes one row to snapshots. Document how to run it daily with cron or Task Scheduler. 5. Dashboard: total net worth, net worth line chart from snapshots, allocation donut by asset type, table of holdings with value, weight, and gain versus cost basis. 6. Multi currency: store a base currency in .env, fetch FX rates in the same refresh job, convert everything to base for display. Out of scope, do not attempt: bank or broker account linking, open banking or PSD2 aggregators, credential scraping, mobile apps, multi user support, tax reporting. Secrets in .env.example: BASE_CURRENCY, COINGECKO_API_KEY, QUOTE_API_URL, QUOTE_API_KEY, FX_API_URL. Never commit real keys. Seed the database with three fake accounts and eight holdings so the dashboard is not empty on first run. Write a README with setup, refresh, and snapshot instructions in under thirty lines. ## Required capabilities - Node 20 and a machine that can run a cron job or scheduled task - CSV exports or manual entry for each account you hold - A free crypto price API key and a source for equity and ETF quotes - Manual valuations for illiquid assets like property ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Finary. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Finary indie build ## Goal Build the smallest trustworthy replacement for the core Finary workflow for one developer or a tiny team. ## Scope A local dashboard that tracks manually entered or CSV imported holdings, refreshes prices from public APIs, and charts net worth and allocation over time. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Automatic bank and broker sync across hundreds of institutions - Mobile apps with push updates and Face ID - Automated real estate valuation estimates and loan tracking - Benchmarking against other users and the community and content layer - Someone else fixing the connector the day your bank changes its API If those capabilities are essential, use Finary instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local personal net worth tracker. Single user, runs on my machine, no accounts, no cloud, no telemetry. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through better-sqlite3 with plain SQL migrations in /db, Recharts for charts. No ORM, no auth library, no external UI kit. Data model: - accounts: id, name, institution, type (cash, brokerage, retirement, crypto, property, loan), currency - holdings: id, account_id, symbol (nullable), quantity, manual_value (nullable), cost_basis (nullable) - prices: symbol, date, close, currency - snapshots: date, total_value, breakdown_json Features: 1. CRUD pages for accounts and holdings. Holdings are either priced by symbol or carry a manual value for things like property and cash. 2. CSV import at /import: paste or upload a CSV, map columns to symbol, quantity, cost basis, pick the target account, preview before commit. 3. A price refresh route that pulls crypto quotes from CoinGecko and equity or ETF quotes from a single configurable HTTP quote endpoint. Cache into the prices table, never hit the network on page render. 4. A snapshot script, npm run snapshot, that recomputes total net worth and writes one row to snapshots. Document how to run it daily with cron or Task Scheduler. 5. Dashboard: total net worth, net worth line chart from snapshots, allocation donut by asset type, table of holdings with value, weight, and gain versus cost basis. 6. Multi currency: store a base currency in .env, fetch FX rates in the same refresh job, convert everything to base for display. Out of scope, do not attempt: bank or broker account linking, open banking or PSD2 aggregators, credential scraping, mobile apps, multi user support, tax reporting. Secrets in .env.example: BASE_CURRENCY, COINGECKO_API_KEY, QUOTE_API_URL, QUOTE_API_KEY, FX_API_URL. Never commit real keys. Seed the database with three fake accounts and eight holdings so the dashboard is not empty on first run. Write a README with setup, refresh, and snapshot instructions in under thirty lines. ## Required capabilities - Node 20 and a machine that can run a cron job or scheduled task - CSV exports or manual entry for each account you hold - A free crypto price API key and a source for equity and ETF quotes - Manual valuations for illiquid assets like property ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Finary. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Finary product brief ## Problem The dashboard half of Finary is a weekend project: a table of holdings, a price fetcher, a few charts, a history table so you can see net worth over time. The hard half is the plumbing, connecting to hundreds of European banks and brokers through PSD2 aggregators, which needs either a licensed provider or a lot of scraping you do not want to maintain. You can get most of the way with CSV imports from your broker plus public price APIs for equities and crypto, refreshed on a cron. That gets you honest numbers with a monthly chore attached. If the chore is the reason you were paying, this is not a replacement. ## Product outcome A local dashboard that tracks manually entered or CSV imported holdings, refreshes prices from public APIs, and charts net worth and allocation over time. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a machine that can run a cron job or scheduled task - CSV exports or manual entry for each account you hold - A free crypto price API key and a source for equity and ETF quotes - Manual valuations for illiquid assets like property ## Explicit non-goals for v1 - Automatic bank and broker sync across hundreds of institutions - Mobile apps with push updates and Face ID - Automated real estate valuation estimates and loan tracking - Benchmarking against other users and the community and content layer - Someone else fixing the connector the day your bank changes its API ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a local personal net worth tracker. Single user, runs on my machine, no accounts, no cloud, no telemetry. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through better-sqlite3 with plain SQL migrations in /db, Recharts for charts. No ORM, no auth library, no external UI kit. Data model: - accounts: id, name, institution, type (cash, brokerage, retirement, crypto, property, loan), currency - holdings: id, account_id, symbol (nullable), quantity, manual_value (nullable), cost_basis (nullable) - prices: symbol, date, close, currency - snapshots: date, total_value, breakdown_json Features: 1. CRUD pages for accounts and holdings. Holdings are either priced by symbol or carry a manual value for things like property and cash. 2. CSV import at /import: paste or upload a CSV, map columns to symbol, quantity, cost basis, pick the target account, preview before commit. 3. A price refresh route that pulls crypto quotes from CoinGecko and equity or ETF quotes from a single configurable HTTP quote endpoint. Cache into the prices table, never hit the network on page render. 4. A snapshot script, npm run snapshot, that recomputes total net worth and writes one row to snapshots. Document how to run it daily with cron or Task Scheduler. 5. Dashboard: total net worth, net worth line chart from snapshots, allocation donut by asset type, table of holdings with value, weight, and gain versus cost basis. 6. Multi currency: store a base currency in .env, fetch FX rates in the same refresh job, convert everything to base for display. Out of scope, do not attempt: bank or broker account linking, open banking or PSD2 aggregators, credential scraping, mobile apps, multi user support, tax reporting. Secrets in .env.example: BASE_CURRENCY, COINGECKO_API_KEY, QUOTE_API_URL, QUOTE_API_KEY, FX_API_URL. Never commit real keys. Seed the database with three fake accounts and eight holdings so the dashboard is not empty on first run. Write a README with setup, refresh, and snapshot instructions in under thirty lines. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Finary capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Finary indie build ## Goal Build the smallest trustworthy replacement for the core Finary workflow for one developer or a tiny team. ## Scope A local dashboard that tracks manually entered or CSV imported holdings, refreshes prices from public APIs, and charts net worth and allocation over time. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Automatic bank and broker sync across hundreds of institutions - Mobile apps with push updates and Face ID - Automated real estate valuation estimates and loan tracking - Benchmarking against other users and the community and content layer - Someone else fixing the connector the day your bank changes its API If those capabilities are essential, use Finary instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a local personal net worth tracker. Single user, runs on my machine, no accounts, no cloud, no telemetry. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through better-sqlite3 with plain SQL migrations in /db, Recharts for charts. No ORM, no auth library, no external UI kit. Data model: - accounts: id, name, institution, type (cash, brokerage, retirement, crypto, property, loan), currency - holdings: id, account_id, symbol (nullable), quantity, manual_value (nullable), cost_basis (nullable) - prices: symbol, date, close, currency - snapshots: date, total_value, breakdown_json Features: 1. CRUD pages for accounts and holdings. Holdings are either priced by symbol or carry a manual value for things like property and cash. 2. CSV import at /import: paste or upload a CSV, map columns to symbol, quantity, cost basis, pick the target account, preview before commit. 3. A price refresh route that pulls crypto quotes from CoinGecko and equity or ETF quotes from a single configurable HTTP quote endpoint. Cache into the prices table, never hit the network on page render. 4. A snapshot script, npm run snapshot, that recomputes total net worth and writes one row to snapshots. Document how to run it daily with cron or Task Scheduler. 5. Dashboard: total net worth, net worth line chart from snapshots, allocation donut by asset type, table of holdings with value, weight, and gain versus cost basis. 6. Multi currency: store a base currency in .env, fetch FX rates in the same refresh job, convert everything to base for display. Out of scope, do not attempt: bank or broker account linking, open banking or PSD2 aggregators, credential scraping, mobile apps, multi user support, tax reporting. Secrets in .env.example: BASE_CURRENCY, COINGECKO_API_KEY, QUOTE_API_URL, QUOTE_API_KEY, FX_API_URL. Never commit real keys. Seed the database with three fake accounts and eight holdings so the dashboard is not empty on first run. Write a README with setup, refresh, and snapshot instructions in under thirty lines. ## Required capabilities - Node 20 and a machine that can run a cron job or scheduled task - CSV exports or manual entry for each account you hold - A free crypto price API key and a source for equity and ETF quotes - Manual valuations for illiquid assets like property ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Finary product brief ## Problem The dashboard half of Finary is a weekend project: a table of holdings, a price fetcher, a few charts, a history table so you can see net worth over time. The hard half is the plumbing, connecting to hundreds of European banks and brokers through PSD2 aggregators, which needs either a licensed provider or a lot of scraping you do not want to maintain. You can get most of the way with CSV imports from your broker plus public price APIs for equities and crypto, refreshed on a cron. That gets you honest numbers with a monthly chore attached. If the chore is the reason you were paying, this is not a replacement. ## Product outcome A local dashboard that tracks manually entered or CSV imported holdings, refreshes prices from public APIs, and charts net worth and allocation over time. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a machine that can run a cron job or scheduled task - CSV exports or manual entry for each account you hold - A free crypto price API key and a source for equity and ETF quotes - Manual valuations for illiquid assets like property ## Explicit non-goals for v1 - Automatic bank and broker sync across hundreds of institutions - Mobile apps with push updates and Face ID - Automated real estate valuation estimates and loan tracking - Benchmarking against other users and the community and content layer - Someone else fixing the connector the day your bank changes its API ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a local personal net worth tracker. Single user, runs on my machine, no accounts, no cloud, no telemetry. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through better-sqlite3 with plain SQL migrations in /db, Recharts for charts. No ORM, no auth library, no external UI kit. Data model: - accounts: id, name, institution, type (cash, brokerage, retirement, crypto, property, loan), currency - holdings: id, account_id, symbol (nullable), quantity, manual_value (nullable), cost_basis (nullable) - prices: symbol, date, close, currency - snapshots: date, total_value, breakdown_json Features: 1. CRUD pages for accounts and holdings. Holdings are either priced by symbol or carry a manual value for things like property and cash. 2. CSV import at /import: paste or upload a CSV, map columns to symbol, quantity, cost basis, pick the target account, preview before commit. 3. A price refresh route that pulls crypto quotes from CoinGecko and equity or ETF quotes from a single configurable HTTP quote endpoint. Cache into the prices table, never hit the network on page render. 4. A snapshot script, npm run snapshot, that recomputes total net worth and writes one row to snapshots. Document how to run it daily with cron or Task Scheduler. 5. Dashboard: total net worth, net worth line chart from snapshots, allocation donut by asset type, table of holdings with value, weight, and gain versus cost basis. 6. Multi currency: store a base currency in .env, fetch FX rates in the same refresh job, convert everything to base for display. Out of scope, do not attempt: bank or broker account linking, open banking or PSD2 aggregators, credential scraping, mobile apps, multi user support, tax reporting. Secrets in .env.example: BASE_CURRENCY, COINGECKO_API_KEY, QUOTE_API_URL, QUOTE_API_KEY, FX_API_URL. Never commit real keys. Seed the database with three fake accounts and eight holdings so the dashboard is not empty on first run. Write a README with setup, refresh, and snapshot instructions in under thirty lines. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Finary capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Because nobody actually keeps a spreadsheet updated for two years. Finary's pitch is that you connect once and then your net worth is just correct every morning, including the accounts you forget about, and that only works if someone maintains regulated connections to your specific bank in your specific country. The DIY build is honest and private and free, but it asks you for fifteen minutes of CSV wrangling a month, and most people quietly stop doing that around month three.
xAutomatic bank and broker sync across hundreds of institutions
xMobile apps with push updates and Face ID
xAutomated real estate valuation estimates and loan tracking
xBenchmarking against other users and the community and content layer
xSomeone else fixing the connector the day your bank changes its API
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Finary ($14.5/mo) with one prompt"
Vibecode Finary
Kinda. The core of Finary is buildable in a weekend with the prompt on this page, but there are real gaps: Automatic bank and broker sync across hundreds of institutions, Mobile apps with push updates and Face ID. Read the honest list above before committing.
How much does Finary cost?
Finary costs about $14.5/month (Finary Plus, checked 2026-08-18), which is $174 per year.
What do I lose by replacing Finary?
Honestly: Automatic bank and broker sync across hundreds of institutions; Mobile apps with push updates and Face ID; Automated real estate valuation estimates and loan tracking; Benchmarking against other users and the community and content layer; Someone else fixing the connector the day your bank changes its API. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Finary?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.