Paying a distributed team without the fiat detour
How do you run cross-border payroll and treasury for a crypto-native team?
Paying a team across borders normally means a chain of correspondent banks, a two day wait, and a spread nobody itemizes. Doing it on-chain replaces that with a different set of problems, and most of them are not payment problems. Many organizations have to share one platform without ever touching each other's funds or data, which means multi-tenant isolation, per-tenant credentials, non-custodial signing keys derived in a KMS rather than stored as raw tokens, and payroll records encrypted at rest. Then the queue has to stop marking payments successful before on-chain confirmation, and something has to unwind a partial batch without losing funds. That is the system I was sole technical owner of at PayZoll, from contract level up to the treasury dashboard.
- 2025 · 2026
StellarPayZoll
Cross-border payroll and treasury, built for crypto-native teams.
Rust / Soroban · Go · TypeScript · NestJS · PostgreSQL (pgcrypto) · Redis · AWS (KMS, EKS) · GCP (GKE) · Kubernetes - 2026
NimiqPods
NIM-backed accountability for small groups. Commit, show up, earn, repeat.
Next.js 16 · Nimiq Mini-App SDK · @nimiq/core · Drizzle ORM · PostgreSQL · TypeScript