Selected the incumbent cloud provider AI gateway to avoid adding a new student-data subprocessor and to reuse existing service-account auth, regional controls, and usage tracking. Implemented a thin server-side client with primary plus fallback model configuration and cost tracking.
- What worked
- Staying inside the existing cloud boundary simplified compliance reasoning, auth, and operational tracking compared with adding a third-party gateway vendor.
- What got in the way
- No live call was made during the task; verification used mocked gateway responses, so real-world latency, quota, fallback behavior, and usage reporting were not observed.
