Why this matters
Most modern finance apps centralize your transaction history and customer data. Running your own instance means credentials, transactions and any analytics stay under your control while still offering bank sync, multi-currency accounting, budgeting and automation. Securo targets users who want a full-featured finance UI without handing data to third parties and who can operate a simple server stack.
What Sets It Apart
- Privacy-first, self-hosted architecture — everything (credentials, transaction history, rules) lives on your PostgreSQL/Redis instance, so you avoid vendor lock-in and third-party telemetry. This means greater data control and simpler compliance for privacy-conscious setups.
- Bank sync with multiple providers — built-in connectors for Pluggy (Brazil), Enable Banking (PSD2 Europe) and SimpleFIN (US/international) let you pull transactions into the same workspace. So you can consolidate cross-border accounts without manual CSV juggling.
- Rules-driven automation and reporting — transaction auto-categorization, recurring transactions, budgets and net-worth reports reduce manual bookkeeping overhead. That enables faster month-to-month analysis and reusable automation across accounts.
- Optional self-hosted AI Agents and RAG — you can enable an MCP server and connect LLM providers (OpenAI, Anthropic, Ollama, etc.) for conversational queries and tool use over your instance. Because the agents are optional and self-hosted, you control which models and retrieval backends see your data.
Who it's for and tradeoffs
Great fit if you:
- Need a privacy-first way to consolidate multiple bank accounts, investments and budgets on your own infrastructure; and
- Can run Docker/Postgres/Redis or have access to a small VPS; and
- Want lightweight automation (rules, recurring transactions) plus the option to add conversational search/agents without sending data to a SaaS AI product.
Look elsewhere if you:
- Require a zero-ops mobile-first consumer app with hosted customer support (Securo expects you to self-host or operate via a provider);
- Need guaranteed bank connector availability without configuring external provider credentials and TLS (Enable Banking production requires proper HTTPS and keys); or
- Plan to offer a public SaaS using modified code without complying with the AGPL-3.0 license — the license requires source release for network-deployed modifications.
Operational notes
Runs on a standard web stack (FastAPI backend, React frontend, PostgreSQL, Redis + Celery). Enabling AI Agents adds an optional MCP server process; agents chat without tools if MCP isn't present. Because the project bundles bank connectors, some features require external credentials or provider signup and occasional maintenance (rate limits, OAuth PEM keys, or sandbox vs production differences).
