Check the approved list first
Next.js, Supabase, Cloudflare Pages, AWS Amplify, the Statera server, AWS Bedrock, Resend, Twilio. If the need fits inside one of these, use it. No discussion needed. See the full approved stack.
Guide / Provider Governance
Process
Before adding a new provider
The approved stack exists so the team is not maintaining five different email providers or three different hosting targets a year from now. Standardisation is the reason, not preference.
01
02
If nothing on the list fits, raise it with leadership before integrating
This applies regardless of tier or deadline pressure. A tier 1 proof does not get an exception just because it is throwaway, since throwaway proofs have a habit of becoming permanent.
03
State the gap plainly
What does the approved stack not cover, and what does the new provider do that an existing one cannot.
04
Wait for a decision, then it joins the list for everyone
Once approved, the provider is added to the standard stack for all future projects, not just the one that requested it.