Sure

A community fork of the abandoned Maybe Finance project, honestly reviewed. Open-source personal finance, self-hosted on your own server.

---

TL;DR

• What it is: A full-featured personal finance and wealth management app — bank account tracking, budgeting, transactions, and an AI assistant — running on your own server under AGPL-3.0 [README].
• Who it’s for: Non-technical founders and individuals paying $10–15/mo for YNAB, Monarch, or Copilot who want the same depth of features without a recurring SaaS bill, and who are comfortable with (or willing to learn) Docker deployment [README][homepage].
• Backstory: This is a community fork of Maybe Finance, a startup that spent ~$1 million building a personal finance platform before failing as a business and open-sourcing the code. Sure picks up where they left off [README].
• Cost savings: YNAB runs $99/year. Monarch Money is similar. Sure self-hosted runs on a $5–10/mo VPS with no per-user or per-account fees [homepage].
• Key strength: The original Maybe Finance team built something polished enough to charge real money for. That UX depth carries over — this isn’t a hobbyist weekend project; it’s a near-production-quality personal finance app with 7,440 GitHub stars [merged profile].
• Key weakness: AGPL-3.0 means you cannot embed it in a commercial product without open-sourcing your wrapper. It’s also a community fork with no paid support or SLA — you’re betting on volunteer momentum [README].

---

What is Sure

Sure is a self-hosted personal finance platform built in Ruby on Rails, backed by PostgreSQL and Redis. It lets you connect bank accounts, track investments (stocks and crypto), manage transactions, set budgets, and ask questions of an AI assistant — all from a single dashboard running on your own infrastructure [homepage][README].

The name is a deliberate pun. Maybe Finance — the company that originally built this — shut down its hosted B2C product in 2023 after spending roughly $1 million on development (employees, contractors, data providers, infrastructure) without finding a sustainable business model [README]. Before going dark, they open-sourced the codebase under AGPL-3.0 with the stated goal of letting users self-host it for free. The community fork picked it up, renamed it “Sure” (as in: turn your maybe into a sure thing), and has been maintaining and extending it since [README].

What you’re actually getting is a near-production-quality application that a well-funded startup built for real paying users — not a tool someone bolted together on weekends. The 7,440 stars and active Discord suggest the fork has genuine momentum [merged profile][README].

One important caveat the README states plainly: “This repository is a community fork of the now-abandoned Maybe Finance project. NOT affiliated with or endorsed by Maybe Finance Inc.” The “Maybe” trademark belongs to Maybe Finance Inc. and is off-limits for forks [README]. You’re running community-maintained software, not a vendor-backed product.

---

Why people choose it

The pitch practically writes itself for anyone who’s looked at their YNAB or Monarch bill and thought “I’m paying a subscription to track my own money.”

Versus YNAB. YNAB ($99/year) is the category gold standard for zero-based budgeting, but it’s closed-source SaaS with an opinionated methodology that not everyone wants. You can’t export your history and take it somewhere else easily. Sure covers the same core loop — accounts, transactions, categories, budgets — without the vendor lock-in or the annual bill.

Versus Monarch Money. Monarch (~$99/year) is the more modern, less opinionated alternative to YNAB with cleaner UI and investment tracking. Sure targets roughly the same audience with the same feature set (account aggregation, net worth, budgets, transactions) while adding self-hosting control over financial data [homepage].

Versus Firefly III. Firefly III is the other well-known self-hosted personal finance option. It’s PHP-based, mature, and powerful — but the UX shows its age. Sure’s interface inherited the polish of a VC-funded product with a design team. That matters when you’re logging transactions every day.

The data sovereignty angle. Your bank account data, transaction history, and net worth are arguably your most sensitive personal data. Connecting those to a third-party SaaS means every acquisition, breach, or pricing change affects your financial history. Self-hosting puts that data on a server you control [homepage].

---

Features

Based on the README and website:

Account aggregation:

• 10,000+ financial institutions available for account linking [homepage]
• Bank accounts, investment accounts (stocks, crypto), and “everything else” in any currency [homepage]
• Manual account entry for anything outside the automatic link system [homepage]
• CSV import for accounts and transactions [homepage]

Transactions:

• Create income, expense, and transfer transactions manually [homepage]
• Custom categories, merchants, and tags [homepage]
• Transaction filters (date, account, category, merchant) [homepage]
• Rules engine to auto-categorize transactions [homepage]
• CSV import and linking between transactions [homepage]

Budgeting:

• Category budget setup with custom allocations [homepage]
• Balance monitoring per category [homepage]
• Spending trend comparison over time [homepage]

Net worth and portfolio:

• Charts for all assets and debts [homepage]
• Multi-currency support [homepage]
• Investment performance tracking [homepage]

AI assistant:

• Built-in AI query interface — ask questions about your finances in plain English [homepage]
• Accessible as a distinct feature section (“Sure AI”) [homepage]

Infrastructure:

• Docker deployment (primary path) [README]
• One-click deploy via PikaPods and Railway [README]
• PostgreSQL + Redis required [README]
• Demo data rake task for testing before going live [README]

What’s notably absent from the documented feature list: multi-user household management with separate views (not mentioned in available sources), bill tracking/upcoming payments calendar (not mentioned), and mobile apps (the README and website don’t reference native mobile apps — this appears to be a web app). Data not available on whether these are planned.

---

Pricing: SaaS vs self-hosted math

Sure: Free, AGPL-3.0 license. No cloud tier, no usage fees, no per-account charges. Hosting cost only [homepage][README].

YNAB (competitor):

• Free trial, then ~$99/year or ~$14.99/month
• No self-hosted option

Monarch Money (competitor):

• ~$99/year or ~$14.99/month
• No self-hosted option

Copilot (Mac/iOS only):

• ~$13/month
• No self-hosted option

Self-hosted Sure math for a typical user:

Say you’re currently paying $99/year for YNAB. Switch to Sure on a $6/month Hetzner VPS and you spend $72/year. That’s $27 saved per year before factoring in setup time — not a massive win on its own.

The real math changes if you’re paying for multiple financial tools. If you’re using a portfolio tracker + YNAB + net worth spreadsheet that you’re manually updating, consolidating into one self-hosted Sure instance at $6/month beats three separate subscriptions [homepage].

The more honest calculation: for most individual users, the savings over a single $99/year SaaS tool are modest. The real reason to self-host Sure isn’t primarily the money — it’s data ownership and no vendor dependency for your most sensitive financial data.

---

Deployment reality check

The README’s primary deployment path is Docker, with guides for Mac, Linux, Windows dev setups and a Docker hosting guide in the docs [README].

What you actually need:

• A Linux VPS with at least 2GB RAM (Ruby on Rails + PostgreSQL + Redis is heavier than a Node app)
• Docker and docker-compose
• A domain and reverse proxy (Caddy or nginx) for HTTPS
• PostgreSQL (bundled in docker-compose or external)
• Redis (bundled or external)
• For bank account linking: the project inherits Maybe Finance’s Plaid/Finicity integration, though the specific connection provider for Sure’s fork should be verified against current documentation before assuming full functionality

One-click options:

• PikaPods: managed hosting button in the README — handles the VPS, Docker, and SSL for you, at a per-pod monthly cost [README]
• Railway: one-click deploy button — managed PaaS, no server management needed [README]

Both options eliminate the Docker setup overhead for non-technical users at the cost of giving up some infrastructure control (and paying PikaPods/Railway’s hosting margin instead of a raw VPS).

What can go sideways:

The project is a community fork with no paid support tier. If something breaks between releases, you’re reading GitHub issues and asking on Discord — there’s no support ticket to file [README].

Bank account linking relies on financial data aggregation services that the original Maybe Finance set up. Whether and how well those integrations carry over in the community fork isn’t fully documented in available sources. If live account syncing is critical to your use case, test it against your specific institutions before committing.

The AGPL-3.0 license is a meaningful constraint: if you want to embed Sure’s code in a commercial product or offer it as a hosted service, you must open-source your entire application stack. For personal use this is irrelevant, but for founders building financial tools on top of it, read the license carefully.

Realistic time estimate: 1–2 hours for a technical user on a fresh VPS using the Docker guide. For a non-technical founder using PikaPods or Railway: 20–30 minutes. Manual Docker + domain + SSL from scratch with no prior experience: budget a full afternoon.

---

Pros and cons

Pros

• Professional-quality UX inherited from a funded startup. Maybe Finance spent real money on design and engineering before open-sourcing. That shows in the interface [README].
• Comprehensive feature set in one app. Account tracking, investments, budgeting, transactions, AI assistant — most personal finance SaaS tools charge separately for this stack [homepage].
• 10,000+ institution connections. Comparable to commercial tools for bank linking coverage [homepage].
• One-click deployment options. PikaPods and Railway make this accessible to non-technical users without raw server management [README].
• 7,440 GitHub stars and active community. Not a dead repo — Discord, open issues, and multi-language README translations signal real engagement [merged profile][README].
• No per-user, per-account, or usage fees. Self-host once, use indefinitely without cost scaling [homepage].
• Your financial data on your infrastructure. Bank account history, net worth, and spending patterns don’t live on someone else’s SaaS [homepage].

Cons

• AGPL-3.0, not MIT. You cannot build a commercial product on top of this without open-sourcing your entire application. Stricter than the MIT licenses common in self-hosted tools [README].
• Community fork with no vendor support. No paid tier, no SLA, no dedicated support team. Maintenance depends on volunteer contributors [README].
• Ruby on Rails stack is heavier than alternatives. More RAM and CPU than tools like Actual Budget (Node/SQLite). Plan for at least 2GB RAM minimum.
• Bank linking status unclear for the fork. The original Maybe Finance had working Plaid/Finicity integrations. Whether the community fork has kept these live and compliant is not fully documented in available sources.
• No mobile apps documented. This appears to be a web application — no native iOS or Android app mentioned in README or homepage [README][homepage].
• “Community fork” framing carries long-term risk. Maybe Finance failed as a business once. If contributor momentum drops, the project could stall again. The original Maybe Finance repo is archived [README].
• AI assistant details thin. The homepage advertises AI prominently but provides minimal detail on what model powers it, what data it has access to, or whether it makes external API calls [homepage].

---

Who should use this / who shouldn’t

Use Sure if:

• You’re paying $99–$180/year for YNAB, Monarch, or similar and want to own your financial data instead of renting access to it.
• You’re comfortable with Docker or willing to use PikaPods/Railway for managed deployment.
• You want a polished personal finance UI, not a spreadsheet with a database behind it.
• You’re a solo user or couple — the core feature set maps well to individual financial management.

Skip it (use Actual Budget instead) if:

• You want zero-based budgeting with a proven YNAB-style methodology and a larger self-hosted user community focused specifically on budgeting.
• You want MIT licensing with fewer open-source restrictions.
• You need offline-first functionality without a server.

Skip it (use Firefly III instead) if:

• You need deep double-entry accounting, multi-currency with full transaction control, and don’t care about modern UX.
• You want a PHP-based stack that’s lighter to host.
• You want a project with a longer self-hosted track record and more community documentation.

Skip it (stay on YNAB or Monarch) if:

• You have no interest in server management even via one-click tools.
• You’re relying heavily on mobile apps — YNAB and Monarch have mature iOS/Android apps; Sure’s status here is unclear.
• You need guaranteed live bank sync — commercial tools have SLAs with data providers; this fork does not.

Skip it for commercial use if:

• You’re building a product or service — AGPL-3.0 means you’d need to open-source your entire application if you use Sure’s code.

---

Alternatives worth considering

• Actual Budget — the closest self-hosted competitor. MIT-licensed, Node/SQLite-based (lighter), strong zero-based budgeting focus, active community, local-first architecture option. More specifically focused on budgeting than Sure’s broader wealth-management scope.
• Firefly III — PHP-based, mature, double-entry accounting support. Heavier methodology, older UI, but extremely well-documented and stable.
• YNAB — the category standard for zero-based budgeting. Closed source, $99/year, but unmatched methodology documentation and mobile apps.
• Monarch Money — modern alternative to YNAB with cleaner interface and investment tracking. Also closed source, similar pricing.
• GnuCash — desktop-based, free, double-entry accounting. Not self-hosted in the web sense, but a zero-cost option for users who want complete offline control.

For a non-technical founder choosing between self-hosted personal finance tools, the realistic shortlist is Sure vs Actual Budget. Choose Sure if you want the broader wealth management scope (investments, net worth, AI assistant) and the Maybe Finance UI heritage. Choose Actual Budget if budgeting is the primary use case, you want MIT licensing, and you want the lighter deployment footprint.

---

Bottom line

Sure is what happens when a well-funded startup builds something genuinely good and then fails as a business — the code survives, and a community picks up the pieces. The 7,440 stars and active Discord suggest this fork has real momentum, not just a GitHub archive with an optimistic README. For someone paying $99/year for YNAB or Monarch, Sure is worth a serious look: you get comparable features, full data ownership, and no recurring bill. The deployment is accessible enough through PikaPods or Railway that “I’m not technical” is only a partial excuse anymore.

The risks are real too. Community forks can stall. The AGPL-3.0 license limits commercial use. The bank linking story for the fork isn’t fully documented. And if live mobile apps are part of your daily workflow, the available sources don’t confirm Sure has them. Go in with eyes open — this isn’t a vendor product with an SLA. But for personal financial data you’d rather keep off third-party servers, the tradeoff is defensible.

---

Sources

1. Sure — GitHub Repository and README (we-promise/sure, 7,440 stars, AGPL-3.0). https://github.com/we-promise/sure
2. Sure — Official Website (sure.am). https://sure.am