RouhSaz is the production platform I build and operate for Rouhi Group. It connects organizational food ordering with the operational, financial, and technical workflows required to run the business reliably.

What I own

This is not a small feature or a narrow implementation task. I own the technical direction and delivery of the platform end-to-end: architecture, implementation, deployment, production operations, reliability, and the decisions that keep the product maintainable as the business grows. The platform is currently available in production at rouhsaz.rouhi.ir.

Product surface

The platform brings together:

• organizational ordering and approval workflows,
• food catalog and operational delivery flows,
• wallets, finance, invoices, deposits, settlement, and payment integration,
• role-based access control and organization boundaries,
• notifications, SMS workflows, audit trails, and operational visibility,
• production safeguards around sessions, CSRF, validation, throttling, health checks, and deployment.

Engineering approach

RouhSaz is built around a modern TypeScript platform stack: Next.js on the frontend, NestJS services, PostgreSQL and Prisma for data access, and Docker/Nginx for deployment and production operations. The important part is not only the list of technologies; it is the connection between product rules, permissions, money movement, notifications, and real operational outcomes. I treat every business write as something that needs a clear owner, a traceable result, and a predictable recovery path. That means the platform is designed with explicit workflows, auditability, focused tests, and operational controls instead of relying on happy-path UI behavior.

Why it matters

Organizational ordering looks simple from the outside. In practice, it involves people, budgets, approvals, kitchens, delivery, timing, exceptions, and financial reconciliation. RouhSaz is the system that makes those moving parts understandable and operable in one place.