During development of Rivorea, deploying the real-time backend on Vercel was not feasible due to platform limitations with persistent real-time connections. The backend was moved to an external hosting provider, but occasional request blocking issues occurred, requiring VPN access to maintain connectivity. As a temporary trade-off, real-time features were simplified, and notifications currently rely on page refresh to stay functional

To ensure stability and continuous progress, the real-time system was temporarily simplified to a refresh-based notification flow, allowing the application to remain fully usable without downtime. The architecture was adjusted to separate backend and frontend deployments, keeping the system modular. A future upgrade is planned to migrate the backend to a more suitable cloud environment to fully restore real-time functionality without connectivity limitations.