Azure Expert for SaaS Backend Setup

I want an AZURE expert set up a... 1.2 Backend SaaS Engine — What It Automates 1. Monthly automated deletion requests sent to data brokers on behalf of subscribed customers 2. Dark-web monitoring for credential/data leaks 3. Government/public ID-database leak checks 4. Leaked photo/video reverse-search 5. Social media exposure monitoring (is a profile public/findable — not content or opinion analysis) 6. News/media mention monitoring 7. Subscriber management (add/edit/remove people on a plan, billing, plan tier changes) Recommended Tech Stack Layer Recommendation Why Frontend Next.js (React) or similar SSR framework SEO-critical marketing site + authenticated app in one codebase Backend Node.js/TypeScript or Python (FastAPI/Django) Either works; pick based on your dev's strength Database PostgreSQL Relational data (subscribers, removal statuses, reports) Hosting AWS or Azure, Australian region Matches the original SaaS spec; satisfies data-residency disclosure Auth Managed auth provider (e.g., Auth0, Clerk, or Supabase Auth) with magic-link support Faster to ship securely than rolling your own Payments Stripe (AU) PCI-DSS compliant via hosted fields/tokenisation — you never touch raw card data Email Transactional (Postmark/SendGrid) + marketing (separate tool) with SPF/DKIM/DMARC configured Deliverability + Spam Act compliance Background jobs / scheduling Queue system (e.g., BullMQ, Celery, or cloud-native equivalent) Powers the monthly automated broker requests, re-scans 3D/WebGL (hero scene) Three.js via React Three Fiber + drei Lightweight, React-native, huge ecosystem of performance-tuned examples for exactly this kind of node/network visual Scroll & component animation Framer Motion Page transitions, whileInView reveals, form micro-interactions Scroll-triggered storytelling GSAP + ScrollTrigger The "How It Works" pipeline sequence specifically — best-in-class for scroll-scrubbed animation Lottie fallback lottie-web / dotlottie Lightweight fallback animation for the hero on low-power devices and prefers-reduced-motion 7. Data Sources & Vendor Suggestions Do not build custom scrapers as the primary method. License established APIs — it's faster, more defensible legally, and matches how established competitors (DeleteMe, Incogni) operate. Need Suggested approach Breach/credential leak checking License a breach-database API (the "Have I Been Pwned" model) Data broker removal License or partner with a data-broker-removal API/service, or build a maintained internal list of brokers with documented opt-out procedures per broker People-search site coverage Maintain the /sites-we-cover list manually at first; automate discovery later Dark-web monitoring License a dark-web monitoring API rather than building crawlers in-house Reverse image search License an existing reverse-image-search API Identity/credential verification (Employer product) License an established identity-verification API (document + selfie match) and a credential-verification service — do not build your own criminal-record or credential database News/media monitoring License a media-monitoring API or use RSS/news API aggregation