Server & Supabase Migration Tuning

I am moving everything that currently runs under lovable.dev to a fresh production environment and I need an experienced engineer to take the lead on the entire move. The scope covers four main layers: the P2P signalling server, the SFU media server, the Supabase database, and the general app server.

Your first task will be to replicate each service in the new cloud account, configure secure networking, then run a controlled cut-over from the legacy hosts. Once traffic is flowing, we will work together to fine-tune the P2P server, the SFU server, and the Supabase database so they perform reliably under real-world load.

Typical work will include:
• Clean installs of the P2P and SFU stacks (we can decide together whether to keep the existing stack or upgrade to a newer build).
• Full Supabase export/import, auth re-keying, and connection-pool tuning.
• Error hunting—eliminating the crashes and intermittent timeouts that have been plaguing the current setup.
• Performance profiling, autoscaling rules, logging, and alerting so we can spot issues before users do.

I will provide SSH keys, access tokens, and detailed diagrams the moment we start. The job is finished when the new cluster is stable for at least 48 hours, metrics show equal or better latency than the old servers, and no outstanding errors remain in the logs. If that milestone is hit smoothly, I’m open to an ongoing retainer for proactive maintenance.