Institutional Engineering Specifications
Technical Specs for Sysclu HotelOps
Engineered for mission-critical reliability with strict layer isolation, local-first SQLite/MySQL persistence, and zero floating-point ledger rounding.
Frontend Client Architecture
- Flutter Multiplatform (Web, Windows Desktop, Android)
- GoRouter State Machine
- Riverpod 2.x Reactive Providers
Backend Services & Concurrency
- High-Concurrency REST API
- WebSocket Event Dispatcher
- JWT Stateless Tokens
Database & Transaction ACIDity
- Relational MySQL / SQLite Local Cache
- ACID Compliant Transactions
- Encrypted Guest Records
Domain Architecture & Patterns
- Feature-First Domain Architecture (Clean Layered)
- Repository & Provider Patterns
Security, RBAC & Audit Trails
- Role-Based Access Control (Front Desk, Maid, Tech, Manager)
- Audit Trail Logging for all operations
Engineering FAQ
Frequently Asked Architectural Questions
Can Sysclu HotelOps work on both mobile tablets and desktop computers?
Yes. Sysclu HotelOps is engineered with Flutter, running natively on Windows desktop for front desk reception setups and on Android/iOS tablets and smartphones for mobile housekeeping and engineering teams.
Does it support offline operations if the internet goes down?
Yes, the local caching engine stores transactions and status updates locally and synchronizes automatically upon reconnecting to the cloud server.
How does the split billing and accounting system work?
The folio manager allows single guests, corporate accounts, or room shares to split room charges, restaurant tabs, and laundry costs across separate payment methods (cash, card, UPI, bank transfer).
Download the production binaries now
Verify SHA-256 hashes and test on your devices.