Proxy-Enabled Web Scheduling System

I need a robust, web-based appointment scheduler built from the ground up. Core flow is simple for the end user, yet under the hood the platform has to work hard every single second to secure slots through an external booking API.

What the application must do:
• Web interface only, with a secure login. At launch I only need the Admin role; future roles can be added later, so the structure should remain extendable.
• Full booking calendar visible to me in real time.
• Automatic confirmation notifications and follow-up reminders triggered on successful booking events.
• Continuous slot hunting: every second the system should poll the external API, rotating through a configurable proxy list, until an available time meets the rules I set. When it finds a match it must lock it immediately and record every request/response for audit.
• Proxy management dashboard where I can upload or remove proxies and see health metrics (success rate, response time, bans).
• Unique ID tracking for each booking attempt so I can trace issues quickly.
• Clean, documented REST hooks so that in the future I can plug the scheduler into other in-house tools without rewriting core logic.

Additional Requirements:
1. The portal is for scheduling appointments and must handle Cloudflare error 1015 by automatically switching proxies before the error occurs.
2. A centralized portal should manage all IDs, showing their status (active/inactive).
3. Once an appointment is scheduled, the bot should notify me immediately.
4. A task system should allow monitoring specific locations based on client requirements to avoid unnecessary errors.
5. The system must run 24/7 via a cloud setup, continuously checking appointments and sending alerts.
6. Human verification handling: Every 15 minutes, if a human verification page appears, the bot must open a new tab to complete it using 2Captcha. Login details should be auto-saved with auto-login enabled.

Technical notes:
I am open on the tech stack so long as it is proven for high-frequency API calls and easy to maintain. If you lean toward Node.js, Python (FastAPI / Django), or Go with a modern front-end framework, outline why your choice is best for sustained 1-second polling and rapid proxy rotation.

Deliverables:
1. Production-ready source code in a private repo
2. Deployed instance (Docker or similar) with all environment variables templated
3. Brief setup document and API reference
4. One-week post-launch support to iron out edge cases

If you have built anything similar—ticket bots, reservation grabbers, or high-traffic schedulers—please mention it; practical experience with rotating proxies and rate-limited APIs will help you hit the ground running.