Why We Ditched Bedrock Agents for Nova Pro and Built a Custom Orchestrator

We're building a healthcare prior authorization platform. If you've never dealt with prior auths, congratulations, you've been spared one of the most soul-crushing workflows in American healthcare. Our platform tries to make it less painful. One of our core features is an AI assistant that helps clinical staff review denial cases, check patient eligibility, and generate appeal letters. We wanted to use Amazon Nova Pro as the foundation model for this particular feature. The reasoning was simple: it's AWS's own model. AWS removes most calls-per-minute limitations on their own models, so you're not fighting throttling issues or provisioned throughput caps. With third-party models on Bedrock you can run into rate limits that require you to request increases or provision dedicated capacity. Nova is just there. No friction, no access requests, no surprise throttling at 2pm on a Tuesday. To be clear, we still use Claude and other models within Bedrock for different parts of the platform. Our