2025 – Present · Lead Architect & Open Source Maintainer · Full-stack · Actively building
Arda — Multi-Tenant Financial Operations Platform
Cloud-native platform with 15 Go microservices (gRPC & NATS), React Module Federation (13 remotes), and Ory IAM
What this system is for
ARDA is a self-owned multi-tenant business platform built from first principles: domain services, identity, workflow, frontend composition, and self-hosted infrastructure are designed as one system.
What I owned
Lead architecture, backend and frontend implementation, shared libraries, identity boundaries, event contracts, and GitOps infrastructure across the ARDA Labs repositories.
Overview & Context
ARDA is a self-owned multi-tenant business platform built from first principles: domain services, identity, workflow, frontend composition, and self-hosted infrastructure are designed as one system.
Problem & Constraints
Financial operations demand strict multi-tenant data isolation, high-throughput microservices communication, unified zero-trust identity, and decoupled frontend release cycles across CRM, Finance, HRM, and Workflow domains.
System Architecture
Browser / Client ──► Cloudflare Tunnel ──► Traefik (ForwardAuth)
│
┌──────────────────────────────────────┴──────────────────────────────────────┐
▼ ▼
BFF Auth-Gateway ──► Ory Kratos + Hydra (Identity) React Shell + 7 MFE Remotes
│ [@workspace/ui, api, auth]
▼
15 Go Microservices (HTTP/JSON + gRPC + NATS Events)
[iam, platform, finance, workflow, crm, hrm, notification, media, mdm]
│
▼
CloudNativePG (HA Postgres) · Valkey · Garage S3 · Zeebe 8.5 BPMN- React Module Federation with shared @workspace packages
- 15 Go Microservices with gRPC inter-service calls & NATS domain events
- Ory Kratos & Hydra zero-trust authentication via Traefik ForwardAuth
- CloudNativePG HA PostgreSQL cluster with Valkey distributed caching
Engineering Deliverables
- Engineered 15 Go microservices sharing common libraries (arda-auth, arda-grpc, arda-events, arda-postgres) with standardized gRPC contracts.
- Architected React Module Federation with a central shell and 13 remotes (iam, platform, finance, account, hrm, workflow, crm, mdm, loan, deposit, capital, statistical, ai) using shared workspace packages.
- Built zero-trust identity flow with Ory Kratos, Ory Hydra, Traefik ForwardAuth, and BFF session cookies.
- Orchestrated HA PostgreSQL with CloudNativePG, Valkey distributed cache, and Zeebe 8.5 BPMN workflow on a 3-node K3s cluster.
Engineering Signals & Outcomes
- 15 Go Microservices with gRPC & NATS event streams
- React Module Federation (Shell + 13 Remotes)
- Zero-trust Ory Kratos/Hydra IAM & CloudNativePG HA
Engineering Outcomes
- A coherent platform model spanning domain services, identity, workflow, frontend composition, and infrastructure.
- Explicit contracts for synchronous calls, asynchronous events, and tenant-aware identity.
- Public repositories that make the architectural reasoning inspectable.
Engineering threads behind the project
Each thread links to notes focused on one concrete decision or engineering problem.
Domain boundaries that remain understandable
Why Finance, IAM, Workflow, CRM, HRM, and platform capabilities are separated, and where synchronous gRPC should stop.
Identity as a boundary, not a frontend feature
The BFF, ForwardAuth, Ory, session, tenant, and route-policy decisions behind a safer browser boundary.
Events that do not disappear between database and broker
Transactional Outbox, NATS JetStream, idempotency, and the operational consequences of choosing eventual consistency.
Workflow without leaking the engine into every domain
A dedicated workflow boundary keeps BPMN lifecycle concerns consistent while domain services keep their own language.
Frontend composition across seven remotes
The rules for shared packages, remote ownership, failure isolation, and release independence in the React platform.
Technologies & Tooling
Go · gRPC · NATS · React · Module Federation · Ory Kratos · CloudNativePG · K3s · Zeebe
Related Engineering Notes
- How Arda Is Put Together: 15 Go Services, One Workspace12 min read
- Authentication Beyond JWT: How Arda Authenticates Requests, and Where Trust Ends13 min read
- Transactional Outbox on NATS JetStream: What Arda's Six Relays Actually Guarantee10 min read
- Putting BPMN Behind a Workflow Service Boundary11 min read
- A Shell and Thirteen Remotes: Reading Arda's Module Federation Setup11 min read
- Running a Production-Like Platform on a Three-Node K3s Cluster11 min read