Plivo SMS Application Migration

I have an existing Plivo SMS messaging application that is already built and working. The application sends bulk SMS messages using the Plivo Messaging API. Originally, it was hosted on a shared Namecheap hosting account. Because I often send campaigns to 1,700+ recipients at one time, the shared hosting environment could not handle the workload, resulting in server resource errors and failed message processing. To work around this, the previous developer moved the SMS processing to his own server. I have now upgraded to a Namecheap VPS, and I want the entire application moved back to my own server. This is not a new development project. The application already exists. I need someone to migrate the Plivo SMS processing, configure the VPS correctly, and ensure the system can reliably send large SMS campaigns. Responsibilities Review the existing Plivo SMS application Migrate the SMS processing from the developer's server to my Namecheap VPS Configure the VPS for reliable bulk SMS processing Configure background workers or a queue system (if needed) Optimize the application for sending 1,700+ SMS messages Verify Plivo API credentials and messaging configuration Verify delivery status callbacks (if applicable) Test the complete messaging workflow Document the server configuration and deployment process Current Environment Existing Plivo SMS application Namecheap VPS Linux server Existing production code Custom website Plivo Messaging API Required Skills Plivo Messaging API (required) Linux VPS administration Namecheap VPS Background workers and job queues PHP, Python, or Node.js (depending on the existing application) Apache or Nginx Cron jobs REST APIs Server performance optimization Deliverables The project is complete when: The SMS application runs entirely from my Namecheap VPS. The previous developer's server is no longer required. Bulk SMS campaigns of 1,700+ recipients process successfully. Messages are sent reliably through the Plivo API. No timeout or server resource errors occur. The deployment and server configuration are documented.