Securo is a fast-moving, privacy-first self-hosted finance manager. Its native SimpleFIN integration makes it a natural destination for BankSync users who want account aggregation without building a custom importer.
The key architecture is simple: BankSync maintains supported bank connections and exposes the SimpleFIN-compatible feed; Securo claims the connection and stores the access URL in its own environment.
What Securo imports
Current Securo documentation lists accounts, balances and transactions across its bank-sync providers, and its SimpleFIN implementation also handles holdings where data is available. Securo adds budgets, goals, asset tracking, multi-currency reporting, recurring transactions and optional AI agents around that imported base.
The repository documents two relevant environment settings: SIMPLEFIN_ENABLED=true and SIMPLEFIN_API_URL. Its example uses the beta Bridge host for sandbox testing and the production Bridge host for real banks. With BankSync, follow BankSync’s current provider/destination instructions rather than hard-coding a host from an unrelated provider.
Securo setup
Deploy or update Securo
Use the current Docker or Podman instructions and back up your database first.
Enable SimpleFIN
Set `SIMPLEFIN_ENABLED=true` and configure the API/provider setting required by your deployment.
Restart the stack
Confirm the SimpleFIN option appears in the bank connection UI.
Connect the bank in BankSync
Complete supported institution authorization and verify the selected accounts.
Create a one-time SimpleFIN token
Use the current BankSync SimpleFIN destination flow.
Connect inside Securo
Go to Accounts → Connect Bank → SimpleFIN and paste the token once.
Verify and schedule
Compare account identity, balances, recent transactions and holdings before enabling routine sync.
Sandbox first, then production
Securo points builders to free demo tokens on the SimpleFIN developer page. Use synthetic data to verify deployment, reverse proxy, background jobs and account mapping before involving a real institution.
Privacy boundaries
Self-hosting keeps Securo’s database under your control, but the access URL still authorizes reads from the provider. Encrypt the host disk and backups, secure .env, restrict registration, enable TOTP or OIDC where appropriate, and terminate HTTPS before exposing the service remotely.
Securo supports other bank providers as well. That is useful for a mixed household, but keep provider identity attached to each account so two connectors do not import the same bank account twice.
Securo verification
| Stage | What to do | Check |
|---|---|---|
| Deployment | Current image and migrations completed | No background worker errors |
| Provider | SimpleFIN option enabled | Correct environment and restart |
| Connection | Token claimed once | Access URL stored without logs |
| Accounts | Remote accounts discovered | Type, currency and identity match |
| Transactions | Recent posted records imported | No duplicates after second sync |
| Holdings | Only where source supplies them | Quantities and currency are sensible |
Confirm the integration layer by layer.
Troubleshooting
If the SimpleFIN option does not appear, re-check environment variables inside the running container rather than only the host shell. If the setup token fails, generate a new one; it may already have been claimed. If a connection returns no accounts, test the provider with a bounded /accounts request and inspect structured errors.
For contributors, Securo’s implementation is a useful reference because the provider registration is explicit and the project is AGPL-3.0. Preserve that license obligation when distributing a modified network service.