Remitly Hub was created and is actively maintained by software engineer k007sam. It was built to solve a pervasive problem faced by international professionals, expatriates, and immigrant families: gaining clear, multi-year financial transparency over cross-border remittance transfers without surrendering personal financial records to third-party cloud servers.
The Problem with Modern Financial Dashboards
Most commercial financial aggregators require users to connect their bank credentials or upload statements to cloud databases where sensitive data is processed, indexed, and frequently monetized for ad targeting or credit scoring. For remittance senders, transaction logs contain highly sensitive personal information, including recipient legal names, physical addresses, bank account identifiers, and recurring family support payments.
Our Core Engineering Principles
Air-Gapped In-Browser Execution: Remitly Hub functions entirely inside the user's web browser memory. Whether parsing five hundred or fifty thousand transactions, all data manipulation uses client-side Web APIs (FileReader, Web Streams, and optimized in-memory indexing). Zero financial data packets are transmitted across the internet.
Multi-Year Consolidated Clarity: Remitly users frequently accumulate CSV files across five to ten separate years (2018–2026). Our parsing pipeline normalizes varying header schemas, resolves timezone offsets, and creates seamless unified timelines.
Intelligent Beneficiary Grouping: Senders often enter recipient names with minor variations (e.g., maiden names, abbreviations, middle initials). Remitly Hub leverages fuzzy identity resolution to group related records into consolidated beneficiary statements.
Open-Source Transparency: Trust cannot be demanded; it must be proven. Our complete codebase is open-source and auditable on GitHub, allowing developers, security researchers, and AI agents to verify every computation.
Developer & Leadership
Remitly Hub is developed and architected by k007sam under the SDP Flash InfoTech organization. For technical discussions, contributions, or architecture reviews, visit our GitHub repository or reach out directly via our contact page.