Building a Treasury SaaS with React, Node.js, Firebase & MySQL
Applying 25+ Years of Software Experience to a Modern Financial
Platform
Hello DEV community,
My name is Hernán Ricardo Ávila Castillo, a senior fullstack developer with more than 25 years of experience, currently based in Guatemala. I am also completing my degree in Computer Science and Systems Engineering.
At the moment, my main focus is the development of a Treasury Management SaaS platform: a modern system designed to support real-world financial operations, payment workflows, balances, and business controls.
In this post, I would like to share what I am building, why I selected this technology stack, and how I approach architecture when working on a fintech-oriented product.
The Project: A Treasury / ERP Ecosystem
The platform is being designed to support:
- Treasury operations
- Cash flow monitoring
- Accounts payable and receivable
- Payment approval workflows
- Financial tracking across projects and organizations
- A scalable SaaS foundation for future ERP modules
This is not a demo project. The goal is to evolve it into a production-grade enterprise platform.
Technology Stack
After working with many technologies throughout my career, I decided to build this treasury system using a modern and reliable stack:
Frontend: React
React provides an excellent foundation for:
- Admin dashboards
- Component-driven interfaces
- Long-term scalability in UI development
Backend: Node.js
Node.js enables:
- Fast API development
- Strong integration capabilities
- Clean service-oriented architecture
Authentication and Platform Services: Firebase
Firebase is used for:
- Secure authentication
- Notifications
- Realtime capabilities when needed
- Simplified scalability for SaaS workflows
Core Financial Database: MySQL
MySQL remains a strong choice for treasury data because it provides:
- Relational consistency
- Transactional reliability
- Strong reporting and structured modeling
High-Level Architecture
The platform follows a modular SaaS architecture:
React Admin Dashboard
|
v
Node.js REST API Layer
|
+-------------------+
| |
Firebase Auth MySQL Database
| |
Notifications Treasury Ledger + ERP Data
This separation allows:
- Clear API boundaries
- Enterprise-grade data integrity
- Independent scaling of modules
Key Design Principles
After more than two decades building software, several principles remain constant:
1. Financial systems require strong consistency
Treasury platforms must be auditable, traceable, and transaction-safe.
Data integrity is not optional.
2. SaaS requires modular thinking
Every module must evolve independently:
- Payments
- Clients
- Projects
- Approvals
- Reporting
3. Automation is part of the future
The platform is being developed with automation in mind, integrating AI-driven workflows using tools such as n8n and Make.
Treasury is not only accounting. It is operations.
What I Am Building Next
Upcoming milestones include:
- Multi-tenant SaaS structure
- Role-based access control
- Payment gateway integrations
- Approval pipelines
- Financial reporting dashboards
- Cloud-native deployment workflows
Why I’m Sharing This Here
I am joining DEV.to to:
- Share real-world software engineering experience
- Learn from the community
- Document the evolution of this treasury platform
- Connect with others building fintech and enterprise systems
Final Thoughts
Even after decades in software, building systems like this remains exciting. Technology evolves constantly, and so do we as engineers.
If you are working on treasury platforms, ERP systems, fintech SaaS products, or React/Node architectures, I would be glad to connect and exchange ideas.
Thank you for reading.
Links
- GitHub: https://github.com/hricardoavilac
- Website: https://racastillo.com
#dev #react #node #firebase #mysql #saas #fintech #softwarearchitecture
Top comments (0)