A neobank demo showing fintech architecture with Go microservices.

Nivo is a portfolio project implementing the core systems of a digital bank. It demonstrates microservices architecture, double-entry accounting, and fintech domain patterns in a working, deployable application.

Archived Showcase — The live demo at nivomoney.com has been retired. The domain now serves a static landing page. Run the platform locally for the full demo experience.

What it includes:

• 8 Go services and an API gateway, with domain-driven boundaries
• Double-entry ledger with balanced journal entries
• JWT authentication with role-based access control
• React frontends for users and admins
• Full observability stack (Prometheus, Grafana)

• Go 1.26+
• Docker & Docker Compose
• Node.js 18+

git clone https://github.com/1mb-dev/nivomoney.git
cd nivomoney
cp .env.example .env
cp docker-compose.override.yml.example docker-compose.override.yml  # publishes ports

# Start all services. On a fresh database they race on migrations:
# repeat this until `docker compose ps` shows them all healthy.
make dev

# Seed database with demo data (reads config from the environment)
set -a; . ./.env; set +a
make seed

# Start frontend (separate terminal)
cd frontend/user-app && npm install && npm run dev

Open http://localhost:5173 and login with demo credentials.

Admin access: Run make seed locally to generate admin credentials (see .secrets/credentials.txt).

All data is synthetic. No real money.

services/
├── identity/       # Auth, users, KYC
├── ledger/         # Double-entry accounting
├── wallet/         # Balance management
├── transaction/    # Transfers, payments
├── rbac/           # Roles & permissions
├── risk/           # Fraud detection
├── notification/   # Alerts, messaging
├── simulation/     # Test data generation
└── seed/           # Database seeding

gateway/            # API Gateway with SSE
frontend/
├── user-app/       # Customer React app
└── admin-app/      # Admin dashboard

• Double-entry ledger - Postgres refuses to post a journal entry that does not balance
• Idempotent transfers - The wallet service dedupes internal transfers on transaction ID
• RBAC - Granular permissions with role hierarchies
• Real-time updates - Server-sent events through the gateway

Transfers do not reach the ledger: the transaction service's ledger client sends no credentials, so the ledger refuses the call. The failure is logged and the transfer still completes.

Full documentation: nivomoney.com/docs

• Quick Start
• Architecture
• API Flows
• ADRs

This is a portfolio demonstration, not a production bank. It shows how a neobank would be built.

See CONTRIBUTING.md for development setup and guidelines.

MIT - see LICENSE