Project / Fork / Open-source adaptation

Securo

Privacy-first personal finance management fork with self-hosting and data integrity.

Snapshot

Current record

Role
Fork, self-hosted infrastructure, integrations and backup engineering
Stage
Independent fork under controlled testing and infrastructure review
Stack
Docker, Python, TypeScript, React, PostgreSQL, Pluggy
Status
Active

Record

A dated view of the project.

  1. Started
  2. Published
  3. Updated

Current state

Securo is an independent adaptation and self-hosted implementation based on the open-source Securo project (opens in a new tab). This record documents infrastructure isolation, Docker containerization, Brazilian Open Finance (Pluggy) integration, and automated backup routines.

The primary proposition of upstream Securo is privacy: managing personal accounts, spending, and financial habits without dispatching sensitive financial records to third-party corporate servers.

Upstream foundation vs our engineering work

The upstream Securo project, licensed under AGPL-3.0, delivers the core financial management system: an asynchronous FastAPI/Python backend, a React/TypeScript interface, PostgreSQL data architecture, and WebAuthn authentication. The fork preserves full credit to original authors and maintainers.

Our engineering layer concentrates on deployment reliability and local adaptation:

  • Containerized infrastructure: Docker Compose and Podman orchestration for local or VPS deployment with zero external data leakage.
  • Open Finance integration: support for Brazilian banking connectors through secure Pluggy pipeline.
  • Backup and recovery routines: automated PostgreSQL snapshot generation and verified persistence to safeguard transaction history.
  • Environment hardening: isolated secret management and dedicated configuration for reliable operation.

Why maintain as a fork

Personal financial software demands strict data sovereignty. Running a verified fork enables local API integration, resilient backup schedules, and dependable operational security while staying aligned with upstream open-source releases.

Keep exploring

Follow the work behind the project.

See the other projects, read the engineering notes, or get in touch about a problem worth building around.