Featured projects#Backup

Sure: the community fork that keeps Maybe Finance alive after the archive

The community fork of archived Maybe Finance: self-hosted finance via Docker Compose, AGPL-3.0, SECRET_KEY_BASE required before your first account.

Project facts

GitHub Ecosystem
Repositorygithub.com/we-promise/sure
License
AGPL-3.0
Language
Ruby
Stars
14,993
Data checked
2026-11-14

Snapshot figures reflect the check date and may change over time.

The Maybe Finance story stopped in July 2025: a team that spent nearly a million dollars building a personal finance app open-sourced it, its hosted business failed to sustain, and the repository was archived. The community picked up the code as Sure — the README describes it as a community-maintained fork that cannot use the Maybe trademark but keeps the features moving. GitHub’s API reported 14,993 stars on November 14, 2026, with pushes that same day.

Core features

  • The full personal-finance set: cash, credit-card, investment and loan accounts; transaction tracking; portfolio and net-worth monitoring; budgets; category reports. The README’s screenshot shows a built-in AI assistant sidebar answering questions about the accounts.
  • More than a web app: besides the browser, the README lists a macOS desktop app, a mobile app, API clients, and LLM agents; a Sure Clients doc gathers the entry points.
  • The compliance line a fork must walk: forks must keep the original AGPLv3 license and state in their README that they are based on Maybe Finance; “Maybe” is a trademark of Maybe Finance Inc. and may not be used in forked repositories or logos. Sure itself is AGPL-3.0.
  • Self-hosting first: the official docs give a full Docker Compose path with images on ghcr.io; an optional backup service ships in compose.yml, and the docs cover backups, upgrades and rollbacks.

Typical use cases

  • Migrating from Maybe: the original repository is archived but your data is still yours; Sure carries the same codebase forward, and the README addresses the original Maybe community directly.
  • Keeping financial data on your own server: accounts, investments and net-worth trends stay self-hosted, with PDF import and AI Q&A — for people who would rather not hand their finances to a SaaS.
  • Long-term personal or household finance: budgets, category reports and net-worth trends need a project that keeps being maintained; Sure’s release activity (new versions through November 2026) is the metric that matters for a self-hosted dependency. Weigh its hard PostgreSQL and Redis requirements into the long-term cost too.

Quick start

The official Docker hosting doc runs: fetch the sample compose.yml (with the optional backup service), generate a SECRET_KEY_BASE into .env, and start the stack. Compose requires PostgreSQL and Redis — the docs do not support SQLite or MySQL — the image pins Ruby 3.4.9, and PDF import needs poppler-utils.

The doc repeats one warning: set SECRET_KEY_BASE before creating the first account, and never ship the placeholder default. It does more than sign session cookies — without explicit ACTIVE_RECORD_ENCRYPTION_* keys it seeds the encryption keys that protect provider API tokens at rest. Changing it later makes already-encrypted data unreadable, and upgrades must keep the original value. Generate a strong random value before you start; there is no easy undo.

For backups, compose.yml ships an optional backup service and the docs cover upgrades and rollbacks; when you plan backups for a whole self-hosted stack, compare Zerobyte, a Restic-based automation tool.

Summary

For Maybe Finance users, Sure is the most direct continuation available: same lineage, community-maintained, actively released. It is not free of obligations — you own the Docker, PostgreSQL, Redis and backup operations, and AGPL-3.0 carries redistribution duties. GitHub’s API reported Ruby, AGPL-3.0, 14,993 stars, an unarchived repository, and a push the same day, on November 14, 2026.

This entry is based on the README and the official hosting docs; we did not deploy it or import data. Follow the docs exactly on secrets and backups, and rehearse one recovery before going live. From a 54,188-star archive to a 14,993-star fork within a year, the lineage shows an open-source project can outlive its company.